JP4135000B2 - Cargo information management method using electronic tags - Google Patents

Description

The present invention relates to a freight information management method and a freight management system for freight transportation from a consignor to a consignee, and in particular, using an IC card capable of reading non-contact information as an electronic tag, The present invention relates to a freight information management method and a freight management system suitable for wide-area transportation that requires many unloading bases and needs to be transported quickly and accurately.

In a consolidated freight transportation service in which cargoes of many shippers, such as courier services, are mixed and transported, the cargo is transported from a shipper to a consignee through multiple stages. In such a situation, freight tracking that accurately grasps the passage history of each cargo at each location is very important in improving the quality of transportation services such as preventing irregular situations such as cargo loss, destination differences, and damage. This is an important issue.

  At the present practical level, systems using barcodes are widely used as means for realizing this cargo tracking. In the bar code system, a bar code representing a freight number is printed in a freight slip, and the freight is traced by reading the bar code in the voucher attached to the freight at each passing point. However, in the barcode system, in order to read the barcode, it is necessary to align the cargo direction and scan the information one by one. In addition, there is a technical limitation that only fixed information that is initially registered can be held, or the information capacity that can be held is small. For this reason, there is a problem that it takes time to obtain cargo passage information, and it is difficult to fully automate cargo control such as sorting without human intervention. Furthermore, due to these problems, another problem that is important in cargo tracking, such as a time lag between the obtained cargo history information and the actual cargo movement, or insufficient items in the cargo history information may occur.

  In order to solve these problems, in recent years, electronic information using an IC card that can store a large amount of information and can write and read information in a contactless manner instead of a freight slip printed with a barcode. Cargo information management methods using freight slips (electronic tags) are being studied. Such a technique is described in, for example, JP-A-4-341414. Here, when storing the delivery information in the electronic tag for the navigation system using the electronic tag that transmits the stored delivery information in response to the inquiry signal from the electronic tag reader / writer installed in the truck, the delivery is performed. The previous position information is input with the longitude and latitude corresponding to the GPS information. On the other hand, the truck detects the position of its own vehicle by GPS (Global Positioning System), displays the current position as a current position display mark on the navigation map displayed on the display of the navigation device, and reads it from the electronic tag. Among the delivery information input to the navigation device, the location information of the delivery destination is displayed on the navigation map as the delivery destination. According to such a conventional technique, even an inexperienced delivery worker can set a delivery route like an experienced worker, and it is possible to prevent omission of delivery or forgetting delivery.

The conventional technology described above is a method for managing transportation information using an electronic tag, but has been limited to an application range and an effective application method of the electronic tag for navigation. For this reason, the following points that effectively use the electronic tag are not considered.

(1) The shipper's destination writes the collection request information, etc. to the electronic tag, but the shipper's information system can only have an electronic tag reader / writer, an IC card tag reader / writer, and a bar code label printer. Information systems are installed in different places, such as places where they cannot be placed, and these realistic problems are not considered.
(2) Utilize electronic tags including delivery / date change requests, handling of multiple cargoes for a single order (referred to as “quantity”), special cargo handling such as crap and precision machinery The processing at the practical level has not been realized.
(3) No consideration is given to prompt responses to irregular situations such as wrong arrival, wrong loading, unloading, unloading and overloading.
There is a problem.

  An object of the present invention is to provide a cargo information management method that solves the above-described problems by using a storage medium capable of reading non-contact information as an electronic tag.

In order to achieve the above object, according to one preferred aspect of the present invention, a consignee destination system provided at a consignee destination and a plurality of traders that deliver cargo collected from the consignee destination to the consignee. The base system provided at each of the bases, the consignee system provided at the consignee destination, the freight information overall management system connected to the base system, and the freight required for delivery In a freight information management system having an electronic tag capable of electronically storing information, a pickup request input in a shipper's destination system is recorded on an electronic tag attached to the freight, and a pickup management system in the base system And a collection request is accepted. When the cargo is collected, information related to the collection is recorded on the electronic tag by the terminal device, and the collection information is sent to the collection management system. The site system notifies the cargo information overall management system of the collection information and information related to the cargo passing through the site. The overall cargo information management system acquires the cargo transportation history based on the information sent from the intra-site cargo information management system, calculates the delivery schedule of the cargo, and notifies the intra-base cargo information management system.

  According to another aspect, in the freight information management method using an electronic tag, when the shipper has an electronic tag reader / writer, the electronic tag reader / writer of the shipper sends the collection request information and the landing name to the electronic tag. If there is no electronic tag reader / writer at the shipper's destination, the pickup request information received by the site system is stored in the terminal device used by the person in charge of pickup, and the shipper's destination is stored. , The collection request information input in advance to the terminal device is read into the electronic tag. In the freight transportation process, the arrival name of the arrival point at the electronic tag is completed by the electronic tag reader / writer connected to the portable terminal, the in-vehicle terminal, and the sorting device at the division of work such as unloading, sorting, and loading at each site. Write the freight transportation history information such as the date and time, the person in charge of the work, etc., and grasp the freight transportation history of each freight realistically and precisely. By comparing the freight transport history information with freight arrival schedule information, special freight handling, and collection request information such as designated delivery date and time, it is possible to quickly respond to freight transport and irregular conditions at the practical level as described above. Realize.

  As described above, according to the present invention, cargo to be transported can be handled efficiently in cargo transportation. In addition, it is possible to quickly respond to irregular situations such as mis-attachment, misloading, unloading, unloading of cargo, and overloading.

Hereinafter, an embodiment of the present invention will be described in detail as an example of a mixed freight transportation service that transports a cargo of a plurality of shippers from a consignor to a consignee. In general, in the case of mixed freight transportation, the transported cargo is delivered from the consignee to the consignee through multiple stages such as a departure store, a departure relay store, a arrival relay store, and a arrival store.

  FIG. 1 is a conceptual diagram showing the function and the overall flow of a mixed freight transportation service according to an embodiment of the present invention. Participants of the consolidated cargo transportation service include a shipper 10, a carrier 20, and a consignee 30. The shipper 10 corresponds to an individual, a company, or the like who entrusts transportation of cargo. The transporter 20 has bases such as a departure store 102, a departure relay store 104, a arrival relay store 106, and a arrival store 108, a cargo information management center 114, a collection vehicle 101, a relay vehicle 116, and a delivery vehicle 110, and undertakes a transportation service. . The consignee 30 is an individual, a company or the like who receives the cargo. In general, there are a plurality of shippers 10 and consignees 30. The overall flow of the mixed freight transportation service will be described below with reference to FIG.

  First, the shipper 10 requests the transporter 20 to collect the cargo (collection request processing 118), and the transporter 20 receives the request (request reception processing 120). Based on this, the transporter 20 circulates a plurality of consignor destinations with the collection vehicle 101 and collects cargo to be transported at each consignor destination (collected cargo reception processing 124). The collected cargo is brought back to the departure store 102 and unloaded from the collection vehicle 101 (unloading process 126). After that, they are sorted by destination (sorting process 128), loaded onto the relay vehicle 116 (loading process 130), and transported to the next base. Further, at the time of unloading 126, it is checked whether the scheduled cargo has arrived at the departure store 102 correctly (unarrived cargo check processing 132).

  Thereafter, similarly to the departure store 102, unloading 126, sorting 128, loading 130, and unarrived cargo check 132 are performed in the order of the departure relay store 104, the arrival relay store 106, and the arrival store 108 in that order.

  After loading 130 on the delivery vehicle 110 at the arrival store 108, the cargo is transported to the consignee destination 30 by the delivery vehicle 110, and the corresponding cargo is delivered at each consignee destination 30 (delivery cargo delivery processing 136). At this time, if the consignee is absent and the delivery of the cargo cannot be performed, the cargo is taken back to the arrival store 108 and stored (storage process 138). Then, loading 130, delivery transportation, and delivery cargo delivery 136 are repeated at an appropriate timing.

  In addition, cargo information such as cargo transit time is registered in the information management center 114 at the time of collecting cargo receipt 124, unloading 126 at each site, sorting 128, loading 130 and delivery cargo delivery 136 (cargo information Registration process 140). Further, the freight information management center 114 notifies the shipper of freight information such as a scheduled delivery time based on the freight information registered when the collected freight is received 124 (delivery scheduled freight information notification processing 124 and delivery freight information confirmation). In addition to the processing 144), cargo information such as estimated arrival time is notified to each base (arrival scheduled cargo information notification processing 146 and scheduled arrival cargo information confirmation processing 148). In addition to this, the cargo information management center 114 notifies the shipper 10 of the fact that the delivery of the cargo to the consignee 30 is correctly performed based on the cargo information registered at the time of delivery of the delivery cargo (delivery). Completion notification processing 150 and delivery completion confirmation processing 152) When the consignee 30 is not present and cannot deliver the cargo correctly, the consignee 30 is notified of this (absence notification processing 154 and absence notification confirmation processing 156). .

  In addition to the above, the function of the consolidated cargo transportation service is related to the inquired cargo from the freight information management center 114 to the requester in response to inquiries from the consignor 10, the consignee 30, and each base. Functions for providing various information such as attribute information and transit time information (freight information provision processing 158 and freight information inquiry processing 160), and functions for dealing with a change in the recipient's delivery destination and delivery time (delivery destination / date change) There are a request process 162 and a delivery destination / date / time change response process 164), and a function (individual cargo information confirmation process 166) for grasping the cargo information without connecting to the cargo information management center 114 at each base.

  FIG. 2 is a block diagram showing the overall configuration of a system for realizing various functions at the consignee destination, each carrier base and freight information management center, and the consignee destination shown in FIG. FIG. The system shown in FIG. 2 is a portable terminal brought by the driver of the collection vehicle 101 and the delivery vehicle 110 to the consignee destination cargo information system 210 installed in the consignee destination 10, the consignee destination 10 and the consignee destination 30. And a portable terminal system 215 installed in a portable terminal installed in each base, a collection vehicle 101, a delivery vehicle 110, an in-vehicle system 220 installed in a relay vehicle 116, a collection management system 225 installed in a store, Cargo information management system 230 in the base installed at the base, automatic sorting system 235, delivery / storage freight management system 240 installed in the arrival shop 108, cargo information overall management system 245 installed in the freight information management center 114, receipt of goods Recipient destination cargo information system 250 installed at the destination or consignee destination 10 and the network information in the site connecting each system in the site. Network 255, an inter-base network 260 that connects the intra-site cargo information management system 230 of each base, an external network 265 that connects the overall cargo information management system 245, the ship-to party cargo information system 210, and the consignee-destination cargo information system 250 including. The portable terminal system 215 possessed by the driver is wirelessly connected to the collection management system 225 and the delivery / storage cargo management system 240.

  FIG. 3 is a configuration diagram showing the configuration of the consignor destination cargo information system 210. The consignee destination cargo information system 210 is used by a consignee to perform a collection request processing 118, a delivery completion confirmation processing 152, and a cargo information inquiry processing 160, and includes a processing device 300, a storage device 310, an input device 320, and an output device. 330, an electronic tag reader / writer 340, a bar code label printer 350, an IC card reader / writer 360, an electronic tag 370, and an IC card 390.

  The input device 320 is a general input device such as a keyboard or a pointing device. The output device 330 is a general output device such as a display or a printer. The barcode label printer 350 is a device for issuing a sticker-like barcode label 380 on which a barcode is printed. The IC card reader / writer 360 is a device that writes information to the IC card 390 and reads information from the IC card 390. The IC card 390 stores special contract fee rules for individual shippers as will be described later. The electronic tag 370 is an electronic freight slip including a storage medium that can read and write information without contact. The electronic tag reader / writer 340 is a device that writes and reads information to and from the electronic tag 370.

  In the present embodiment, the electronic tag 370 is a memory that can read and write information in a non-contact manner on a part of a conventionally used multi-freight freight slip (for example, a receipt piece collected upon completion of delivery). Although the medium is attached, a storage medium such as a so-called non-contact type IC card may be used alone. The electronic tag 370 has a cargo number No. for which an order from the shipper is uniquely determined. Are registered in advance with a basic electronic tag 372 and a cargo number. There is a multi-piece electronic tag 374 that is used when there is a plurality of cargoes for one order. In the basic electronic tag 372 and the number electronic tag 374, tag classifications for distinguishing between them are registered in advance. One shipper destination cargo information system 210 does not have to include all of the electronic tag reader / writer 340, the bar code label printer 350, and the IC card reader / writer 360, and only one of them may be included. Both the basic electronic tag 372 and the number electronic tag 374 are distributed in advance as the electronic tag 370 to the shipper destination 10 having the shipper destination cargo information system 210 having the electronic tag reader / writer 340. In other shippers' destinations 10, the person in charge of collection brings the electronic tag 370 at the time of collection.

  FIG. 4 is a configuration diagram showing the configuration of the mobile terminal system 215. The portable terminal system 215 is used for the collected cargo reception process 124, the delivery cargo delivery process 136, and the individual cargo information confirmation process 166, and includes a processing device 400, a storage device 410, an input device 420, an output device 430, an electronic tag reader / writer 440, an IC. A card reader / writer 450, a barcode reader 460, a wireless communication device 480, and a label printer 490 are included. The processing device 400 is connected to the measuring instrument 470 and the in-site network 255. The input device 420 and the output device 430 have functions similar to those of the input device 320 and the output device 330 of the ship-to party cargo information system 210. The electronic tag reader / writer 440 and the IC card reader / writer 450 also have the same functions as the electronic tag reader / writer 340 and the IC card reader / writer 360 of the ship-to party cargo information system 210. The barcode reader 460 is a device for reading a printed barcode. The IC card reader / writer 450, the barcode reader 460, and the measuring device 470 are used at the time of collected cargo reception processing. The wireless communication device 480 has a function of performing wireless communication with the collection management system 225 and the delivery / storage cargo management system 240, and is used for collection cargo reception 124 and delivery cargo delivery 136. Note that when the mobile terminal system 215 and the in-vehicle system 220 can be connected, the wireless communication device 480 may be provided on the in-vehicle system 220.

  FIG. 5 is a configuration diagram showing the configuration of the in-vehicle system 220. The in-vehicle system 220 is used for the unloading process 126 and the loading process 130, and includes a processing device 500, a storage device 510, an input device 520, an output device 530, and an electronic tag reader / writer 550. The processing device 500 is connected to the in-base cargo information management system 230 at the time of unloading 126 and loading 130. The input device 520 and the output device 530 have functions similar to those of the input device 320 and the output device 330 of the consignee destination cargo information system 210. The electronic tag reader / writer 550 has a function similar to that of the electronic tag reader / writer 340 of the consignee cargo information system 210. The electronic tag reader / writer 550 is installed at the loading / unloading port of the vehicle, and the input device 520 and the output device 530 are also installed in the vicinity thereof. When performing the unloading process 126 and the loading process 130, the function of the in-vehicle system 220 may be realized by the intra-site cargo information management system 230.

  FIG. 6 is a block diagram showing the configuration of the collection management system 225. The collection management system 225 is used for the request reception process 120 and the collected cargo reception process 124, and includes a processing device 600, a storage device 610, an input device 620, an output device 630, and a wireless communication device 640. The processing device 600 is connected to the local network 255 and the external network 265. The input device 620 and the output device 630 have functions similar to those of the input device 320 and the output device 330 of the consignee destination cargo information system 210. The wireless communication device 640 has the same function as the wireless communication device 480 of the portable terminal system 215 and is used for wireless communication with the portable terminal system 215 at the time of collecting cargo reception 124 and delivery cargo delivery 136.

  FIG. 7 is a block diagram showing the configuration of the intra-base cargo information management system 230. The in-base cargo information management system 230 is used in the unarrived cargo check processing 132, the cargo information inquiry processing 160, the cargo information registration processing 140, and the delivery destination / date / time change correspondence processing 164, and includes a processing device 700, a storage device 710, and an input device. 720 and an output device 730. The processing device 700 is connected to the intra-base network 255 and the inter-base network 260. The input device 720 and the output device 730 have the same functions as the input device 320 and the output device 330 of the consignor destination cargo information system 210, respectively.

  FIG. 8 is a configuration diagram showing the configuration of the automatic sorting system 235. The automatic sorting system 235 is used for sorting 128, and includes a processing device 800, a storage device 810, an input device 815, an electronic tag reader / writer 820, a sorting line 840, and a label printer 850. The processing device 800 is connected to the intra-site network 255. The electronic tag reader / writer 820 has a function similar to that of the electronic tag reader / writer 340 of the consignee cargo information system 210. The label printer 850 is used at a store.

  FIG. 9 is a block diagram showing a configuration of the delivery / storage freight management system 240. The delivery / storage freight management system 240 is used for the delivery freight delivery processing 136 and the storage processing 138, and includes a processing device 900, a storage device 910, an input device 920, an output device 930, a wireless communication device 940, and an electronic tag reader / writer 950. The The processing device 900 is connected to the intra-site network 255. The wireless communication device 940 has a function similar to that of the wireless communication device 480 of the mobile terminal system 215 and is used for wireless communication with the mobile terminal system 215 during delivery cargo delivery 136. The input device 920 and the output device 930 have the same functions as the input device 320 and the output device 330 of the consignor destination cargo information system 210, respectively. The electronic tag reader / writer 950 has a function similar to that of the electronic tag reader / writer 340 of the consignee cargo information system 210.

  FIG. 10 is a configuration diagram showing the configuration of the consignee destination cargo information system 250. The consignee destination cargo information system 250 is used for the scheduled delivery cargo information confirmation processing 144, absence notification confirmation processing 156, cargo information inquiry processing 160, delivery destination / date change request processing 162 by the consignee, processing device 1000, storage device 1010, an input device 1020, and an output device 1030. The processing apparatus 1000 is connected to the external network 265. The input device 1020 and the output device 1030 have functions similar to those of the input device 320 and the output device 330 of the consignee destination cargo information system 210.

  FIG. 11 is a configuration diagram showing the configuration of the cargo information overall management system 245. The entire cargo information management system 245 includes a cargo information registration process 140, a scheduled delivery cargo information notification process 142, an expected arrival cargo information notification process 146, a delivery completion notification process 150, an absence notification process 154, a delivery destination / date / time change handling process 164, It is used for freight information provision processing 158 and comprises a processing device 110 and a storage device 1110. The processing apparatus 1100 is connected to the inter-base network 260 and the external network 265.

  Hereinafter, the processing operation in each part will be described along the flow of the mixed freight transportation service.

  <1: Collection Request and Request Reception> FIG. 12 is a flowchart showing the processing flow of the collection request process 118 and the request reception process 120. In the flowcharts shown in FIG. 12 and other drawings, a wavy line indicates that information is transmitted.

  The collection request information is input from the input device 320 of the consignor destination cargo information system 210. FIG. 13 is a data configuration diagram of the collection request information. The collection request information 1300 is large and includes freight information 1302 related to the freight requested to collect, consignor information 1304 related to the consignor, consignee information 1306 related to the consignee, and desired collection date 1310. The cargo information 1302 is set when a cargo item name 1312 to be collected is collected, the number of cargos 1316 in one order, and a shipper requests additional services such as refrigerated transportation and timed delivery in addition to normal transportation. If the time specified delivery is set as the incidental service 1318 or the incidental service 1318, the specified delivery time 1320 for the specified time is set. Special cargo category 1322 that indicates the category, and the payment method of the fee are set to one of the following: cash collection for collecting the price at the time of collection, accounts receivable using the price as sales, and cash on delivery for collecting the price from the consignee when delivery is completed A billing section 1324 is included. The shipper information 1304 includes a shipper code 1326 that uniquely identifies a shipper given individually for each shipper, a shipper name (name) 1328, a shipper address 1330, a telephone number 1332, a shipper An electronic address 1334 is included as a person's e-mail address, and an infrastructure type 1335 indicating whether the electronic tag reader / writer 340, the bar code label printer 350, or the IC card reader / writer 360 is provided in the ship-to party cargo information system 210 is included. It is. The consignee information 1306 includes the consignee name 1336, address 1338, telephone number 1342, electronic address 1342, and consignee destination information 1308 as the consignee address 1350, telephone number 1352, and electronic address 1354. included. The consignee destination information 1308 may include information regarding a plurality of destinations. When the collection request information 1300 is input from the input device 320, it is sequentially stored in the storage device 310.

  When the collection request information 1300 is set, a table as shown in FIG. 13 is displayed on the display screen on the output device 330, and each information is set by the consignor on the display screen. Of the collection request information 1300, the consignor information 1304 is stored in advance in the storage device 310 so that display on the display screen and setting in the collection request information 1300 are performed without input by the consignor. it can. Similarly, information related to the consignee to whom the cargo is delivered periodically is stored in the storage device 310, and a search using the name and telephone number as a key is performed on the input screen, and the consignor information 1306 is retrieved. Can also be set automatically.

  When all items of the collection request information 1300 are input, the processing device 300 transmits the collection request information stored in the storage device 310 to the collection management system 225 via the external network 265 in accordance with the instruction of the shipper. (Step 1200).

  In the collection management system 225, the processing device 600 receives the collection request information 1300 from the consignee destination cargo information system 210. The processing apparatus 600 selects the collection request No. that uniquely determines the received collection request information 1300. Number. The collection request information 1300 includes a collection request No. Are stored in the storage device 610 together with the time when the processing device 600 receives the collection request information (step 1210).

  Based on the shipper's address 1330 and the desired collection date and time 1310 in the collection request information 1300 stored in the storage device 610, the processing device 600 determines the collection person DB by time zone / area stored in the storage device 610. Refer to and determine the person in charge to collect goods. FIG. 14 shows an example of the collection person in charge DB by time zone / area. The collection person in charge by time zone / area DB 1400 stores the person in charge No. of the person in charge of the collection work for each time zone of the day and the area under the control of the store. Is registered. The time zone / area-specific collection person in charge DB 1400 is provided with a table for each day or every certain period. Specifically, the person in charge is first determined based on the date information 1410 in the time zone / area collection person in charge DB corresponding to the desired collection date 1310 included in the collection request information. And the person in charge No. set in the entry in which the consignor address 1330 and the desired collection date 1310 in the collection request information match. To extract.

  Next, the processing apparatus 600 is in charge of the person in charge No. Based on the above, the person-in-charge terminal-supported DB is searched to identify the portable terminal system 215 possessed by the person in charge. The person-in-charge-portable terminal correspondence DB 1600 is stored in the storage device 610 and, as shown in FIG. Every 1610, the person in charge No. The portable terminal No. of the portable terminal system 215 possessed by the person in charge specified by 1620 is registered. The processing device 600 has the mobile terminal No. specified here. Is assigned as the transmission destination of the collection request information, the corresponding collection request information 1300 stored in the storage device 610 and the corresponding collection request No. Send. The collection request information 1300 is sent via the in-base network 255 when the corresponding mobile terminal system 215 is in the departure store 102, and via the wireless communication device 640 when the mobile terminal system 215 is at the destination. At this time, when an electronic tag reader / writer or an IC card reader / writer is provided as the infrastructure type 1335 of the consignor freight information system 210, collection request information excluding the consignor information 1306 may be sent. (Step 1220).

  When the collection request information 1300 is correctly transmitted to the portable terminal system 215 in step 1220, the processing apparatus 600 transmits the fact as a collection request reply to the consignee destination cargo information system 210 via the external network 265. At this time, if the infrastructure type of the ship-to party cargo information system 210 is a bar code label printer, the collection request No. Is also transmitted (step 1230).

  In the consignee destination cargo information system 210, when the processing device 300 receives the collection request response, the information sent as the collection request response is combined with the collection request information 1300 stored in the storage device 310 to the output device 330. It is displayed (step 1240). Thereafter, in the ship-to party cargo information system 210, in step 1250, the processing apparatus 300 performs order information registration processing.

  FIG. 15 is a detailed flowchart of the order information registration process. In the order information registration process (step 1250), first, it is checked whether the infrastructure type of the ship-to party cargo information system 210 is a bar code label printer (step 1510). If the infrastructure type is a bar code label printer, the processing apparatus 300 receives the collection request No. included in the collection request response received in step 1240. Is converted into a bar code, a bar code label 380 is issued, and the process ends. Here, the shipper attaches the printed label 380 to the corresponding cargo. When there are a plurality of cargoes for one order, the shipper attaches a barcode label 380 to the representative cargo (step 1520).

  On the other hand, if the infrastructure type is not the barcode label printer in step 1510, the processing device 300 is stored in advance in the storage device 310 using the consignee address 1338 included in the pickup request information stored in the storage device 310 as a key. The store name DB by address is searched to determine the store name. FIG. 17 shows an example of the addressed store name DB. In the address-specific arrival store name DB 1700, for each address 1710 in the area targeted for the cargo transportation service, a store arrival name 1720 having the address as the service range is registered (step 1530).

  Next, it is checked whether or not the infrastructure type of the consignee cargo information system 210 is an electronic tag reader / writer (step 1540). If the infrastructure type is not the electronic tag reader / writer, the collection request information 1300 held in the storage device 310 and the store name determined in step 1530 are distributed to the shipper's destination 10 in advance using the IC card reader / writer 360. Registered in the IC card 390 (step 1550).

  If it is determined in step 1540 that the infrastructure type is an electronic tag reader / writer, the collection request information 1300 stored in the storage device 310 and the store name determined in step 1530 are stored in advance using the electronic tag reader / writer 340. It is registered in the basic electronic tag 372 distributed to the shipper's destination 10. In addition, the processing device 300 has a cargo No. registered in the basic electronic tag 372 in advance. Is read by the electronic tag reader / writer 340 and stored in the storage device 310 (step 1560).

  Further, the processing device 300 checks whether the number 1316 included in the collection request information 1300 held in the storage device 310 is 2 or more, and ends the processing if it is less than 2 (step 1570). If the number 1316 is 2 or more, the processing apparatus 300 has the number number No. The initial value 2 is stored in the storage device 310 as follows. Number port No. Is a number that uniquely defines each freight when there are a plurality of freights for a single order (step 1575). Subsequently, the processing device 300 stores the freight number registered in the basic electronic tag 372 together with the collection request information stored in the storage device 310 and the arrival name determined in step 1530. And the number port No. Is registered in the electronic tag 374 distributed in advance using the electronic tag reader / writer 340. At this time, the number No. Is incremented by 1 (step 1580). Next, the piece number No. Whether the number is larger than the number 1316. If the number is larger than the number 1316, the process is terminated. If not, the process proceeds to step 1580, and the registration of the number electronic tag 374 is continued (step 1590).

  <2: Receipt of Collected Cargo> The collection request information 1300 transmitted from the collection management system 225 in step 1220 is received by the portable terminal system 215 of the person in charge who performs the collection work. The portable terminal system 215 stores the received collection request information 1300 in the storage device 410 and outputs it to the output device 430. A person in charge of collection work (driver) performs collection work using the portable terminal system 215. FIG. 18 is a flowchart showing a flow of processing mainly performed in the portable terminal system 215 during the collected cargo reception processing 124 performed by the person in charge of collection at the consignor.

  In the collected cargo reception 124, information stored in the IC card 390 distributed in advance to the shipper's destination 10 is read using the IC card reader / writer 450 of the portable terminal system 215 and read into the processing device 400. . In the memory in the IC card 390, as shown in FIG. 19, a special charge rule 2010, a usage fee history 2030, and an electronic money balance 2060 are stored. The special charge rule 2010 includes a rule used to calculate a price such as “If the accumulated usage price of the current month is 100,000 yen or more, the discount rate is set to 0.9” as in the discount rule 2020. The special charge rule 2010 may be different for each shipper. In the usage price history 2030, the usage date 2040 in the order of the shipper's freight transportation service and the history of the price 2050 at that time are recorded for each order. The electronic money balance 2060 records the electronic money balance when the IC card 370 is provided with an electronic money function (step 1910).

  Next, when the infrastructure type of the ship-to party cargo information system 210 is an electronic tag reader / writer, the collection request information 1300 and the store name for one order stored in the basic electronic tag 372 attached to the cargo are: The data is read into the processing device 400 by the electronic tag reader / writer 440 of the portable terminal system 215. When there are a plurality of orders, only the collection request information 1300 stored in the basic electronic tag 372 may be read. When the infrastructure type of the shipper's destination cargo information system 210 is an IC card reader / writer, the pickup request information and the store name stored in the IC card 390 are used by using the IC card reader / writer 450 of the portable terminal system 215, The data is read into the one order processing apparatus 400. Thereafter, using the IC card reader / writer 450, the collection request information 1300 corresponding to the read order is deleted from the IC card 390. When the infrastructure type of the ship-to party cargo information system 210 is a barcode label printer, first, the barcode label 380 is read using the barcode reader / writer 460 of the portable terminal system 215. The pickup request No. read from the bar code label 380 is displayed. As a key to collect request No. stored in the storage device 410. Is retrieved, and the matching pickup request No. is matched. The collection request information corresponding to is read into the processing device 400 (step 1915).

  When the weighing instrument 470 measures the weight of the cargo corresponding to the collection request information, the processing device 400 reads the obtained weight information from the weighing instrument 470. If there are a plurality of cargoes, the weights of all the relevant cargos are measured, and the processing device 400 adds them together to obtain weight information (step 1920). Subsequently, the processing apparatus 400 performs fee calculation based on the acquired weight information (step 1925).

  FIG. 20 is a flowchart showing detailed processing of the charge calculation processing (step 1925).

  In the fee calculation processing, the processing device 400 calculates a flat fee based on the fixed fee system DB stored in the storage device 410 in advance and adds it to the price. The flat fee system DB is a database in which a flat fee 2220 is registered for each fee item 2210 as shown in FIG. The flat fee is a fee that is added to the fixed price regardless of the contents of the order. The flat fee is calculated by adding all the flat fees 2220 corresponding to the respective charge items 2210 in the flat fee structure DB 2200 (step 2110).

  Next, the processing device 400 calculates an incidental service fee based on the incidental service fee system DB stored in the storage device 410 in advance and adds it to the price. As shown in FIG. 22, the incidental service fee system DB is a database in which necessary incidental service fees are registered for each incidental service item 2310. Ancillary services are services such as timed delivery and refrigerated transport that are carried out in response to the shipper's request in addition to normal services. Charges added when using such services are incidental service charges. is there. Here, an incidental service fee 2320 corresponding to the incidental service item 2310 that matches the incidental service 1318 in the collection request information 1300 is obtained. If there are a plurality of matching incidental services, the charges are calculated together (step 2120).

  The processing device 400 checks whether the information set in the infrastructure type 1335 of the collection request information 1300 is a barcode label printer. If the infrastructure type is a bar code label printer, the process proceeds to step 2128; otherwise, the process proceeds to step 2140 (step 2124).

  In step 2128, the processing device 400 determines the store name by referring to the store-specific store name DB stored in the storage device 410 in advance using the consignee address 1330 included in the collection request information 1300 as a key. The store name DB by address stored in the storage device 410 of the portable terminal system 215 is the same as the store name DB 1700 by address of the shipper destination cargo information system 210 in FIG. It is determined in the same way.

  In step 2130, the transportation distance is determined with reference to the transportation distance calculation DB stored in the storage device 410 in advance. As shown in FIG. 23, in the transport distance calculation DB 2400, a store 2410 is set in the row direction and a store 2420 is set in the column direction, and a distance 2430 between the bases is registered at the intersection. The transport distance includes the store opening name stored in advance in the storage device 410 for each portable terminal system 215 and step 1915 (when the infrastructure type of the consignee cargo information system 210 is an IC card reader / writer or an electronic tag reader / writer). Alternatively, based on the store name obtained by the processing device 400 in step 2128 (when the infrastructure type of the shipper's destination cargo information system 210 is a bar code label printer), the store 2410 in the transport distance calculation DB 2400 2420 is searched and determined from the transport distance described in the matching location. For example, if the departure store is a Tsuzuki store and the arrival store is a Kohoku Tohoku store, the transport distance is 15 km.

  Next, the processing device 400 refers to a metered fee system DB stored in the storage device 410 in advance, calculates a metered fee, and adds it to the price. The metered fee is a fee determined by the transportation distance and weight of the cargo, and the metered fee system DB 2500 has a metered fee corresponding to each of the weight band 2510 and the distance band 2520 as shown in FIG. It is registered. The transportation fee is obtained from the charges corresponding to the corresponding weight band 2510 and distance band 2520 in the transportation fee system DB 2500 based on the weight read by the processing device 400 in step 1920 and the transportation distance determined in step 2130. For example, in the figure, if the weight is 7 kg and the transport distance is 15 km, the weight band is “5 to 10 kg”, the distance band is “10 to 30 km”, and the transport fee is 370 yen (step 2140).

  Further, the processing device 400 determines a discount rate based on the discount rule set in the special contract fee rule 2010 obtained in step 1910. When determining the discount rate, the processing apparatus 400 refers to the information such as the weight information acquired in step 1920 and the usage fee history 2030 as necessary. If the conditions match a plurality of discount rules, the final discount rate is calculated by multiplying the discount rates determined from the respective discount rules. For example, in the case of the special contract fee rule 2010 shown in FIG. 19, if the accumulated usage fee for the current month is 101000 yen and the weight is 110 kg, the final discount rate is 0.9 × 0.95 = 0.855. The processing device 400 calculates the final fee by multiplying the price calculated up to step 2140 by this final discount rate (step 2150).

  When the final fee is calculated as described above, the processing device 400 displays the calculated fee on the output device 430 and proceeds to the processing of the next step 1930 (step 2160). In step 1930, it is checked whether or not the billing category 1324 of the collection request information 1300 is “cash receipt”. If the billing category 1324 is the current income, the process moves to Step 1935, and if not, the process skips Step 1935 and moves to Step 1940.

  When the billing category 1324 is cash, the processing device 400 subtracts the fee calculated in step 2150 from the electronic money balance read in step 1910 to calculate the balance of the electronic money after cash is collected. The balance of electronic money is displayed on the output device 430, and the electronic money balance 2060 in the IC card 390 is updated with this balance by the IC card reader / writer 360. If the balance of electronic money is negative, the shortage amount is displayed on the output device 430. When the price has been correctly collected, the processing apparatus 400 holds “Done” as the collection category (step 1935).

  In step 1640, it is checked whether or not the billing category 1324 in the collection request information is “cash on delivery”. If the billing section 1324 is cash on delivery, the processing apparatus 400 proceeds to Step 1950; otherwise, the processing apparatus 400 proceeds to Step 1945.

  The processing device 400 includes a shipper name 1328, a billing category 1324 included in the collection request information 1300, a transport service contractor name, a store name, a person-in-charge name stored in the storage device 410 in advance, the fee calculated in step 2150, From the label printer 490, a calculation / receipt describing the date on which the charge was calculated, a sign field, and the like is output. Further, the processing device 400 records the usage date and the fee calculated in step 2150 in the usage date column 2040 and the price column 2050 of the usage price history 2030 of the IC card 390 by the IC card reader / writer 450 (step 1945). .

  In step 1950, the processing apparatus 400 performs collection information registration processing. FIG. 25 shows a detailed flowchart of the collection information registration process.

  In the collection information registration process, first, the collection request information 1300 is checked to determine whether the infrastructure type is an electronic tag reader / writer (step 2610). If the infrastructure type is the electronic tag reader / writer, the processing device 400 reads the weight acquired in step 1920, the charge calculated in step 2150, and the person in charge number stored in advance in the storage device 410. The date and time of registration and “collection” as a work category are registered in the basic electronic tag 372 attached to the corresponding cargo using the electronic tag reader / writer 440. If the collection category held by the processing apparatus 400 in step 1935 is “completed”, “done” is registered in the basic electronic tag 372 as “collection” if the collection category is not held. When there are a plurality of cargos, the same information is registered in all the corresponding electronic tags 374. Further, the processing device 400 reads the collection request information and the store name registered in the basic electronic tag 372 using the electronic tag reader / writer 440, and combines it with the information registered in the basic electronic tag 372 and the number electronic tag 374. The registration processing is terminated after storing in the storage device 410 (step 2620).

  If it is determined in step 2610 that the infrastructure type is not the electronic tag reader / writer, the processing device 400 uses the electronic tag reader / writer 440 to collect the collection request information, the store name, the weight acquired in step 1920, the charge calculated in step 2150, and the storage device in advance. The person in charge No. The date and time of registration, and “collection” as the work category are registered in the basic electronic tag 372 brought by the person in charge of collection. The collection category is also registered in the basic electronic tag 372 in the same manner as in step 2620. The processing device 400 also has a cargo No. registered in the basic electronic tag 372 in advance. Is read by the electronic tag reader / writer 440, and the information registered in the basic electronic tag 372 is stored in the storage device 410 (step 2630).

  Next, the processing apparatus 400 checks whether or not the number 1316 of the collected collection request information 1300 is “2” or more, and ends the processing if the number 1316 is less than 2 (step 2640). If the number 1316 is 2 or more, the processing apparatus 400 will receive the number port No. Is set and held (step 2650).

  The processing apparatus 400 uses the electronic tag reader / writer 440 to hold the collection request information, the store name, the weight information, the fee calculated in step 2150, the person in charge number. , Registration date and time, and work classification, the cargo No. registered in the basic electronic tag in step 2630. And the number port No. At the same time, it is registered in the number-of-pieces electronic tag 374 brought by the person in charge of collection. The collection category is also registered in the number-of-pieces electronic tag 374 as in step 2620. And the number mouth No. 1 is added to the value held in (2660).

  Subsequently, the processing apparatus 400 includes a number slot No. It is determined whether the value of exceeds the number 1316 in the collection request information. Number port No. If the value of the number is less than or equal to 1316, the processing of step 2660 is repeated, If the value exceeds the number 1316, the collection information registration process is terminated (step 2670).

  Following the collection information registration process, the processing apparatus 400 outputs the special cargo category labels from the label printer 490 in the number indicated by the number 1316 in accordance with the special cargo category 1322 of the collection request information 1300. The special cargo classification label is affixed to the cargo by the person in charge. For example, when the special cargo category 1322 is “wet”, the special cargo category label is output with a label “notice of crap” (step 1955).

  Thereafter, the processing device 400 checks whether there is a collection registration end request from the input device 420 (step 1960). If there is no collection registration end request, the processing device 400 repeats the processing from step 1915 onward and performs processing for other orders. If there is a collection registration end request, the collection request information, the store name, the weight information, the fee, the person in charge number stored in the processing device 400 and the storage device 410 are stored. Then, the label printer 490 outputs a receipt in which the registration date / time, the work classification, and the signature field are described. When there are a plurality of orders, the contents of the collection request, the store name, the weight, and the charge are output in a plurality of lines (step 1965).

  When the issuance of the receipt is completed, the processing device 400 follows the instructions of the collector in charge, the collection request information stored in the storage device 410, the store name, the weight information, the fee calculated in step 2150, the person in charge No. The collection registration information including the registration date / time, work category, and collection category is transmitted to the collection management system 225 by the wireless communication device 480 (step 1970).

  Upon receiving the collection registration information sent from the portable terminal system 215 by the wireless communication device 640, the collection management system 225 transmits it to the in-base cargo information management system 230 via the in-base network 225 (step 1980). . Further, the intra-site cargo information management system 230 transmits the cargo registration information to the overall cargo information management system 245 via the inter-base network 260 (step 1985).

  <3: Unloading> FIG. 26 is a flowchart of the unloading process 126, that is, a process performed by the in-vehicle system 220 and the in-site cargo information management system 230 when unloading cargo from a vehicle at each site. .

  In the unloading process 126, the processing device 500 of the in-vehicle system 220 first receives the person in charge No. from the input device 520. The site name is received and stored in the storage device 510. Person in charge No. For example, the in-vehicle system 220 is equipped with an IC card reader / writer, and the person in charge No. of each person in charge is received. May be received from an IC card or the like registered. This is because the person in charge in other processing is NO. The same applies to the registration of (step 2810).

  Next, the processing apparatus 500 uses the electronic tag reader / writer 550 to read the cargo number registered there from the electronic tag 370. , No. The electronic tag classification, the number, the special cargo classification, the store name, the store name, and the delivery specified time are acquired and held (step 2815).

  The processing apparatus 500 is a cargo No. Is used as a key to search the delivery destination / date / time changed cargo DB stored in the storage device 710 of the intra-site cargo information system 230 to check whether the delivery destination / date / time change information is registered for the corresponding cargo. As shown in FIG. Corresponding to 2910, changed delivery destination information 3015 and changed delivery desired date / time information 3020 are held. The changed delivery destination information 3015 includes a changed destination name 3030, an address 3035, a telephone number 3040, an electronic address 3045, and a changed arrival store name 302. In the delivery destination / date / time changed cargo DB 3000, either or both of the changed delivery destination information 3015 and the changed delivery desired time information 3020 are registered by a delivery destination / date / time change request and response processing described later (step 2817). As a result of the search, the cargo No. Cargo No. that matches If a record having 3010 is found, the process proceeds to step 2820. Cargo No. Cargo No. that matches If there is no record having 3010, the process of step 2820 is skipped, and the process proceeds to step 2825 (step 2817).

  In step 2820, the cargo No. Information of the record including 3010 is read. If the changed delivery destination 3015 is registered in the read record, the processing device 500 uses the electronic tag reader / writer 550 to use the name 3030, the address 3035, the telephone number 3040, the electronic address 3045, and the change destination of the changed delivery destination 3015. With the store name 3025, the consignee name 1336, the address 1338, the telephone number 1340, and the arrival name of the collection request information 1300 registered in the electronic tag 370 are changed. If the changed delivery desired time 3020 is registered, the specified delivery date held in the electronic tag 370 is updated with the changed delivery desired date 3020 by the electronic tag reader / writer 550 (step 2820).

  In step 2825, the processing device 500 displays the person in charge number stored in the storage device 510 in step 2810. The current time is registered in the electronic tag 370. And these information and cargo No. , No. The cargo passage information including “unloading” as the work category is transmitted to the intra-base cargo information management system 230 (step 2825).

  Next, the processing device 500 searches the transportation route pattern DB using the departure store name and arrival store name as keys, and determines a transportation route base. In the transport route pattern DB, as shown in FIG. 28, transport route bases are registered at the intersections of the matrix of the departure store 3110 and arrival store 3120. For example, if the departure store is “Sapporo West Store” and the arrival store is “Fukuoka East Store”, from entry 3130, the transportation route is Sapporo West Store−Chitose Airport Store−Fukuoka Airport Store−Fukuoka East Store. If the transportation route base determined in this way does not include a base to which the processing device 500 belongs, a message to that effect is output to the output device 530 (step 2830).

  When the delivery time is designated by the delivery designated time 1320 acquired in step 2815, the processing device 500 determines the delivery designated time, freight number. , And the store name are output to the output device 530 (step 2835). If the special cargo category 1322 indicates a special cargo category such as “wet” or “precision equipment”, the contents and the cargo number. Is output to the output device 530. By looking at this output, the worker in charge can easily identify the special cargo and handle the cargo (step 2840).

  Furthermore, if the number is two or more, the processing apparatus 500 will store the cargo No. held. , No. And the quantity are registered in the quantity cargo information DB stored in the storage device 510. As shown in FIG. 3210, No. 32 3220 and the number 3230 are registered. In this process, the cargo No. 3210, No. 32 Both of the cargo numbers No. 3220 to be registered are registered. , No. If there is already a record having the same value, the registration to the piece quantity cargo information DB 3200 is not performed (step 2845).

  The processing device 500 checks whether there has been an input of a number check start request to the input device 520. If there is no quantity check start request, the processing device 500 clears the stored information, returns to the processing of step 2815, and repeats the above-described processing for the next cargo (step 2850). When the request for starting the number check is detected in step 2850, the processing device 500 checks the number check cargo information DB 3200 and checks the same cargo number. The number of records in which 3210 is registered is counted. The resulting count number and its cargo number The value registered in the number 3230 corresponding to the number 3210 is compared. 3230, the number 3230, and the count number are output to the output device 530. Cargo No. For each time, a piece quantity cargo information deletion request is accepted from the input device 520. Same cargo No. The record having 3210 is deleted from the piece quantity cargo information DB 3200 (step 2860).

  When the number check in step 2860 is completed, the processing device 500 checks whether a work end request is input to the input device 520. If there is a work end request, the processing device 500 ends the process, and if there is no work end request, the processing device 500 repeatedly performs the processes after step 2815 (step 2870).

  On the other hand, when receiving the cargo passage information from the in-vehicle system 220 in step 2825, the intra-base cargo information management system 230 registers the cargo passage information in the cargo passage DB stored in the storage device 710. As shown in FIG. 3310, piece number No. 3320, base name 3330, work classification 3340, transit time 3350, vehicle No. 3370, storage category 3380, and person in charge name 3390. In this process, the cargo No. 3210, No. 32 Both of the cargo No. 3220 included in the received passing cargo information. , No. Is already registered in the cargo passage information DB 3300 (step 2875). The intra-site cargo information management system 230 transmits data registered in the cargo passage information DB 3300 at regular intervals to the overall cargo information management system 245 via the inter-base network 260 (step 2885).

  <4: Sorting> The cargo that has been unloaded is sorted by the automatic sorting system 235. FIG. 31 is a flowchart of processing performed by the automatic sorting system 235 and the in-base cargo information management system 230 during the sorting process 128.

  First, in the automatic sorting system 235, the person in charge No. of the person in charge performing the sorting work. Is received from the input device 815 and stored in the storage device 810 (step 3410).

  The processing apparatus 800 uses the electronic tag reader / writer 820 to read the cargo number from the electronic tag 370. , No. , Read the store name. In the case where the sorting base is the arrival store, in addition to these information, the consignee name 1336, address 1338, telephone number 1340, incidental service 1318, delivery specified time of the collection request information 1300 held in the electronic tag 370 1320 is also read (step 3420).

  Next, a sorting instruction is given for each destination (step 3430). FIG. 32 shows a detailed flowchart of the destination-specific sorting instruction.

  In step 3430, first, it is determined based on the store name read from the electronic tag 370 whether or not the site is the store for the cargo to be sorted. (Step 3510).

  If the base is not the arrival store, in step 3520, the processing device 800 refers to the arrival location classification DB stored in the storage device 810 using the stored arrival name as a key, and sets the cargo number of the corresponding cargo. . The sorting port is instructed to the sorting line 840. As shown in FIG. 33, the sorting DB classified by arrival stores the sorting port No. for identifying the sorting port of the sorting line 840. Corresponding to 3610, a base name 3620 as a delivery destination of the cargo delivered from the sorting port is registered. In the arrival store name 3620, one or more base names are registered, except when there is no corresponding case. When the processing apparatus 800 issues a sorting instruction to the sorting line 840, the processing apparatus 800 proceeds to the next step 3450. (Step 3520).

  On the other hand, when the base is a store, the processing apparatus 800 uses the information read in step 3420 to issue a label in a sticker shape describing the information from the label printer 850. This label is affixed to the corresponding cargo by the person in charge (step 3430). Next, the processing device 800 checks whether or not a delivery time is designated based on the delivery designation date and time 1320 that is held. If the delivery time is specified, the process proceeds to step 3530. If the delivery time is not specified, the process in step 3530 is skipped and the process proceeds to step 3540 (step 3525).

  In step 3530, the processing device 800 refers to the sorting time zone-delivery end time correspondence DB stored in the storage device 810 and instructs sorting of the stored cargo. The sorting time zone-delivery end time correspondence DB, as shown in FIG. 34, for each time zone (sorting time zone) 3710 in which the sorting operation is performed, delivers the cargo that has been subjected to the sorting operation performed in that time zone. Is registered (scheduled delivery end time) 3720. For example, in the figure, it can be seen that cargo entered between 10:00 and 12:00 is scheduled to be delivered by 14:00. The processing device 800 searches the sorting time zone 3710 for the time zone to which the current time belongs, and acquires the corresponding scheduled delivery end time 3720. Then, the delivery designation time 1320 acquired in step 3420 is compared with the scheduled work end time. If the scheduled delivery end time is earlier, an instruction is given to the sorting line 840 to sort the corresponding corresponding cargo into the storage cargo sorting port. If the scheduled delivery end time is later, no sorting instruction is issued (step 3530).

  In step 3540, processing apparatus 800 refers to the address-specific sorting port DB using acquired consignee address 1338 as a key, and instructs sorting line 840 for the corresponding cargo sorting port. As shown in FIG. For each 3810, an address (area) 3820 serving as a delivery destination from the sorting port is registered (step 3540).

  Following the destination-specific sorting instruction, the processing device 800 reads the person-in-charge number from the storage device 810. And the name of the base where the work is registered in advance is read. These pieces of information are registered in the electronic tag 370 together with the current time, “sort” indicating the work category, and the storage category. As the storage category, “storage” is registered for those for which a storage cargo sorting instruction is issued in step 3530, and “pass” is registered for those for which a storage cargo sorting instruction has not been issued. Furthermore, the processing device 800, together with the information registered in the electronic tag 370, receives the cargo number acquired in step 3420. , No. Is transmitted to the in-base freight information management system 230 as freight passage information (step 3450).

  Thereafter, the processing device 800 determines whether a work end request has been accepted, and if there is a work end request, ends the processing. If the work end request has not been received, the processing device 800 returns to step 3420 and continues the processing (step 3470).

  In the base cargo information management system 230, when the cargo passage information transmitted from the automatic sorting system 235 is received in step 3450, the cargo passage information is registered in the cargo passage information DB 3300 by the processing device 700 as in step 2875. (Step 3480). Then, the information registered in the cargo passage information DB 3300 is transmitted to the cargo information overall management system 245 via the inter-base network 260 at regular intervals (step 3490).

  <5: Loading> FIG. 36 is a flowchart showing a flow of processing performed when loading cargo into a vehicle in the loading processing 130.

  In the loading process 130, the processing device 500 receives the person in charge No. from the input device 520 of the in-vehicle system 220. And the input of the site name is accepted. Entered person in charge No. The base name is stored in the storage device 510 (step 3910). Similarly, the input device 520 receives an input of a destination base name, and the input base name is stored in the storage device 510. Further, as an initial setting, 0 is set to the weight cumulative variable (step 3915).

  The processing apparatus 500 includes a cargo No. of cargo loaded by the electronic tag reader / writer 550. , No. Read out the store name and store name. When the work base is a store, the electronic tag classification is also read out. If the electronic tag classification is “basic electronic tag”, the number 1316 recorded as the collection request information 1300, the consignee name 1336, the address 1338, the telephone number 1340, and the designated delivery date 1320 are read out. And stored in the storage device 510 (step 3920).

  Similar to step 2830, the processing device 500 searches the transport route pattern DB 3100 based on the store name and the store name, and determines the transport route base. If the destination base name input in step 2915 is not included in the transport route base, an erroneous loading alarm is output to the output device 530 (step 3925). Next, in step 3920, the weight read from the electronic tag 370 is added to the weight cumulative variable to obtain a new weight cumulative, which is compared with the load limit weight registered in advance in the storage device 510. If the cumulative weight variable is larger than the load limit weight, an overload alarm is output to the output device 530 (step 3930).

  After the above check, the processing apparatus 500 determines the person in charge number. , Base name, current time, vehicle number stored in the storage device 510 in advance. In addition, “loading” is registered in the electronic tag 370 as a work category. In addition, such information includes cargo No. , No. At the same time, it is transmitted to the in-base freight information management system 230 as freight passage information (step 3935).

  Next, the processing device 500 checks whether or not a work end request is input from the input device 520. If there is no work end request, the processing device 500 repeatedly performs the processing from step 3920 (step 3940). If there is a work end request, the processing device 500 checks whether the work base is a store arrival, and if not, ends the processing (step 3945). If the work base is the arrival store, the processing device 500 determines the cargo number stored in the storage device 510 in step 3920. The number 1316, the consignee name 1336, the address 1338, the telephone number 1340, and the designated delivery date / time 1320 are read out, and a delivery destination list in which such information is described is output from the output device 530. As shown in FIG. 37, the delivery destination list includes the cargo No. of all cargo to be delivered for each delivery vehicle 110. 2910, a number 2920, a consignee name 2930, an address 2940, a telephone number 2950, and a delivery designated date 2960. The delivery destination list 2900 is used when a delivery person performs delivery and transportation of cargo. The delivery vehicle may be equipped with an existing car navigation system, and the delivery destination list 2900 may be output on the display screen of the car navigation system. When the processing apparatus 500 outputs the delivery destination list 2900, the processing ends (step 3947).

  On the other hand, when receiving the cargo passage information sent from the in-vehicle system 220 in step 3935, the intra-site cargo information management system 230 registers the cargo passage information in the cargo passage information DB 3300 in the same manner as steps 2875 and 2885 in unloading. (Step 3950), and transmitted to the freight information overall management system 245 via the inter-base network 260 at regular intervals (Step 3955).

  FIG. 38 is a flowchart showing a processing flow when checking unloaded cargo in the loading process 130. The processing device 700 of the intra-site cargo information management system 230 receives the unloading check start request and performs the following unloading check process.

  First, it is determined whether the work base is a store arrival or other base (step 4030). If the work base is not the arrival store, the processing device 700 reads the cargo No. of the record whose work classification 3340 is “unloading” from the cargo passage information DB 3300 stored in the storage device 710. 3310 is acquired. Subsequently, the freight number of the record whose work classification 3340 in the freight passage information DB 3300 is “loading”. 3310 is acquired. The processing device 700 compares the two, and the cargo number of the record whose work classification 3340 is “unloading” is displayed. 3310, the freight number of the record whose work classification 3340 is “loading”. Cargo No. not included in If there is 3310, the cargo No. Cargo No. To the output device 730 (step 4040).

  On the other hand, if the work base is the arrival store, the freight number of the record in which the work classification 3340 is “sort” and the storage classification 3380 is “pass” from the cargo passage information DB 3300. 3310, and all cargo numbers registered in the carry-out cargo information DB described later. To get. Next, the freight number of the record in which the work classification 3340 is “loading” from the freight passage information DB 3300. 3310 is acquired. The freight number of the record in which the work category 3340 is “sort” and the storage category 3380 is “pass”. 3310, and all cargo numbers registered in the carry-out cargo information DB described later. The cargo No. of the record in which the work classification 3340 is “loading”. If there is something that is not included in the Cargo No. To the output device 730 (step 4050).

  After the processing of Steps 4040 and 4050, the processing device 700 deletes all the information in the carry-out cargo information DB and the records already transmitted to the cargo information overall management system 245 from the records in the cargo passage information DB. (Step 4060).

  <6: Delivery Cargo Delivery> FIG. 39 is a flowchart showing the processing flow of the delivery cargo delivery process 136.

  In the delivery freight delivery 136, first, a delivery registration category is received from the input device 420 of the portable terminal system 215. If the cargo cannot be delivered due to reasons such as the absence of the consignee at the time of delivery of the cargo, “absence registration” is entered as the delivery registration category, and “delivery completion registration” is entered when delivery is performed. (Step 4110). When the delivery registration category is input, the processing device 400 uses the child tag reader / writer 440 to read the freight number from the electronic tag 370. , No. , Read collection request information, weight, electronic tag classification, charge. At this time, if the electronic tag classification is a multi-piece tag, the read content is discarded and information is read from another electronic tag 370 (step 4115). Next, the delivery registration classification input in step 4110 is discriminated. If it is delivery completion registration, the process proceeds to step 5215, and if it is absent registration, the process proceeds to step 4160.

  In step 4125, the content of the billing category in the collection request information read from the electronic tag 370 in step 4115 is further determined. If cash on delivery is set for the billing category, the process of step 4130 is performed as it is. If it is not cash on delivery, the process proceeds to step 4140.

  In step 4130, the processing apparatus 400 converts the fee read from the electronic tag 370 to the cargo number. At the same time, it is displayed on the output device 430. Subsequently, an input of a charge collection category is received from the input device 420. If the collection category is “completed”, the collection category information is updated using the collection category. Next, when the collection classification input in step 4130 is “completed”, the processing apparatus 400 sends the consignee name, billing classification, fee, transportation service contractor name, base name, person in charge name, delivery in the collection request information. A receipt describing the date and time, the sign field, etc. is output from the label printer 490. It is assumed that the transport service contractor name, base name, and person in charge name are registered in advance in the storage device 410 (step 4135).

  In step 4140, “delivery completed” is registered in the electronic tag 370 by the electronic tag reader / writer 440 as the person in charge, delivery date and time, and work classification. At this time, the processing apparatus 400 reads the cargo No. read in step 4115. Same cargo No. The same information is registered for the multi-port electronic tag 374 having. Cargo No. , No. The collection request information, the weight, the fee, and the delivery date and time registered in the electronic tag 370 are stored in the storage device 410.

  Next, processing device 400 checks whether a delivery completion registration end request has been input from input device 420. If there is no delivery completion registration end request, processing from step 4115 is repeated (step 4145). If an end request is input and entered, the cargo number stored in the storage device 410 is stored. , No. , Collection request information, weight, and fee are described only for the cargo delivered to the consignee, along with the receipt of the transportation service contractor name, base name, person in charge, delivery date, signature column, etc. The document and a copy thereof are output from the label printer 490. After the receipt is signed by the consignee, it is taken back by the person in charge and the copy is given to the shipper. (Step 4155).

  If the delivery registration classification input in step 4110 is “absence registration”, the processing apparatus 400 uses the electronic tag reader / writer 440 to indicate “absent” as the person in charge, the processing date and time, and the work classification in the electronic tag 370. sign up. At this time, in the same manner as in Step 4140, the same cargo No. The same information is also registered in the electronic tag 374 having “No.”, and the storage device 410 stores the processing date and time, the cargo number. , No. Information such as collection request information, weight, and fee is stored (step 4160).

  Next, the processing device 400 checks whether or not an absence registration end request is input from the input device 420. If there is no absence registration end request, the processing device 400 returns to step 4115 and repeats the absence registration processing for other cargo (step 4170). If there is an absence registration end request, the processing device 400 stores the freight number stored in the storage device 410. In the collection request information, the product name, quantity, and shipper name are written only for the delivery cargo, and the consignee name, transport service contractor name, base name, person in charge name, processing date and time, signature column, absence notice Etc. are output from the label printer 490. The absence slip is left behind in order to inform the consignee of the absence (step 4175).

  After outputting the receipt at step 4155 or outputting the absence slip at step 4175, the processing device 400 reads the cargo number stored in the storage device 410. Then, delivery registration information such as delivery (processing) date and time, work category, and collection category is transmitted to the delivery / storage freight management system 240 via the wireless communication device 480, and the process is terminated (step 4180). In the delivery / storage freight management system 240, the processing device 900 receives the delivery registration information transmitted from the portable terminal system 215 by the wireless communication device 940 and transmits it to the in-base cargo information management system 230 via the in-base network 255. (Step 4185). Further, the intra-site cargo information management system 230 transmits the received delivery registration information to the overall cargo information management system 245 via the inter-base network 260.

  <7: Storage> FIG. 40 is a flowchart of processing performed when cargo is brought into the storage location in the storage processing 138.

  When cargo is brought into the storage location, the person in charge No. is entered from the input device 920 of the delivery / storage cargo management system 240. The site name is input and stored in the storage device 510 (step 4205). The processing device 900 of the delivery / storage freight management system 240 uses an electronic tag reader / writer 950 installed in the vicinity of the entrance of the storage location. When the cargo is put into the storage location, the electronic tag 370 of the cargo that passes by it is used. Cargo No. , No. Read. At this time, the processing apparatus 900 writes the date and time as the warehousing date and time for the electronic tag 370. If the warehousing date is already recorded in the electronic tag 370, the warehousing date is not registered. The processing apparatus 900 is a cargo No. , No. At the same time, the base name stored in the storage device 910 in advance, the name of the person in charge input in step 4205, and “storage” as the work classification are transmitted to the intra-base cargo information management system 230 as the cargo passage information, and the processing is terminated. To do.

  In the base cargo information management system 230, when the cargo passage information transmitted from the delivery / storage cargo management system 240 is received, the cargo passage information is registered in the cargo passage information DB 3300 by the processing device 700 as in step 2875. (Step 4220). Then, the information registered in the cargo passage information DB 3300 is transmitted to the cargo information overall management system 245 via the inter-base network 260 at regular intervals (step 7230).

  FIG. 41 shows a process executed by the delivery / storage freight management system 240 and the intra-site freight information system 230 when a stored cargo take-out instruction and a long-term storage cargo alarm are output. It is a flowchart.

  The process shown in FIG. 41 is started when a storage cargo handling request is input from the input device 920. The stored cargo response request confirms the presence of a cargo that has been stored for a period of time longer than a predetermined period, and a carry-out cargo instruction for instructing a cargo to be loaded on the delivery vehicle 110 from among the stored cargo. There is a long-term storage freight notification instruction (step 4310).

  When the stored cargo handling request is input, the processing device 900 uses the electronic tag reader / writer 950 installed in the storage location to store the cargo number recorded in the electronic tag 370 attached to the stored cargo. , No. The delivery designated date and time and the warehousing date and time are read (step 43230). The processing device 900 creates a storage cargo location DB based on the read information and stores it in the storage device 910. As shown in FIG. 42, the storage freight location DB stores the freight number as information. 4410, piece number 4420, delivery specified date 4430, warehousing date 4440, and location information 4450 indicating the approximate position of the corresponding cargo at the storage location. The location information 4450 includes, for example, one or more electronic tag reader / writers 950 moved within the storage location, and the reading time and the cargo number read from the electronic tag 370. Or an electronic tag reader / writer is installed for each location. (Step 4330).

  Next, the processing apparatus 900 determines the type of the stored freight handling request input at step 4310 (step 4340). If the storage cargo handling request is a long-term storage cargo notification instruction, the processing apparatus 900 extracts a record having data that has passed a preset period from the date and time set in the storage date and time 4440 from the storage cargo location DB 4400. To do. And the cargo number in the extracted record. 4410; 4420 and the location 4450 are output to the output device 930 as long-term storage cargo information, and the process is terminated (step 4350). On the other hand, if the storage cargo handling request is a carry-out cargo instruction, delivery time zone information including a scheduled delivery start date and a scheduled delivery end date is received from the input device 920. The processing apparatus 900 extracts from the storage freight location information DB 4400 a record in which the value set for the designated delivery date / time is between the scheduled delivery start date / time and the scheduled delivery end date / time of the delivery time zone information received here. And the cargo No. of the retrieved record is displayed. 4410; 4420 and the location information 4450 are output to the output device 930 and the cargo number. 4410; 4420 is sent to the in-base freight information system 230 as carry-out freight information, and the process is terminated (step 4360). In the base cargo information system 230, the carry-out cargo information sent from the delivery / storage cargo management system 240 is stored in the carry-out cargo DB stored in the storage device 710. As shown in FIG. 4510 and the number No. It consists of a list of 4520 (step 4370).

  <8: Cargo Information Management> FIG. 44 is a flowchart showing the process flow of the cargo information management process 168.

  When the freight information overall management system 245 receives the passing freight information from the in-base freight information management system 230 (step 4602), the freight history related data is registered in the freight transport history DB. As shown in FIG. Each pass point, base name, work classification there, passage date and time, person in charge of the work, and flight name of the vehicle involved in the work are held (step 4604). The processing apparatus 1100 refers to the freight transportation history DB 4800 and sets the freight number. The following processing is performed every time. First, the latest work category registered in the freight transportation history is checked. If it is a pickup, the process proceeds to step 4608, and if not, the process proceeds to step 4622 (step 4606).

  If the latest work classification is collection, cargo attribute information necessary for cargo management is registered in the cargo attribute DB at this stage. In the cargo attribute DB, various information shown in FIG. (Step 4608). Subsequently, the store name for the information related to the delivery destination in the cargo attribute DB 4700 is searched with reference to the store / departure area information DB. In the arrival / departure area information DB, as shown in FIG. 47, for each location (arrival / departure) 5010, a district area 5020 in which the location is responsible for arrival or departure is registered. Based on the arrival store name obtained here and the departure store name obtained from the cargo attribute information 4700, the transport route pattern DB 3100 stored in the storage device 1110 is searched to extract the transport route. The processing apparatus 1100 registers the extracted transportation route in the transportation route schedule DB. As shown in FIG. 48, the transportation route schedule DB 4900 includes the cargo No. For each, a base division 4910, an arrival base name 4920 corresponding to the base division, and a scheduled arrival date and time 4930 at the arrival base are held. Of the information in the transportation route schedule DB 4900, the estimated arrival date and time 4930 is obtained and registered / updated by the arrival / delivery scheduled date and time calculation process in step 4612 when the collection process or the loading process is completed. Step 4610).

  In step 4612, the processing apparatus 1100 calculates the estimated arrival date and time at each base and delivery destination. FIG. 49 shows a flowchart of the process for calculating the estimated arrival date and time.

  In the process of calculating the estimated arrival date and time, first, the passing point of the latest history data (data at the end of the history data) is obtained as the current base u based on the cargo transportation history DB 4800 (step 5240). The processing device 1100 extracts the next base of the current base u from the transport route schedule DB 4900, and specifies the shift master DB of the transport flights from the current base u to the next base v. As shown in FIG. 50, the transport flight shift master DB 5300 includes a transport flight shift 5310 for each route, a base departure time 5320 for each transport flight shift, and an arrival time 5330 for the next base for each route from the base to the base. It is registered. Next, the processing device 1100 extracts the nearest transport flight shift that can be departed in the future from the identified transit flight master DB 5300 and the passage date and time of the latest history data, and based on the arrival time of the transit flight shift, The estimated arrival date and time at the base v is obtained (step 5242).

  Subsequently, it is determined whether or not the next base v is a delivery destination. If the next base v is a delivery destination, the calculation process of the estimated arrival date and time is ended (step 5244).

  If the next base v is not a delivery destination, the processing device 1100 performs a series of operations including unloading, sorting, and loading the earliest from the work shift master DB of the base v using the estimated arrival date and time obtained earlier. Extract work shifts that can be started. As shown in FIG. 51, each work shift 5410, and each work shift start time 5420 and end time 5430 are registered in the work shift master DB 5400. Based on the extracted work shift end time 5430, the processing device 1100 refers to the transport flight shift master DB 5300 of the transport flight from the base v to the next base w and returns to the base w in the same manner as Step 5242. Is calculated (step 5246).

  Next, the processing apparatus 1100 checks whether the base w is a delivery destination, and if it is a delivery destination, ends this processing (step 5248). If the base w is not a delivery destination, the base v is replaced with the base w (step 5250), and the process returns to step 5246 to calculate the estimated arrival date and time at the next base.

  When the calculation of the estimated arrival date / time is completed, the processing device 1100 compares the calculated estimated arrival date / time with the estimated arrival date / time registered in the transportation route schedule DB 4900 (step 4614). If the two match, the cargo has been transported as scheduled, and the processing ends. If they are different, the transportation schedule is off. In this case, the processing device 1100 calculates the estimated arrival date and time 4930 of the base (or the consignee) where the calculated estimated arrival date and time and the estimated arrival date and time registered in the transportation route schedule DB 4900 are different. Update. Note that when the collection information is confirmed, the scheduled arrival date and time are registered for the first time, and all the estimated arrival dates and times calculated for each base are registered (step 4616).

When the scheduled arrival date (delivery) to the consignee destination is changed, the processing device 1100 notifies the consignee destination cargo information system 250 of the new scheduled date of arrival (delivery). The corresponding consignee destination cargo information system 250 is identified from the electronic address corresponding to the delivery destination in the cargo attribute DB 4700 (step 4618). If there is a base whose scheduled arrival date / time has been changed, the processing apparatus 1100 displays the cargo number of the corresponding cargo. At the same time, the new arrival date and time is notified to the intra-site cargo information management system 230 as the expected arrival cargo information (step 4620).
In step 4622, the latest work section is checked, and if it is loading, the process proceeds to step 4614, and the process from step 4614 is performed in the same manner as in the case where the work section is collection. If the work section is not loaded, it is further determined whether or not the latest work section is delivery completed. (Step 4624).

  If the work classification is delivery completion, the processing device 1100 notifies the shipper destination cargo information management system of delivery completion information including the image information of the judgment piece, delivery destination, delivery date and time, product name, fee, etc. The processing is terminated (step 4626).

  If the work category is not completed in step 4624, it is further checked whether or not the latest work category is absent. If the work category is not absent, the process is terminated (step 4628). On the other hand, if the work classification is absent, the processing device 1100 transmits information on the consignee information, product name, absence confirmation date / time and the like, the desired delivery destination, and date / time inquiry to the consignee cargo information system 250 for processing. Finish (step 4630).

  Here, the arrival / delivery scheduled date and time are calculated and recalculated at the completion of the collection process or loading process, but in order to realize precise transportation tracking, the unloading process and the sorting process are also completed. Recalculation of arrival / delivery scheduled date and time may be performed.

  <9: Delivery Destination / Date Change Request and Response> FIG. 52 is a flowchart showing the processing flow of the delivery destination / date change request processing 162 and the delivery destination / date change processing 164. In this process, when there is a delivery destination / date change request from the consignee destination cargo information system 250 in response to the scheduled delivery cargo information notification or absence notification from the cargo information overall management system 245, the entire cargo information is sent. The management system 245 calculates the estimated arrival date and time for the change request, and if the change is accepted, notifies the change information to the in-base freight information management system 230 and the consignee destination freight information system 250. If the change is not accepted, the non-change information is notified to the consignee cargo information system 250.

  In the consignee destination cargo information management system 250, when the consignee is instructed to change the delivery destination or date / time in response to the scheduled delivery cargo information notification or absence notification received from the overall cargo information management system 245, the delivery destination change request or The delivery date change request is sent to the cargo number. The information is transmitted to the cargo information overall management system 245 in units (step 5610).

  When the freight information overall management system 245 receives the delivery destination change request or the delivery date change request sent from the consignee destination freight information management system 245 (step 5812), the processing device 1100 displays the change contents of the corresponding cargo. In order to write in the electronic tag 370, the base r where the information of the electronic tag 370 can be updated earliest is extracted. Specifically, the passing point name and the work classification are extracted from the latest history data in the cargo transportation history DB 4800. If the work classification is completion of loading, it can be regarded as being transported. Therefore, the processing apparatus 1100 obtains the next arrival base as the base r. This base is obtained as a next arrival base by referring to the transportation route schedule DB 4900, searching for the passing point name extracted from the cargo transportation history DB 4800. On the other hand, if the work classification is completion of unloading or sorting, the corresponding cargo is in one of the bases, and this base becomes a passing point extracted from the freight transportation history DB 4800 (step 5614).

Next, the processing device 1100 examines the contents of the change request, and if only the delivery date / time change request is entered, the processing device 1100 moves to the processing of step 5636, and only the delivery destination change request or both the delivery destination and delivery date / time change requests are received. If there is, the process proceeds to step 5618 (step 5616).
When there is only a delivery destination change request or when there is a change request for both the delivery destination and the delivery date, the processing device 1100 searches the arrival / departure area information DB 5000 based on the address information of the change request delivery destination, and changes delivery. The base P in charge of the previous area is extracted as a new store. Next, the processing apparatus 1100 searches the transport route pattern DB 3100 based on the base r and the base P, and determines a transport route from the base r to the delivery destination that requested the change. Specifically, it is determined as follows according to the site classification of the site r.

(1) When the base r is a store opening In this case, the transportation route from the base r to the change request delivery destination is determined in the same manner as a normal transportation route.

(2) When the base r is the originating relay store or the arrival relay store In this case, the processing device 1100 searches the transport route pattern DB 3100 for an entry whose destination store name 3120 is the base P, and the base r is in the transport route. Extract included transportation route patterns. Then, using the transport route from the base r to the base P in the extracted transport route pattern, the transport route to the change request delivery destination is determined.

(3) When the base r is the arrival store In this case, it corresponds to the state where the delivery to the arrival store is in progress, the delivery is in the arrival store and delivery has not been completed yet, or delivery has not been possible due to the absence of the consignee. . In this case, the transport route to the change request delivery destination is determined in the same manner as the normal transport route, starting from the arrival store (base r) before the change request.

  The processing apparatus 1100 temporarily stores the new transport route obtained as described above (step 5618).

  The processing apparatus 1100 calculates the scheduled arrival date and time of the cargo at each base and the changed consignee for the determined new transportation route by the same processing as described in FIG. 49 (step 5620).

  Next, the processing device 1100 notifies the consignee destination cargo information management system 250 of whether or not delivery can be performed at the delivery date and time designated by the delivery date and time change request. Here, it is checked whether or not the delivery date and time designated by the delivery date and time change request is later than the scheduled arrival date and time of the cargo to the consignee determined in step 5620. If the requested delivery date and time is earlier than the estimated arrival date and time, the processing device 1100 ends the processing because it cannot respond to the delivery date and time change request. At this time, along with the inability to respond, information for requesting a change in delivery date is transmitted to the consignee cargo information system 250. If there is no delivery date change request, the process proceeds to the next step 5625 (step 5622).

  In step 5625, the changed delivery destination and the new scheduled delivery date and time ((if there is no delivery date change request, the scheduled delivery date and time calculated in step 5620; if there is a delivery date change request, the requested delivery date and time The reply information including) is transmitted to the consignee destination cargo information system 250.

  Next, the processing apparatus 1100 compares the new transportation route determined in Step 5618 with the transportation route before the change registered in the transportation route schedule DB 4900, and is added to the base common to both of them and the new transportation route. Identify locations that have been removed and removed from the transport route. At this time, the location r is instructed to write the delivery information (name, address, e-mail, etc.) after the change to the electronic tag 370 of the corresponding cargo and the requested delivery date and time (if requested). (Step 5626).

  Subsequently, the processing apparatus 1100 sends the corresponding cargo number to the cargo information management system 230 in the site newly added to the transportation route. And the arrival date and time are notified (step 5630). Furthermore, for the bases removed from the transportation route, the cargo number of the corresponding cargo is displayed. At the same time, passage cancellation information indicating that the cargo has stopped passing due to the change of the transportation route is sent (step 5632).

  After the above processing, the processing apparatus 1100 deletes the information in the transportation route schedule DB 4900 related to the bases removed from the transportation route, the bases after the base r that are included in the new transportation route, and newly The calculated arrival date and time of the cargo to those bases is registered in the transportation route schedule DB 4900. Also, the changed information in the cargo attribute information DB 4700 is updated and the process is terminated (step 5634).

  On the other hand, if it is determined in step 5616 that only the delivery date / time change request is requested, the processing device 1100 determines whether or not the requested delivery date / time can be accommodated. In this case, since the scheduled arrival date and time to the consignee destination registered in the transportation route schedule DB 4900 is the scheduled arrival date and time in the shortest schedule, the delivery date and time specified by the delivery date change request is stored in the transportation route schedule DB 4900. It is checked whether or not it is later than the scheduled date and time of arrival at the registered consignee. If the requested delivery date and time is earlier than the estimated arrival date and time, the processing device 1100 ends the processing because it cannot respond to the delivery date and time change request. At this time, along with the inability to respond, information for requesting a change in delivery date and time is transmitted to the consignee cargo information system 250 (step 5636). When it is possible to respond to the delivery date change request, the processing device 1100 sends the cargo number of the corresponding cargo to the consignee cargo information management system 250. Response information including the date and time designated in the delivery date and time change request is transmitted as the estimated arrival date and time (step 5640).

  Next, the processing device 1100 notifies the base r of the change of the scheduled delivery date and instructs the writing of the changed delivery date to the electronic tag 370 of the corresponding cargo (step 5642). Thereafter, the processing apparatus 1100 updates the scheduled arrival date and time to the consignee destination in the transportation route schedule DB 4900 and the desired delivery date and time in the cargo attribute information DB 4700 with the requested delivery date and time, and ends the processing (step 5644).

  In the consignee destination freight information management system 250, when the reply information sent from the freight information overall management system 245 is received, the consignee confirms the reply to the change request (step 5624). Further, in the base cargo information management system 230, when the information sent from the cargo information overall management system 245 is received, the following processing is performed. When the base is the base r, based on the received information, delivery destination / date / time change information relating to the corresponding cargo is created and registered in the delivery destination / date / time change information DB 3000. At a base newly added to the transportation route, a cargo No. as a newly scheduled cargo arrives based on the received information. And the estimated arrival date and time are registered. In addition, the registration of the scheduled arrival cargo is deleted at the base removed from the transportation route (step 5627).

  <10: Cargo Information Provision and Inquiry> FIG. 53 is a flowchart showing the process flow of the cargo information provision processing 158 and the cargo information inquiry processing.

  When the consignee destination freight information system 250, the consignee destination freight information system 210, or the in-base freight information management system 230 receives a freight information inquiry request, it transmits the inquiry request to the freight information overall management system 245. (Step 5710).

  When the freight information overall management system 245 receives the freight information inquiry request (step 5720), the freight information plan DB 4900 and the freight transportation history DB 4800 are searched according to the contents of the received inquiry request, and information that becomes a reply to the inquiry is obtained. Extract. For example, in response to an inquiry about the scheduled delivery date and time of the cargo from the consignee, the transport route schedule DB 4900 may be searched to extract the arrival date and time of the corresponding cargo to the consignee. In response to the inquiry about the current cargo position, the cargo transportation history DB 4800 is searched to extract the latest information on the corresponding cargo. Further, if there is an inquiry about the person in charge for each work category, the flight name of the transportation means, etc. for troubleshooting at the base, the freight transportation history DB 4800 can be searched to obtain necessary information. When the inquiry is made based on the cargo attribute of the consignee or the like, the cargo attribute DB 4700 is searched using the information specified in the inquiry to check the cargo No. And the acquired cargo No. Thus, a search is performed (step 5730). The information acquired in step 5730 is transmitted to the consignee destination cargo information system 250, the sender destination cargo information system 210, or the in-site cargo information management system 230 (step 5740).

When the consignee destination freight information system 250, the consignee destination freight information system 210, and the in-base freight information management system 230 receive a response to the inquiry from the freight information overall management system 245, the contents are output to the output devices 330, 730, and 1030. (Step 5750)
<11: Unarrival Cargo Check> FIG. 54 is a flowchart showing the process flow of the non-arrival cargo check processing 132.

  In the base cargo information management system 230, when the arrival cargo information is received from the overall cargo information management system 245, the arrival cargo information sent by the processing device 700 is stored in the arrival arrival cargo information DB in the storage device 710. . As shown in FIG. 55, the arrival arrival cargo information DB 6000 contains the cargo No. of the cargo scheduled to arrive. 6210 and the date and time 6220 scheduled for arrival of the cargo are included as information (step 6110).

  When a request for unarrived cargo check is input from the input device 720, the processing device 700 checks for unarrived cargo. Specifically, the processing device 700 stores the freight No. of the record in which the date and time before the current time is registered in the estimated arrival date and time 6220 from the expected arrival cargo information DB 6000. 6210 is acquired. Next, the processing measure 700 extracts a record in which “unloading” is registered in the work category 3340 from the cargo passage information DB 3300 in the storage device 710, and the cargo No. 3310 is acquired. The processing device 700 receives the cargo No. acquired from the scheduled arrival cargo information DB 6000 and the cargo passage information DB 3300. The cargo No. obtained from the arrival arrival cargo information DB 6000 is compared. The cargo No. acquired from the cargo passage information DB 3300. Extract those that are not included. Cargo No. extracted here. If there is, the processing device 700 will send the cargo number. No. Hold as. At this time, the cargo No. acquired from the cargo passage information DB 3300 is displayed. Is Cargo No. The record of the arrival arrival cargo information DB 6000 registered in 6220 is deleted.

  Next, the processing apparatus 700 receives the unarrival cargo No. Is determined to determine whether there is a non-arrival cargo No. If there is not, the process is terminated (step 6130). Unarrived cargo No. In the case where there is a cargo number No. Is sent to the freight information overall management system 245 via the inter-base network 260 and the processing is completed (step 6140).

  When the cargo information overall management system 245 receives a request for unarrived cargo search from the intra-site cargo information management system 230, the processing device 1100 causes the undelivered cargo No. Cargo No. sent as Is used as a key to search the cargo transportation history DB 4800 stored in the storage device 1110, and the corresponding cargo No. The base name recorded in the final history is extracted from the transportation history information. And, from this cargo attribute information DB 4700, this cargo No. The cargo attribute information is retrieved. The processing apparatus 1100 includes the cargo attribute information and the cargo number. Is sent to the intra-base cargo information management system 230 with the base name extracted previously (step 6150).

  In the in-base freight information management system 230 that has received a request for unarrived cargo search from the overall cargo information management system 245, the cargo No. included in the unarrived cargo search request that has been sent. The cargo attribute information of the cargo is output to the output device 730 as search target cargo information (step 6160).

  <12: Individual Cargo Information Confirmation> The individual cargo information confirmation processing 166 is performed using the portable terminal system 215. The individual cargo information confirmation processing 166 is performed for confirmation of cargo information at each base, for example. In this process, the information held in the electronic tag 370 attached to the cargo to be confirmed is read by the electronic tag reader / writer 440 of the portable terminal system 215, and the cargo attribute information such as the product name included in the collection request information. The passage base, the worker, the passage date and time, etc., included in the consignor information, the consignee information, or the cargo passage history information are output to the output device 430.

  FIG. 56 is a flowchart of processing performed by the mobile terminal system 215 when searching for cargo that is performed based on an unarrived cargo search request.

  The cargo number of the unarrived cargo notified to the intra-base cargo information management system 230 in the unarrived cargo search request. Is input to the input device 420, and the processing device 400 receives the cargo No. Is acquired (step 6410).

  Next, the processing apparatus 400 uses the electronic tag reader / writer 440 to store the cargo number stored in the electronic tag 370. Is read (step 6420). The processing device 400 receives the cargo NO. Cargo No. read from the electronic tag 370. Are compared to see if they match (step 6430). If the two do not match, the process returns to step 6420 and the cargo number of another cargo is set. Is read and the same processing is repeated. On the other hand, if the two match, the processing device 400 has the freight number. Is output to the output device 430, and the discovery of the corresponding cargo is notified (step 6440).

  Thereafter, the processing device 400 determines whether or not a work end request has been input from the input device 420. If there is a work end request, the processing device 400 ends the process. If the work end request is received, the processing device 400 returns to the process of step 4620 (step 6450). ).

  Here, the cargo No. Searching for the cargo corresponding to the key, the cargo No. The search can be performed in the same manner using other information such as the product name and consignee name as keys.

  According to the embodiment described above, in the freight transportation, the information recorded in the electronic tag is effectively used, and the freight including the special freight handling such as the delivery destination / date / time change request, the freight, the precision machine, etc. It is possible to realize a managed freight management system that enables efficient handling. In addition, it is possible to realize a managed cargo management system that can promptly respond to irregular situations such as erroneous arrival, erroneous loading, unloading, unloading, and overloading.

It should be noted that the present invention is not limited to the above-described embodiment, and can take various forms within the scope of the gist of the present invention. For example, in the above embodiment, the unloading and loading processing of the transported cargo at each site is performed in cooperation with the in-vehicle system installed in the vehicle and the in-site cargo information management system. A system having the same function as the above-described on-vehicle system may be fixedly provided in the base.

It is a conceptual diagram which shows the function of the consolidated freight transportation service by one Embodiment of this invention, and the whole flow. It is a block diagram which shows the whole structure of the consolidated cargo transportation service system by one Embodiment of this invention. It is a block diagram which shows the structure of a consignor destination cargo information system. It is a block diagram which shows the structure of a portable terminal system. It is a block diagram which shows the structure of a vehicle-mounted system. It is a block diagram which shows the structure of a collection management system. It is a block diagram which shows the structure of the cargo information management system in a base. It is a block diagram which shows the structure of an automatic sorting system. It is a block diagram which shows the structure of a delivery / storage freight management system. It is a block diagram which shows the structure of a consignee destination cargo information system. It is a block diagram which shows the structure of the cargo information whole management system. It is the flowchart which showed the processing flow of the collection request process and the request reception process. It is a data block diagram of collection request information. It is a data block diagram of collection person in charge DB classified by time zone / area. It is a detailed flowchart of an order information registration process. It is a data block diagram of person in charge-DB corresponding to portable terminals. It is a data block diagram of arrival name DB classified by address. It is a flowchart which shows the processing flow of collection cargo reception processing. It is a conceptual diagram which shows the mode of the information stored in an IC card. It is a flowchart which shows the detailed process of a charge calculation process. It is a data block diagram of fixed price structure DB. It is a data block diagram of incidental service charge system DB. It is a data block diagram of transport distance calculation DB. It is a data block diagram of metered rate system DB. It is a detailed flowchart of registration processing of collection information. It is a flowchart of the process implemented by the vehicle-mounted system and the cargo information management system in a base in the case of an unloading process. It is a data block diagram of a delivery destination / date change cargo DB. It is a data block diagram of transport route pattern DB. It is a data block diagram of piece quantity cargo information DB. It is a data block diagram of cargo passage information DB. It is a flowchart of the process implemented by the automatic sorting system and the cargo information management system in a base in the case of a sorting process. It is a detailed flowchart of the sorting instruction according to destination. It is a data block diagram of sorting DB classified by arrival store. It is a data block diagram of DB corresponding to a sorting time zone-delivery end time. It is a data block diagram of sorting mouth DB classified by address. It is a flowchart which shows the process flow in a loading process. It is a block diagram of a delivery destination list. It is a flowchart which shows the processing flow at the time of checking unloading cargo in loading processing. It is the flowchart which showed the processing flow of the delivery cargo delivery process. It is a flowchart of the storage process implemented when a cargo is brought into a storage place. It is a flowchart of the process performed when the take-out instruction | indication of the stored cargo and a long-term storage cargo alarm are output. It is a data block diagram of storage cargo location DB. It is a data block diagram of carrying-out cargo DB. It is a flowchart which shows the processing flow of a cargo information management process. It is a data block diagram of freight transportation history DB. It is a data block diagram of cargo attribute DB. It is a data block diagram of arrival / departure area information DB. It is a data block diagram of transportation route plan DB. It is a flowchart of the calculation process of arrival arrival scheduled date. It is a data block diagram of shift master DB of a transport flight. It is a data block diagram of work shift master DB. It is the flowchart which showed the processing flow of the delivery destination / date change request process and the delivery destination / date change processing. It is the flowchart which showed the processing flow of the cargo information provision process and the cargo information inquiry process. 7 is a flowchart showing a processing flow of unarrived cargo check processing 132; It is a data block diagram of arrival schedule cargo information DB. It is a flowchart of the process implemented by the portable terminal system in the case of a cargo search.

Explanation of symbols

210 ... Shipper's destination cargo information management system 215 ... Mobile terminal system 220 ... In-vehicle system 225 ... Collection management system 230 ... Cargo information management system in base 235 ... Automatic sorting system 240 ... delivery / storage freight management system 245 ... freight information overall management system 250 ... consignee destination freight information management system 255 ... intra-base network 260 ... inter-base network 265 ... external network

Claims (4)

A delivery system in which a delivery system information management device is connected to a delivery system that is provided at a plurality of locations where a delivery product with an IC tag in which delivery route information to the delivery location to the first store is stored is distributed. A management system,
Change request information for changing the arrival store from the first arrival store to the second arrival store, the receiving unit receiving change request information on arrival stores related to the base that will be the second arrival store,
Writing an information about the locations to which the shipping articles has passed, and information identifying the locations, based on the delivery record information with a working classification information in the site, the earliest IC tag the change request information after receiving Extract possible bases,
The delivery route information after the change from the extracted base to the base that becomes the second arrival store is stored in the storage unit in advance, and the base of the delivery route is determined for each combination of the two bases A processing unit to extract from the table;
A transmission unit that transmits the extracted delivery route information after the change to the base system of the base that can be written to the IC tag earliest after receiving the change request information;
A delivery information management device comprising:
A receiving unit for receiving the changed delivery route information transmitted;
A write processing unit that writes the received delivery route information after the change to the IC tag;
A base system having
A delivery management system comprising: In the delivery information management apparatus according to claim 1 ,
The work classification information is one of a collection flag, an unloading flag, a sorting flag, and a loading flag, and the flag indicates whether the last base is a base that can be written to the IC tag. A delivery management system comprising a delivery product information management device characterized in that a base that can be written to the IC tag earliest is extracted by determining . A base system provided in a base where a delivery product having an IC tag in which delivery route information to a base where the first store arrives is stored is distributed, and a delivery information management apparatus connected to the base system A delivery management method in a delivery management system comprising:
The freight information management center receives change request information for changing the arrival store from the first arrival store to the second arrival store, the change request information for the arrival location relating to the base that is the second arrival store. And
Based on the delivery history information of the product, the information identifying the base and the work history information at the base, the change request information can be written to the IC tag as soon as possible after receiving the change request information. Extract bases,
The delivery route information from the extracted base to the base that becomes the second destination after the change is stored in the storage unit in advance, and the correspondence table in which the base of the delivery route is determined for each combination of the two bases Extracted from
The extracted route information after the change is sent to the base that can write to the IC tag as soon as possible after receiving the change request information.
The site system of the site that can be written to the IC tag earliest after receiving the change request information receives the transmitted delivery route information after the change,
A delivery management method, wherein the received route information is written in the IC tag. In the delivery management method according to claim 3 ,
The work classification information is one of a collection flag, an unloading flag, a sorting flag, and a loading flag, and the flag indicates whether the last base is a base that can be written to the IC tag. A delivery management method comprising: extracting a base that can be written to the IC tag earliest by determining.

Images