JP5916905B1 - Transportation status collective management search system and program - Google Patents

Abstract

Provided is a server system that collectively manages and searches a transport status from collection of a transported cargo of a user to completion of delivery when a user is provided with an inter-company transport service, an external transport service, or a collection transport service. A trace database, a user management information storage unit, a group information storage unit, a search unit that searches and extracts a trace record of a transported cargo collected on the collection date from the trace database, and The server 2 includes a totaling unit 14 that totals the undelivered state of the transported cargo collected on the collection date for each group unit, and an editing unit 15 that edits the transport status collective management information. [Selection] Figure 4

Description

  The present invention, for example, for a user who has a branch / branch or office in the whole country, from the collection of all the cargos shipped from the branch / branch or office in the country based on a collection / delivery request from the user to the completion of delivery. The present invention relates to a transportation status collective management search system and program for providing a user with information that enables a collective management search in real time by a simple operation.

  Conventionally, for the shipper who requested delivery of cargo (hereinafter also referred to as “user”), the collection / delivery progress information of each stage from the collection of the cargo to the completion of delivery, for example, via the Internet via a personal computer or tablet terminal A service that can be inquired from a terminal such as the above is provided to users (for example, Patent Document 1 and Patent Document 2).

In recent years, as shown in FIG. 1, various services for collecting and sending a large amount of transportation cargo from a user, for example, collecting transportation cargo collected from a user's head office, branch / branch office, or office at the user's head office, A service that transports them to the user's head office, branch / branch or office (hereinafter referred to as “in-house transport service”), and transport cargo collected from the user's branch / branch or office is a user's customer at random. A service for transporting to a delivery destination (hereinafter referred to as “external transport service”) or a service for transporting a transported cargo collected from a collection destination that is a customer of a user to a delivery destination such as a factory (hereinafter referred to as “collection”). Transportation services ”are provided.
However, even in this case, there is still a service for inquiring the user about the transportation status of the collection / delivery process from collection to delivery completion for each individual transportation cargo unit from the terminal such as a personal computer or a tablet terminal via the Internet. It is only provided.

The conventional service only provides a search service of the transport status by the invoice number of each transport cargo. For example, transport collected from the user's headquarters, branch / branch office, or office, such as inter-company transport service. When transporting a large quantity of cargo, for example, several hundred shipments every day, to which the cargo is transported to the user's headquarters, branch / branch office, or office, the user is transported from which branch / branch to what extent. In addition, it is difficult to collectively manage the delivery process of transported cargo that is collected, loaded, and delivered at each branch / branch.
For this reason, for example, when the transport cargo from the A branch has been delivered to the head office, but the transport cargo from another nearby B branch has not yet been delivered to the head office, etc. There are many cases where the collection and delivery process of the collected cargo is inquired by telephone.

JP 2004-244223 A JP 2011-118594 A

For services such as the above, the schedule of the processing cycle in which the transported cargo is collected at the user's head office, branch, branch office, office, etc., loaded into the transport vehicle, and delivered to the destination is generally established. There are many. For example, branches, branch offices, and offices in area A collect almost every day at around 6:00 pm, load transported cargo at around 7:00 pm the next morning, and deliveries around 9:00 am. There are many. Therefore, for example, if the number of completed deliveries at branch offices / branches / offices in area A is zero after 9 am, there may be some irregular circumstances (for example, an accident). is there.
In conventional search inquiries in units of invoices, it has been difficult to determine, for example, which region or which branch / branch / office has an irregular case.

  The present invention has been made in view of such problems. The present invention is based on a collection / delivery request from a user when providing, for example, the above-mentioned intra-company transportation service, external transportation service, or collection transportation service to a user who has branches / branches or offices throughout the country. To provide users with information that can be managed and searched in real-time in a simple operation for the transportation status from the collection to the completion of delivery of all transported cargo shipped from the customer's branch / branch office, business office or user's customer An object is to provide a system and a program.

  (1) The present invention is a server that is communicably connected to a terminal via a communication network, and the server collects a transportation cargo by the transportation company with respect to the transportation cargo handled by the communication unit and the transportation company. Sometimes, at least when loading a transport freight delivery vehicle, it will be registered to register the invoice number, collection date, collection time, number of collections, shipper information, shipper information to identify the waybill. Registration of the scheduled delivery time for registering the processing date, loading time, and the number of loaded items, and completion of delivery for registering at least the delivery date, the delivery time, and the number of items to be delivered when completing the delivery of the transportation cargo. To store a trace record that centrally registers and manages the passing records of each stage of transportation from the collection to the completion of delivery at the departure point of all transported cargo Race database and in-house transportation service in which the carrier collects and delivers transportation cargo for a given user between the user's head office and a plurality of branches, branch offices, offices, or group companies The user's headquarters, multiple branches, branch offices, offices, or group companies that collect transportation cargo and deliver it to an outside consignee, or the user In the case of carrying out a collection transportation service that collects transportation cargo from the user's business partner or group company according to an instruction from the user and delivers it to a predetermined destination, the inter-company transportation service, the outside transportation service, or the collection For each service of the transport service, the user identification information of the user and the shipper code as a billing destination for the transport freight charge are linked in advance. A user management information storage unit for storing information, and a user management information storage unit for a transportation status search request including a collection date of transported cargo handled by the inter-company transport service, the external transport service, or the collection transport service Among all the transport cargoes whose shipper is the shipper code associated with the user identification information stored in the search database, and search and extract the trace records of the transport cargo collected on the pickup date from the trace database. The search unit and the trace record extracted by the search unit as an input, the undelivered state of the transported cargo collected on the collection date is classified by the predetermined unit of the origin, by the predetermined unit of the landing, or the A totaling unit that creates totaled information for each predetermined unit of departure / landing consisting of an arbitrary combination of a predetermined unit of departure and a predetermined unit of landing; The totaling unit counts the predetermined unit of the departure, the predetermined unit of the landing, or the predetermined unit of the departure / landing including any combination of the predetermined unit of the departure and the predetermined unit of the landing. Based on the aggregate information on the undelivered status of the transported cargo collected on the date of collection, the transport status collective management information in a preset format is edited. Edit the predetermined unit of the ground, the predetermined unit of the landing, or the predetermined unit of the landing and the landing, which is an arbitrary combination of the predetermined unit of the landing and the predetermined unit of the landing, into a preset alert display format The place of departure / landing, which is edited in the transportation status collective management information, and includes a predetermined unit of the departure, a predetermined unit of the landing, or an arbitrary combination of the predetermined unit of the departure and the predetermined unit of the landing A trace record of the transport cargo collected on the date of collection with the unit as the origin or the landing is a predetermined unit of the origin, the predetermined unit of the landing, or any of the predetermined unit of the origin and the predetermined unit of the landing An editing unit that links to a predetermined unit of departure / landing made of a combination, and transmits the transport status batch management information edited by the editing unit to the terminal via the communication unit.

  (2) The counting unit receives the trace record extracted by the search unit as an input, for each predetermined unit of the departure, for each predetermined unit of the landing, or for each predetermined unit of the departure and the predetermined unit of the landing Including a tabular totaling unit that counts the number of picked up, loaded and delivered items of the transported cargo for each predetermined unit of departure / landing consisting of any combination of the above, and the editing unit includes the tabular totaling unit For each of the transport cargoes compiled by the predetermined unit of the departure, by the predetermined unit of the landing, or by the predetermined unit of the departure / landing consisting of any combination of the predetermined unit of the departure and the predetermined unit of the landing The number of pickups, loadings, and deliveries is edited into tabular data with either the predetermined unit of origin or the predetermined unit of landing as a row and the other as a column, and the current time is set in advance. Past the alert threshold time A predetermined unit of departure / landing consisting of a predetermined unit of the departure, a predetermined unit of the landing, or an arbitrary combination of the predetermined unit of the departure and the predetermined unit of the landing. Separately, when the total number of loaded items does not match the number of picked up items, the loaded number is edited into an alert display format, and when the current time is past a preset delivery alert threshold time, Calculated by the counting unit by the predetermined unit of the departure, by the predetermined unit of the landing, or by the predetermined unit of the departure / landing consisting of an arbitrary combination of the predetermined unit of the departure and the predetermined unit of the landing When the delivery quantity does not match the collection quantity, a table format editing unit for editing the delivery quantity into an alert display format can be included.

  (3) When the current time has passed a preset collection alert threshold time, the tabular editor edits the predetermined unit of the origin, the predetermined unit of the landing, Or, when the total number of collections is zero for each predetermined unit of departure / landing consisting of an arbitrary combination of the predetermined unit of departure and the predetermined unit of landing, the collected number is edited in an alert display format. be able to.

  (4) The tabular format editing unit may further include, for each predetermined unit of the origin in the tabular data, for each predetermined unit for the landing, or any combination of the predetermined unit for the origin and the predetermined unit for the landing. The number of pick-ups stored in the corresponding cell for each predetermined unit of departure / landing, the predetermined unit of departure, the predetermined unit of landing, or any combination of the predetermined unit of landing and the predetermined unit of landing It is possible to link the trace records of the transported cargo collected on the collection date starting from or landing on the predetermined unit of departure / landing.

  (5) The predetermined unit of departure and the predetermined unit of landing may be one departure and one landing, respectively.

  (6) The server in any one of (1) to (4) is further set in advance in each service with the origin of the transport cargo in the inter-company transport service, the external transport service, or the collection transport service. Landing group in which the information about the originating group grouped according to each condition and the landing of the transported cargo in the inter-internal transportation service, external transportation service or collection transportation service are grouped according to the conditions set in advance in each service And a group information storage unit for storing the information, and the counting unit is configured to set the departure group and the arrival group set based on the information on the departure group and the information on the arrival group stored in the group information storage unit, Make the predetermined unit of departure and the predetermined unit of landing respectively. It can be.

  (7) The server according to (1), wherein the predetermined unit of departure is a departure group obtained by grouping the departure points in a unit of a preset region, and the predetermined unit of landing is the landing unit. The arrival group grouped in units of the region, the collection date is the day before the current date, and the editing unit is configured to collect the collection date by the aggregation unit according to the departure group or the arrival group. Aggregated information summarizing the non-delivery status of the transported cargo collected in the map is edited into map-format data in which the region name of the region unit is arranged, collected on the collection date, and the current date that is the next day of the collection date If there is a shipment that has not been delivered, the location where the unit name of the region that is the originating group including the origin of the shipment is arranged in the alert display format, and is collected on the collection date, The day after the pickup date Includes a map format editor that edits the location where the unit name of the region that is the destination group including the landing of the transported cargo is placed in the alert display format when there is transport cargo that has not been delivered on the current date be able to.

  (8) The server according to (7), wherein the map format editing unit further sets the departure group or the arrival group as a departure point or a landing point in the area name where the area name is arranged, It is possible to link the trace records of the transportation cargo collected on the collection date.

  (9) The present invention provides a server for a transport cargo handled by a carrier, at the time of collection of the transport cargo by the carrier, at least an invoice number, a collection date, a collection time, a collection number, When the cargo collection information is registered to register the shipper information and the shipper information and is loaded onto the transportation cargo delivery vehicle, at least the loading processing date, the loading time, and the scheduled delivery time are registered to register the transportation cargo. Upon completion of delivery, each stage of transportation from the collection at the departure of all the transported cargo to the completion of delivery by registering at least delivery date, delivery time, delivery quantity, etc. Trace database that stores trace records for centrally registering and managing the passing records of the above, the carrier, for a given user, the user's headquarters, If you have an in-house transportation service that collects and delivers freight with several branches, branches, offices, or group companies, the user's head office, multiple branches, branches, offices, or groups Collecting transport cargo from a company and delivering it to an outside consignee, or collecting the transport cargo from the user's business partner or group company according to the instructions from the user. The user identification information of the user, the billing destination of the transportation freight charge, for each service of the inter-company transportation service, the outside transportation service, or the collection transportation service. A user management information storage unit that stores association information in advance associated with a shipper code, the in-house transportation service, the outside transportation service, or All of the shipper codes stored in the user management information storage unit and linked to the user identification information in response to a transport status search request including the collection date of the transported cargo handled by the collection and transportation service A search unit that searches and extracts a trace record of the transported cargo collected on the collection date from the trace database, and inputs the trace record extracted by the search unit as an input, and collects on the collection date The undelivered state of the transported cargo is determined according to a predetermined unit of the departure, a predetermined unit of the landing, or a predetermined origin / landing consisting of any combination of the predetermined unit of the departure and the predetermined unit of the landing. A totaling unit that creates totalized information for each unit, and by the totaling unit, for each predetermined unit of the departure, for each predetermined unit of the landing, or for a predetermined unit of the departure and the previous Transportation in a preset format based on the aggregated information on the undelivered status of the transported cargo collected on the said collection date for each predetermined unit of departure / landing consisting of any combination of predetermined units of landing Edit the status collective management information, and at that time, the predetermined unit of the origin where the undelivered state of the transport cargo exists, the predetermined unit of the landing, or any combination of the predetermined unit of the origin and the predetermined unit of the landing The predetermined unit of departure / landing consisting of the above is edited into a preset alert display format, and the predetermined unit of departure, the predetermined unit of landing, A trace record of the transported cargo collected on the collection date starting from or landing at a predetermined unit of departure / landing consisting of an arbitrary combination of a predetermined unit of land and a predetermined unit of landing Unit, predetermined unit of the landing, or edit unit give link to a predetermined unit of departure-landing consist of any combination of a predetermined unit of a predetermined unit and the landing of the calling destination, a program for functioning as a.

  (10) The program further groups servers according to the conditions set in advance in each service, and the origin of transport cargo in the inter-company transport service, the external transport service, or the collection transport service. Information on the originating group and information on the landing group obtained by grouping the landing of the transport cargo in the inter-company transportation service, the outside transportation service, or the collection transportation service according to the conditions set in advance in each service are stored. A group information storage unit, and the aggregation unit is configured to set a departure group and a destination group set based on information about the departure group and information about the arrival group stored in the group information storage unit, respectively, It will be a predetermined unit and a predetermined unit of landing It can be made to function in.

According to the present invention, when a user having a branch / branch office or business office in the whole country is provided, for example, with the above-described inter-company transportation service, external transportation service, or collection transportation service, the user receives a collection / delivery request. Based on this, it is possible to provide a service for performing a collective management search in real time by a simple operation for the transportation status from the collection to the completion of the delivery of all the cargos sent from the branches / branches, offices or user customers nationwide. In addition, the user can perform a collective management search using a case where collection, loading, and delivery are delayed due to some irregular circumstances as compared with a normal schedule as an alert.
In addition, it has become easier to investigate “uncollected goods”, which conventionally cannot be known without confirming the telephone with the collection shop. In addition, it is possible to collectively check the arrival of all the amounts that have conventionally been performed on a paper basis. In addition, the customer's customer satisfaction is improved and the number of inquiries from the user is improved by seeing the transportation status from the collection of all the cargo sent from the user's branch / branch office, office or user's customer to the completion of delivery. It has the effect of being reduced.

It is a figure which shows the outline | summary of the in-house transportation service, the outside transportation service, and the collection transportation service. It is a figure which shows the structure of a transportation status package management search system. 2 is a diagram illustrating a configuration of a terminal 1. FIG. 2 is a diagram showing a configuration of a server 2. FIG. It is a figure which shows the outline | summary of the flow of transport. It is a figure which shows the specific example of group information and block information. It is a display example of the transportation status collective management table by group information. It is a figure which shows the example of the menu screen for inputting a search pattern. It is an example of a transport status collective management map provided by search pattern 4 (transport status). It is an example of a transport status collective management search screen provided by search pattern 1 (external transport service) corresponding to an external transport service. It is an example of a transport status collective management search screen provided by search pattern 3 (intra-company transport service) corresponding to the intra-company transport service. It is a figure which shows the example of the screen which displays a trace record list. It is a figure which shows the example of the screen of a single case inquiry. It is a flowchart which shows the flow of a process of the transportation status package management search system. It is a flowchart which shows the flow of a process of the transportation status package management search system. It is a flowchart which shows the flow of a process of the transportation status package management search system.

[First Embodiment]
Hereinafter, a preferred embodiment of the transportation status batch management search system 100 of the present invention will be described with reference to FIGS.
First, terms used in the transportation status batch management search system 100 of the present invention will be described.

  The objects of the transportation status collective management search system 100 are the three services shown in FIG. The first service is an “external transport service” that transports the transported cargo collected from the user's branch / branch office or office to a destination that is the user's customer at random, and the second service is a collection destination that is the user's customer. For example, the “collection transport service” that transports transported cargo collected from a destination to a destination such as a factory, which is set in advance, and the third service is, for example, the transport cargo collected from the user's headquarters, branch / branch office, or office This is an “in-house transportation service” that collects the information at the head office of the company and transports them to the user's head office, branch / branch office, or office.

The transport status batch management search system 100 provides a transport status batch management search function corresponding to an outside transport service, a collected transport service, and an in-house transport service. For this reason, the transport status collective management search system 100 uses an identification type of “search pattern” to distinguish which service is the transport status collective management search function.
Here, “search pattern 1” is an identification type for identifying the transport status collective management search function corresponding to the external transport service. Similarly, the search pattern 2 and the search pattern 3 are identification types for identifying the transport status collective management search function corresponding to the collected transport service and the in-house transport service, respectively.

Furthermore, the transportation status batch management search system 100 has a transportation status batch management map function that collectively displays the transportation status for each prefecture by displaying a map of Japan on the top screen of the terminal when the user logs in to the system. Provided. For this reason, the transportation status collective management search system 100 identifies the transportation status collective management map function based on the Japanese map display by “search pattern 4”.
In the search pattern 4, one or more services are set in advance among the outside transportation service, the collection transportation service, or the in-house transportation service, and the previous day is set as the collection date for the set transportation service. Provide a transportation status batch management chart (hereinafter also referred to as “transportation status batch management map (I)”) by map display, which enables intuitive grasp of the status of undelivered cargo.
By doing so, it is possible to grasp the prefectures where irregular circumstances may have occurred.

  When freight is transported, there are points where the cargo is collected (for example, the address, name, departure store, etc. of the shipper) and points where the cargo is delivered (for example, the address, name, delivery store, etc. of the consignee). Therefore, the points where cargo is collected are collectively referred to as “origin”. Similarly, points where cargo is delivered are collectively referred to as “landing”.

  A grouping of one or more departures and one and more landings is referred to as “departure group” and “landing group”. In addition, one or more “originating groups” and one or more “arriving groups” that are blocked are referred to as “origin block” and “arrival block”, respectively.

[Functional configuration of transportation status batch management search system 100]
A functional configuration of a transportation status centralized management system according to a preferred embodiment of the present invention (hereinafter also referred to as “first embodiment”) will be described.

  As shown in FIG. 2, the transportation status collective management search system 100 includes a terminal 1 and a server 2 that are communicably connected via a communication network 3. Here, the communication network 3 may be a wired communication network, a wireless communication network, a mobile phone network, or the like.

[Terminal 1]
The terminal 1 includes, for example, a personal computer, a notebook computer, a tablet terminal, a smartphone, a PDA, a mobile phone, and other electronic devices that include at least a wired or wireless communication device. Software such as a browser is installed in the terminal 1, and based on the user's request, the shipper (for example, the user's head office, branch / branch office, business office, or user associated with the user associated with the user) , Customers, etc.) can carry out a collective management search for the transport status of transport cargo.

As shown in FIG. 3, the terminal 1 includes a control unit 10A, a storage unit 20A, a communication unit 30A, a display unit 40A, and an input unit 50A.
The control unit 10A further includes a connection processing unit 11A and a display control unit 12A.

  The control unit 10A includes a processor having a CPU, RAM, ROM, I / O, and the like, and controls each component of the terminal 1. The CPU executes a program for performing the transportation status collective management search display control read from the RAM, ROM, or the storage unit 20A, and reads information from the RAM, ROM, and storage unit 20A when executing the program. In addition, information is written to the storage unit 20A, and signals are exchanged with the communication unit 30A.

The control unit 10A causes the terminal 1 to function as predetermined functional means (hereinafter collectively referred to as “transportation status collective management search display control unit”) by executing each program for transport status collective management search display control.
Further, the control unit 10A executes predetermined programs (hereinafter collectively referred to as “transportation status collective management search display control step”) on the terminal 1 by executing each program for transport status collective management search display control. Let
The terminal 1 issues a request to the server 2 by the transportation status collective management search display control unit, receives a response from the server 2 to the request, and interactively displays it on the display unit 40A.
The operation of the terminal 1 will be described later.

Next, the server 2 will be described.
<Server 2>
The server 2 transmits / receives information to / from the terminal 1 via the communication unit 30. Here, the server 2 may be a server system including a single server and a plurality of servers.
As illustrated in FIG. 4, the server 2 includes at least a control unit 10, a storage unit 20, and a communication unit 30, and further includes a display unit 40 and an input unit 50 as necessary.
The server 2 is preferably a server system including a plurality of servers such as a Web server, an application server, and a database server, but is not limited thereto.

  The control unit 10 includes a processor having a CPU, a RAM, a ROM, an I / O, and the like, and controls each component of the server 2. The CPU executes a program for performing the transportation collective management search service read from the RAM, ROM, or the storage unit 20, and reads information from the RAM, ROM, and the storage unit 20 when executing the program. Information is written to the unit 20, and signals are exchanged with the communication unit 30.

  The storage unit 20 includes a semiconductor memory, a hard disk drive, and the like, and stores various information such as an operating system (OS) and software called an application being saved. The storage unit 20 further includes a trace database 21, a sales management database 22, a user management information storage unit 23, a group information storage unit 24, and an alert time information storage unit 25.

[Trace database 21]
The trace database 21 has a passing record (hereinafter referred to as “trace information” or “traffic information”) from a driver terminal, a passing point terminal, etc. Is also a database that manages the trace information. The trace database 21 is a database for managing the transportation history for each waybill.
As shown in FIG. 5, in the trace database 21, the transportation status is registered in real time along the transportation flow for each waybill.
More specifically, the following data is registered in the trace database 21 along the transportation flow shown in FIG.
First, for each one waybill, a waybill record (hereinafter also referred to as “trace record”) is created, and an invoice number for identifying the waybill, collection registration data (for example, business code, (Collection date, collection time, item name, number of collection, weight, shipper information, shipper information, collection shop code, etc.) are registered.
Here, the shipper information includes, for example, a shop code, a shipper code for the departure trace, a block code for the shop, a JIS code of the shipper town, a shipper name, a shipper address, a shipper telephone number, a shipper dedicated number Can be included. Similarly, the shipper information includes, for example, a shop code, a shipper code for landing, a shop block code, a shipper municipal JIS code, a shipper name, a shipper address, a shipper telephone number, and a shipper dedicated number. Can be included.
Next, when loading the transportation cargo into the cargo shipping vehicle, shipping registration data (business code, shipping processing date, shipping processing time, number of ships, driver code, shipping office code, etc.) is registered.
Next, when the transport cargo is loaded on, for example, an aircraft of a long-distance transportation means, airport departure registration (departure relay) data (for example, business code, departure airport passage date, departure airport passage time, etc.) is registered.
The next time you arrive at the airport at the transit terminal and transfer the transported cargo to another aircraft, the connection airport pass registration data (for example, business code, connection airport pass date, connection airport pass time, etc.) is registered. .
Next, when the transport cargo arrives at the airport of the delivery destination terminal and is transferred to the transport vehicle, arrival airport passage registration data (for example, business code, arrival airport passage date, arrival airport passage time, etc.) is registered.
Next, when the transported cargo arrives at the delivery store, arrival registration data (for example, business code, arrival processing date, arrival processing time, etc.) is registered.
Next, when transported cargo is transshipped to a freight delivery vehicle, scheduled delivery time registration (loading) data (eg, business code, loading date, loading time, loading number, loading store code, etc.) Is registered.
Finally, delivery completion registration data (for example, business code, delivery date, delivery time, delivery number, delivery office code, etc.) is registered when delivery of the transported cargo to the shipper (consignee) is completed.
In this way, each registered data is recorded in the trace database 21 by being added or updated in real time. At that time, the latest status of the transportation (for example, latest data type, latest processing date, latest processing time, etc.) is added or updated in real time and recorded.

  When loading on a long-distance transport truck instead of an aircraft as a long-distance transportation means, long-distance transportation instead of airport departure registration (departure relay) data, connection airport passage registration data, arrival airport passage registration data, etc. Data corresponding to tracks can be recorded and managed. The trace database 21 can register and store image data of the invoice itself.

The trace record can have a data item for registering a group shipper code for bundling a plurality of accounts receivable shipper codes. For example, for company X with branches all over the country, if a different accounts receivable shipper code is assigned to each branch of company X, a group shipper code is preset for each prefecture in order to extract the results for each prefecture. In addition, the group shipper code of the prefecture unit to which the branch belongs can be stored in the trace record of the cargo for which the branch is the accounts receivable shipper.
In addition, in order to extract the results of each region, a group shipper code is set in advance for each region, and the group shipper code to which the branch belongs (local unit) is stored in the cargo trace record in which the branch becomes the accounts receivable shipper code. be able to. Note that a plurality of group shipper codes can be set in advance so that different group shipper codes can be used from the trace database 21 according to the purpose of extracting the trace records.
Further, in the present invention, in order to manage whether the freight on the waybill is a freight subject to the inter-company transportation service, a freight subject to the external transportation service, or a freight subject to the collection transportation service The account receivable code is used.
In other words, a group that has an accounts receivable shipper code unique to the inter-company transportation service, an accounts receivable shipper code unique to the outside transportation service, and an accounts receivable shipper code unique to the collection transportation service, for example, a group that bundles the accounts receivable shipper code unique to the inter-company transportation service By setting the shipper code, it is possible to extract all trace codes related to the inter-company transportation service.

  The trace database 21 may be stored in a database server (not shown) different from the server 2.

[Sales management database 22]
The sales management database 22 is an accounts receivable information management database created for each waybill.
More specifically, the sales management database 22 includes an invoice number for identifying a waybill, a collection date, a collection time, a collection store code, an account receivable shipper code to which the account is billed, a receipt number, and a receipt of payment amount. You can record and manage numbers, receipts for goods, etc.
The account receivable code can be assigned to each department in charge of the user's head office, branch / branch / office.
In the present invention, the accounts receivable shipper code that is the billing destination for accounts receivable related to the inter-company transportation service, the outside transportation service, and the collection transportation service is used as the accounts receivable shipper code unique to each service. By doing so, it becomes possible to extract the invoice numbers of the transport cargo related to the inter-company transport service, the external transport service, and the collection transport service. Further, in addition to the conventional transportation fee, it is possible to charge a transportation collective management search service usage fee of the present invention in addition to the conventional transportation fee for the transportation cargo related to the inter-company transportation service, the outside transportation service, and the collection transportation service.

  As described above, the cargo information is managed in the trace database 21 and the sales management database 22 in units of invoice numbers.

[User management information storage unit 23]
The user management information storage unit 23 sets user management information set for each user, for example, user identification information (also referred to as “user ID”), user name, user head office information / branch / branch office information / office information, etc. Manage customer information.
In addition, the transport status batch management search function (search pattern 1) corresponding to the external transport service, the transport status batch management search function (search pattern 2) corresponding to the collected transport service, and the transport status batch management corresponding to the inter-company transport service In accordance with the search function (search pattern 3), a group shipper code obtained by grouping accounts receivable shipper codes corresponding to the user's head office, branch / branch office, office, department in charge, department in charge, etc. is stored in association with the user ID. can do.
Moreover, the account receivable consignor code for account receivable management recorded in each waybill record stored in the sales management database can be stored in association with the user ID.

[Linking User ID to Group Shipper Code or Accounts Receivable Shipper Code]
Here, the association between the user ID and the group shipper code or the accounts receivable shipper code will be described.
As described above, when the user uses the inter-company transportation service, the external transportation service, or the collection transportation service, the accounts receivable that is the billing destination for the accounts receivable of the transport cargo related to the inter-company transportation service, the outside transportation service, and the collection transportation service. One or more shipper codes are set for each user. In the accounts receivable information management record created for each waybill in the sales management database 22, an account receivable shipper code as a billing destination of accounts receivable is stored.
Further, in the trace record of the transport cargo related to each service in the trace database 21, a group shipper code obtained by bundling the account receivable shipper code unique to each service is stored.
Then, by connecting all the user IDs and the group shipper codes specific to each service to the users who use each service, the trace records of the transportation cargo related to the service of the user ID are extracted in a lump. It becomes possible.
In addition, by associating all user IDs and accounts receivable shipper codes specific to each service, it is possible to collectively extract accounts receivable information management records in which the accounts receivable shipper codes of the transport cargo related to the service of the user ID are recorded. It becomes possible. By doing so, it becomes possible to collectively extract the invoice number of the transport cargo related to the service of the user ID, and based on the extracted invoice number, the trace record of the transport cargo related to the service of the user ID Can also be extracted in a batch.

For example, when providing the search status 1 transport status collective management search service to user X who has branches / branches or offices throughout the country, the head office, branch / branch office, office, and responsible for user X that is the origin An account receivable shipper code assigned to a department, a department in charge, or a group shipper code obtained by bundling a plurality of accounts receivable shipper codes can be associated with the user ID of the user X.
By doing so, for example, when providing the search function of the search pattern 1 (transportation status collective management search function corresponding to the external transport service) to the user X, the accounts receivable shipper code and group shipper code linked to the user ID of the user X It becomes possible to search and extract the trace records of the transport cargo that becomes the shipper at once. Since the accounts receivable code is not recorded in the trace record, the invoice number related to the accounts receivable code associated with the user ID is acquired via the sales management database, and the invoice number is obtained from the trace database 21 based on the invoice number. Trace records can be searched and extracted.
Even when the search functions of the search pattern 2 and the search pattern 3 are provided to the user X, for each search pattern, the accounts receivable shipper code and the group shipper code assigned to the transported cargo are linked to the user ID. Put it on.
By doing so, also in the case of providing the search function of the search pattern 2 and the search pattern 3 to the user X, similarly to the search pattern 1, the trace record of the transportation cargo related to the search pattern 2 and the search pattern 3 is displayed. It becomes possible to extract all at once

[Group Information Storage Unit 24]
In the group information storage unit 24, group information in which one or more places are grouped, such as a user branch, branch office, office, user customer, user group company branch, branch office, office, etc. Block information obtained by blocking one or more groups is preset and stored.

[For search pattern 1 and search pattern 2]
A group set for one or more shippers (senders) is called a “shipping group”, and a block set for one or more calling groups is called a calling block.
Similarly, a group set in advance for one or more receivers (consignees) is referred to as a “arrival group”, and a block set for one or more arrival groups is referred to as an incoming block. .
Since group information and block information can be set for each search pattern, an optimum group can be set for the service used by the user.

When setting the departure group, the data items of the trace record are the collection shop code, the shipper code for the departure trace, the block code of the collection shop, the JIS code of the shipper municipality, the shipper name, the shipper address, and the phone number of the shipper. A shipping group can be set by designating any one item among the shipper's exclusive numbers and setting one or more values of the item.
The following are the “collection store data item”, “collector location code”, “shipper tracer code”, “collector location block code”, “shipper municipality JIS code”, “shipper name”, “shipper address”, “shipper phone number”, and “shipper exclusive number”. "
As the calling group information, at least the calling group name, the data item specified from the calling grouping data item for setting the calling group, one or more possible values of the specified data item, The originating block code or the like to which it belongs is set in advance. The calling group information is stored in the group information storage unit 24 in association with the user ID and the search pattern.
For example, in the case of Pattern 2, the shipper is the collection destination, and when the shipper group is set, the arrival group “... region” can be set by specifying the “shipper municipality JIS code”.

  As the outgoing block information, a preset regional block code can be used. In addition, a new outgoing block can be set separately.

Similarly, for the grouping of the shippers (consignees), for example, the planned store code, the shipper code for the arrival trace, the block code of the store, the JIS code of the shipper municipality, the shipper name, the shipper address, the caller telephone A destination group can be set by designating any one item among the number and the number dedicated to the arrival party and setting one or more values of the item.
Below, the arrival group code, arrival trace blocker code, arrival place block code, arrival party municipality JIS code, arrival party name, arrival party address, arrival party telephone number, arrival party dedicated number, and "arrival group data" Also referred to as “item”.
As the arrival group information, at least the arrival group name, the data item specified from the arrival grouping data items for setting the arrival group, one or more possible values of the specified data item, The incoming block code to which the call belongs is preset. The destination group information is stored in the group information storage unit 24 in association with the user ID and the search pattern.
For example, in the case of pattern 1, the arrival party is the customer of the user, and the arrival group “... region” can be set by designating the “arrival party municipality JIS code” when setting the arrival group.

  As the arrival block information, a preset regional block code may be used. Alternatively, it can be set by designating a destination block name and a destination group name belonging to the destination block.

Specific examples of groups and blocks will be described with reference to FIGS. 6A and 6B.
6A and 6B, in search pattern 1 (external transport service) or search pattern 2 (collection transport service), the shipper (shipper) is grouped by shipper name, and the shipper (consignee) is received. An example of grouping by shipper telephone number is shown.
For example, the “B Company Douo Group” of the departure group is a group of shipper names “B Company Sapporo Office” and “B Company Ishikari Office”.
As for the departure group, “Hokkaido block”, “Tohoku block”, “Kanto Koshinetsu block”, “Chubu Hokuriku block”, “Kansai block”, “Chinese block”, “Shikoku block”, “Kyushu block”, “ It is divided into “Okinawa block”.

  Similarly, the “A Company Tokyo Center” of the arrival group is a grouping of the arrival phone numbers “03-1111-1111”, “03-1111-1112”, and “03-1111-1113”. . For the arrival group, no block is specified.

As described above, the calling group and the called group can be set in advance for each user and each search pattern, and can be stored in advance in the group information storage unit 24 in association with the user ID and the search pattern.
In addition, the calling group and the called group can be further blocked, and the block information is also stored in the group information storage unit 24 in association with the user ID and the search pattern.

[For search pattern 3]
In search pattern 3, for example, a collective management search of the intra-company transport status between the user's head office and branch / branch / office is performed, so the group includes one parent group (corresponding to the head office) and multiple children. Groups (corresponding to branch offices / branches / business offices) are set in advance and stored in the group information storage unit 24.
The search pattern 3 (intra-company transportation service) of the case where the parent group is the shipper and the child group is the shipper and the case where the child group is the shipper and the parent group is the shipper can be collectively managed and searched.
Regarding the setting of the parent group and the child group, similarly to the setting of the originating group and the terminating group, any one of the originating grouped data items (or the terminating grouped data items) is set in order to set the parent group or the child group. A parent group or a child group can be set by designating one item and setting the value of the item to one in the parent group and one or more in the case of the child group.
As parent / child group information, the type of the parent group / child group, the group name, the data item specified from the grouped data item for setting the group, one or more possible values of the specified data item The block code to which the group belongs is set in advance. The parent group information and the child group information are stored in the group information storage unit 24 in association with the user ID and the search pattern.

  For example, in FIG. 7D, in the search pattern 3 (intra-company transport service), the child groups are represented by, for example, a shipper municipal JIS code, “Hokkaido”, “Aomori Prefecture”, “Iwate Prefecture”, “Miyagi Prefecture”,. , "Okinawa" group. For the parent group, “head office mail center” is designated.

[For search pattern 4]
In the search pattern 4, based on the shipper's shipper municipal JIS code for the shipper group and the shipper group for the shipper group, the region code (for example, the prefecture code) and the region name (for example, the city) Group by prefecture name).
In the first embodiment, the area code and the area name are the prefecture code and the prefecture name, respectively, but the present invention is not limited to this.

[Alert time information storage unit 25]
The alert time information storage unit 25 stores in advance, for each user and each search pattern, a threshold time for determining whether or not to output a transport status alert (warning) when performing a collective management search of the transport status. To manage.
For example, in the transport status collective management search system 100, in the search pattern 3 (intra-company transport service), the time when the number of transported cargo is a preset threshold (hereinafter also referred to as “collection alert threshold time”) has passed. If the number is zero, an alert is output on the assumption that there is a high possibility that the transported cargo has not been collected due to some irregular circumstances.
Similarly, if the number of cargoes to be transported does not coincide with the number of cargoes collected even after a preset threshold time (hereinafter also referred to as “loading alert threshold time”), the cargo will be loaded for some irregular reasons. An alert is output assuming that there is a high possibility of being unregistered.
Similarly, if the delivery quantity of the transported cargo does not coincide with the collection quantity even after a preset threshold time (hereinafter also referred to as “delivery alert threshold time”), it will be considered as an undelivered state due to some irregular circumstances. An alert is output as it is likely that
In search pattern 1 and search pattern 2, the loading alert threshold time and the delivery alert threshold time can be defined for each user.
By doing so, an optimal threshold value can be set in accordance with the freight transportation time zone of the user.

  As described above, according to the first embodiment, a time that is a threshold value for determining the collection state, loading state, and delivery state of a trace as irregular is set in advance and stored in the alert time information storage unit 25. can do.

  The communication unit 30 can implement a communication protocol for performing wired communication (for example, LAN, WAN, Internet line, etc.) or wireless communication (for example, wireless LAN, mobile phone network, etc.) when transmitting / receiving to / from the server 2. For example, the communication unit 30 includes a DSP (Digital Signal Processor) or the like, and can be configured to perform wireless communication through a wireless communication network represented by a mobile phone network such as 3G or LTE.

  The display unit 40 is configured by a display device such as a liquid crystal display or an organic EL panel, for example, and displays an image in response to an instruction from the control unit 10.

  The input unit 50 includes, for example, an input device (not shown) such as a keyboard. The server 2 can be operated by outputting a signal based on the operation input from the input unit 24 to the control unit 10B.

  Before describing each functional unit included in the control unit 10 in detail, a transport status batch management search screen provided by the transport status batch management search system 100 to the terminal 1 will be described with reference to FIGS. 7A to 7F.

[Search pattern 1 (external transport service)]
FIG. 7C is an example of a transport status collective management search screen provided by search pattern 1 (external transport service) corresponding to the external transport service.
As described above, corresponding to the case of the search pattern 1 of the user, the departure group, departure block, arrival group, and arrival block are set in advance with respect to the departure (shipper) and landing (shipper), respectively. It is stored in the information storage unit 24.

[Transportation status management table (A)]
As shown in FIG. 7C, the transport status collective management search screen provides a transport status collective management table (A) in a tabular form representing the transport status from the originating group to the destination group. Here, the originating group name or originating block name is displayed in each row of the transportation status batch management table, and the terminating group name or terminating block name is displayed in each column. In each cell where each row and each column intersect, the collection number, loading number, or delivery completion number of the transportation cargo collected on the designated collection date (in this example, 2014/04/10) is stored. Is displayed.

Referring to the transportation status batch management table shown in Fig. 7C, the number of cargoes collected from the Hokkaido North Hokkaido Dohoku Group and the Tohoku Block Group B is three, of which the number is 1 It is shown that the number of completion is one.
In this example, if the current time is past the loading alert threshold time or the delivery alert threshold time, the number of loadings that is inconsistent with the number of cargoes collected from Hokkaido Hokkaido's Hokkaido North Group to Tohoku Block Group B Alternatively, the number of deliveries can be displayed as an alert (for example, color designation).
By doing so, the user, due to some irregular circumstances, out of the three pick-up numbers to be transported from the Hokkaido block Dohoku group to the Tohoku block group B on the specified pick-up date (2014/04/10), It becomes possible to grasp that two are not loaded and not delivered.
Any irregular circumstances are preferably registered in the trace database. By doing so, it can be expected to reduce the number of user inquiries.

[Collecting quantity link (B)]
Each collection quantity is linked to a set of trace records that is a breakdown of the collection quantity.
When a user depresses (clicks) a collection number link (hereinafter also referred to as “collection number link”), a list of trace record sets (hereinafter referred to as “collection number collection”) as shown in FIG. "Trace record list") is displayed.

[Incomplete Pickup Date List (C)]
In addition, in the transport status batch management search screen in search pattern 1 (external transport service), search pattern 2 (collected transport service), and search pattern 3 (inter-company transport service), the past 1 If there is a trace record with the date of the week as the collection date and there is an undelivered state, the list data of the collection date (“incomplete collection date list”) is displayed as “Uncompleted” (C) can do.
The collection date displayed in the uncompleted collection date list is linked to a set of trace records of the transported cargo collected on the collection date and currently undelivered.
By pressing (clicking on) a collection date link (hereinafter also referred to as “collection date link” (D)) displayed in the uncompleted collection date list, it is a trace record of the transported cargo collected on that collection date. A list of trace records that are currently undelivered is displayed.

[Update button (E)]
As shown in FIG. 7C, the transport status batch management search screen includes an “update button” (E) in addition to the transport status batch management table. When the update button is pressed (clicked) by the user, the transportation status batch management table can be updated to the latest state.

[Download button (F)]
As shown in FIG. 7C, the transport status batch management search screen includes a “download button” (F) in addition to the transport status batch management table. When the download button is pressed (clicked) by the user, the transport status is displayed. A batch management table is downloaded to the terminal 1.

  In addition, the collection number link (B), the uncompleted collection date list (C), the update button (E), and the download button (F) are search management of the transport status in all of the search pattern 1, the search pattern 2, and the pattern 3. Common to screens.

[Trace record list (G)]
As shown in FIG. 7E, the trace record list (G) includes, for example, the branch name, invoice number, cargo collection quantity, weight, collection shop, delivery shop, latest status of transportation, delivery classified into the group. The completion date is displayed. Note that which item of the trace record is displayed can be changed according to user needs.
Also in the trace record list, the trace record can be displayed as an alert (for example, color designation) for the undelivered trace data.

[Invoice number link (H)]
Furthermore, a trace record having the invoice number is linked to the invoice number displayed in each trace record displayed in the trace record list.
When the invoice number link (hereinafter also referred to as “invoice number link”) is pressed by the user, the detailed information (“single inquiry”) of the conventionally provided trace record as shown in FIG. 7F is displayed. Is done.

[Download button]
As shown in FIG. 7E, the trace record list display screen includes an “update button”, and when the user presses the update button, the trace record list can be downloaded.

[About collection transportation service]
The functions and screen configuration provided by the transport status collective management search function (search pattern 2) for the collected transport service are the functions provided by the transport status collective management search function (search pattern 1) for the service outside the company and This is the same as the screen configuration and will not be described.

[Search pattern 3 (in-house transportation service)]
FIG. 7D is an example of a screen provided for a transport status collective management search screen in search pattern 3 (intra-company transport service) corresponding to the intra-company transport service.
Search pattern 3 (intra-company transportation service) is provided in a table format (transportation status collective management table) indicating the transportation status from the originating group to the destination group.

FIG. 7D corresponds to the case of the search pattern 3 of the user, in which a parent group and a child group, and a child group and a parent group are set for the shipper (shipper) and the shipper (consignee), respectively. This is the case stored in the information storage unit 212.
In this case, a parent group (head office mail center) and a child group (Hokkaido, Aomori Prefecture, Iwate Prefecture, Miyagi Prefecture,..., Okinawa Prefecture) are set in advance.

The transport status collective management search screen in search pattern 3 provides a transport status collective management table in a tabular form representing the transport status from the originating group to the destination group. A transportation status batch management table (search pattern 3) is output in a table format.
Referring to the table on the left side of Fig. 7D, the number of cargoes collected and loaded from the child group (Hokkaido, Aomori Prefecture, Iwate Prefecture, Miyagi Prefecture, ..., Okinawa Prefecture) to the parent group (Head Office Mail Center) And a transportation status collective management table (search pattern 3) in which the number of deliveries is totaled is provided to the user.
Referring to the table on the right side of Fig. 7D, the number of cargoes collected and loaded from the parent group (head office mail center) to the child groups (Hokkaido, Aomori, Iwate, Miyagi, ..., Okinawa) And a transportation status collective management table (search pattern 3) in which the number of deliveries is totaled is provided to the user.

Referring to the table on the left side of FIG. 7D (departure: child group, landing: parent group), for example, in the child group, the aggregated data of “Miyagi Prefecture” has 10 collections, 8 loadings, If the number of deliveries is 8, and the current time is past the loading alert threshold time, the number of loaded data in the aggregated data is displayed as an alert (for example, color designation).
In addition, the aggregated data of Ibaraki Prefecture has 8 items collected, 8 items loaded, and 0 items delivered, and if the current time has passed the delivery alert threshold time, the number of items delivered in the aggregated data Then, alert display (for example, color designation) is performed.
In addition, the aggregated data of Aomori Prefecture has a collection number of 0, and if the current time is past the collection alert threshold time, an alert is displayed (for example, color designation) for the collected number data of the aggregated data.

  Similarly to the search pattern 1, each collection quantity is linked to a list of trace record sets that are a breakdown of the collection quantity, and a collection quantity link (hereinafter also referred to as “collection quantity link”) is pressed. As a result, a list of trace records, which is a breakdown of the number of collections, is displayed.

  Similarly to search pattern 1, if there is a trace record that has a date of collection in the past one week and is in the undelivered state on the transportation status collective management search screen, it will be marked as “incomplete”. Collection date list data ("incomplete collection date list") can be displayed.

[Search pattern 4]
FIG. 7B is an example of a screen provided by the transport status collective management search screen in search pattern 4 (transport status collective management map function for collectively displaying the transport status of each prefecture by the Japanese map display).
In the search pattern 4, one or more services are set in advance among the outside transportation service, the collection transportation service, or the in-house transportation service, and the previous day is set as the collection date for the set transportation service. Provide a transportation status batch management chart (hereinafter also referred to as “transportation status batch management map (I)”) by map display, which enables intuitive grasp of the status of undelivered cargo.

  As shown in Fig. 7B, by pressing (clicking) "landing base" on the transportation status batch management search screen, the prefecture (Hokkaido, Aomori Prefecture,..., Okinawa Prefecture) is landed and the previous day is the collection date. Provided is a transportation status collective management map that can intuitively grasp landing-based information as to whether or not there is an undelivered cargo in the collected cargo. For prefectures with undelivered cargo, the relevant prefectures on the transportation status batch management map (I) are displayed in color.

  In addition, by pressing (clicking) “Departure Base”, delivery has not been completed for the collected cargo that has originated from each prefecture (Hokkaido, Aomori Prefecture,..., Okinawa Prefecture) and the collection date is the previous day. Provide a transportation status batch management map that can intuitively grasp origin-based information on whether or not there is cargo. The prefectures with undelivered cargo will be displayed in color on the transportation status batch management map. For prefectures with undelivered cargo, the corresponding prefecture on the transportation status batch management map is displayed in color.

[Prefecture name link (J)]
Each prefecture name (J) is linked to a set of trace records that originate or land in the prefecture. In this way, as in the case of the search pattern 1, by pressing (clicking) the link of the prefecture name (hereinafter also referred to as “prefecture name link”), the prefecture as shown in FIG. A list of trace records to be landed or landed is displayed.

[No pickup button]
In addition, by pressing (clicking) a “no pickup button” displayed on the transport status collective management search screen, it is possible to display an area where no pickup cargo is generated with the previous day being the pickup date.

  As described above, the transport status batch management search system 100 provides the terminal 1 with the transport status batch management search screen, the transport status batch management table, the transport status batch management map, the link with the trace record list, the incomplete pickup date list, etc. The display of was explained.

Next, each functional unit included in the control unit 10 for providing the collective management search information will be described. The control unit 10 executes predetermined programs on the server 2 by executing each program for the transport status collective management search. It is made to function as a means (hereinafter collectively referred to as “transportation status collective management search processing unit”).
Further, the control unit 10 causes the server 2 to execute predetermined steps (hereinafter collectively referred to as “transportation status batch management search processing step”) by executing each program for the transport status batch management search.

  Hereinafter, functions of the control unit 10 will be described from the viewpoint of the transportation status batch management search processing unit. The explanation based on the viewpoint of the transport status collective management search processing step (method) can be explained by replacing “part” with “step”, and will be omitted.

As shown in FIG. 4, the control unit 10 includes a login processing unit 11, an inter-terminal interface unit 12, a search unit 13, a totaling unit 14, an editing unit 15, a group inquiry unit 16, and a single case inquiry unit. 17.
The totaling unit 14 further includes a table format totaling unit 141 and a map format totaling unit 142.
The editing unit 15 further includes a table format editing unit 151 and a map format editing unit 152.
Next, these functional units will be described.

<Login processing unit 11>
The login processing unit 11 executes a login process including a user authentication process from the terminal 1 and performs a connection process with the terminal 1.

<Inter-terminal interface unit 12>

The inter-terminal interface unit 12 analyzes the request received from the terminal 1, selects a function unit that processes the request, provides a parameter to the function unit that has selected the parameter included in the request, and performs processing. Request.
Conversely, a response is transmitted to the corresponding terminal via the communication unit 30 based on output data provided from another functional unit.
The inter-terminal interface unit 12 can ensure the consistency of a series of transaction processes by performing session management.

  Next, a case where the inter-terminal interface unit 12 requests processing from another function unit in response to a request received from the terminal 1 will be described. Note that output data acquired by the inter-terminal interface unit 12 from other functional units will be briefly described together, but editing processing when the inter-terminal interface unit 12 transmits a response to the terminal will be described later.

[Login request]
If the request received from the terminal 1 is a login request, the inter-terminal interface unit 12 provides parameters included in the request to the login processing unit 11 and requests login processing. Here, the parameters included in the request are a user ID, a password, and the like.
The inter-terminal interface unit 12 generates a menu as shown in FIG. 7A, and by default, a search pattern type (search pattern 4) and a collection date (a date range including the day before the current date (for example, a date range) 1 week)) is provided to the search unit 13 and a search process is requested.
The inter-terminal interface unit 12 acquires a transportation status batch management map from the editing unit 15 for a response to the login request.

[Transportation status batch management search request]
When the request received from the terminal 1 is a transportation status batch management search request, the inter-terminal interface unit 12 provides the parameters included in the request to the search unit 13 and requests a search process.
Here, the parameters included in the request are the type of search pattern (any one of search pattern 1, search pattern 2, or search pattern 3) and the date of collection.
Here, the collection date can be specified not only for one day but also for a range such as the past week.
The case where the terminal 1 makes a transport status batch management search request to the server 2 is when the search pattern is selected in the menu and the “update button” is pressed (clicked) while the transport status batch management table is displayed. This is the case.
The inter-terminal interface unit 12 acquires a transportation status batch management table from the editing unit 15 for a response to the transportation status batch management search request.

[Trace record list search request]
When the request received from the terminal 1 is a trace record list search request, the inter-terminal interface unit 12 provides the parameters included in the request to the group inquiry unit 16 and requests a search process.
The terminal 1 makes a trace record list search request to the server 2 when the collection number link in the transport status batch management table is pressed while the transport status batch management table is displayed, or the transport status batch This is a case where the prefecture name link is pressed while the management map is displayed, or a case where the collection date link is pressed while the uncompleted collection date list is displayed.
The parameter included in the request can be the search condition used when creating the trace record list. For example, in the case of a collection number link, the search pattern type, collection date, departure group name, and arrival group name are used. In the case of the prefecture name link, the type of search pattern (search pattern 4), the date of collection, the designation of the departure base or landing base, and the prefecture code are used. In the case of a collection date link, it is the type of search pattern and the collection date.
The parameter may be a list of invoice numbers of trace records included in the trace record list.
The inter-terminal interface unit 12 acquires a trace record list from the group inquiry unit 16 for a response to the trace record list search request.

[Single inquiry]
When the request received from the terminal 1 is a single inquiry request, the inter-terminal interface unit 12 provides the parameters included in the request to the single inquiry unit 17 and requests a search process.
The parameter included in the request is an invoice number.
The case where the terminal 1 makes a single inquiry request to the server 2 is when the invoice number link is pressed while the trace record list is displayed.
The inter-terminal interface unit 12 acquires single inquiry data from the single inquiry unit 17 for a response to the single inquiry request.

[download]
When the request received from the terminal 1 is a download request, the inter-terminal interface unit 12 downloads the transportation status batch management table or the trace record list to the terminal 1 from its work area.
The parameter included in the request is, for example, a file name.
When the terminal 1 makes a download request to the server 2, the download button is pressed while the trace record list is displayed when the download button is pressed (clicked) while the transport status batch management table is displayed. (Clicked).

The processing of the request received from the terminal 1 by the inter-terminal interface unit 12 has been described above.
Processing when the inter-terminal interface unit 12 transmits output data provided from other functional units to the terminal 1 via the communication unit 30 will be described later after the description of the other functional units.

<Search unit 13>
The search unit 13 receives from the inter-terminal interface unit 12 the parameters “search pattern type (search pattern 1, search pattern 2, or search pattern 3) and collection date” or “search pattern type (search pattern 4)”. And a collection date (a date range including the day before the current date (for example, the past one week)) ”is acquired, and a search process is performed.

[Processing for Search Pattern 1, Search Pattern 2, or Search Pattern 3]
The search unit 13 acquires all group shipper codes or accounts receivable shipper codes associated with the user ID from the user management information recording unit 23 based on the user ID and the search pattern type. As described above, the search unit 13 searches the trace database 21 and extracts a trace record having a pickup date that matches the pickup date specified by the parameter based on the acquired group shipper code or accounts receivable shipper code. .
Further, the search unit 13 can search and extract a trace record having a collection date included in a date range including the day before the current date (for example, the past one week) from the trace database 21.

The search unit 13 stores a set of trace records (hereinafter referred to as “trace record group A”) corresponding to the search patterns 1 to 3 extracted from the trace database 21 in the memory or storage unit 20 for each user ID (work area). Hereinafter, it is also referred to as “user work area A”) and stored in association with parameters (search pattern type and collection date).
The search unit 13 extracts the trace record group A in the user work area A when the trace record having the collection date included in the date range including the previous day of the current date (for example, the past one week) is extracted from the trace database 21. Are stored in association with each pickup date.
Thereafter, the search unit 13 provides the user ID and the trace record group A together with the parameters (search pattern type and collection date) to the totaling unit 14.

[Processing for Search Pattern 4]
In the case of the search pattern 4, the search unit 13 searches for a search pattern with a high priority according to a preset search pattern priority for a user who uses a plurality of search patterns.
If the search pattern with the higher priority is the search pattern 1, the search unit 13 collects the collection date that matches the collection date specified by the parameter based on the group shipper code or the accounts receivable shipper code linked to the user ID. The trace record having the above is retrieved from the trace database 21 and extracted.

The search unit 13 uses a trace record set (hereinafter referred to as “trace record group B”) extracted from the trace database 21 as a work area (hereinafter referred to as “user work area B”) set for each user ID in the memory or the storage unit 20. Are also stored in association with each collection date included in the search pattern 4 and the collection date range.
Thereafter, the search unit 13 provides the user ID and the trace record group B to the totaling unit 14 together with the parameters (search pattern 4 and collection date (date range including the day before the current date)).

<Aggregation unit 14>
The aggregation unit 14 performs aggregation processing based on the trace record group A stored in the user work area A by the search unit 13 or the trace record group B stored in the user work area B by the search unit 13.
The totaling unit 14 includes a table format totaling unit 141 and a map format totaling unit 142.
Next, the processing content will be described.

[Processing for Search Pattern 1 or Search Pattern 2]
In the case of the search pattern 1 or the search pattern 2, the tabular form totaling unit 141, based on the trace record group A stored in the user work area A, in the designated collection date unit, Aggregate the number of loads and the number of deliveries. Hereinafter, “collected number, loaded number, and delivered number” is referred to as collected (number) data.
In the case of the search pattern 1 or the search pattern 2, the tabular form totaling unit 141 does not specify a group, but based on the trace record group A stored in the user work area A, the specified place of collection date -You may make it total the number of collection, loading, and delivery according to landing. In the following description, the group-by-group tabulation will be described, but the processing when tabulating by origin / landing can be performed in the same manner.

  Based on the group information stored in the group information storage unit 24, the tabular form totaling unit 141 associates the departure group from the shipper information of each trace record belonging to the trace record group A, and the arrival group from the shipper information. As a result, each trace record belonging to the trace record group A is classified into a departure group and a destination group. At this time, the originating group name and the terminating group name may be added to each trace record.

The tabular totalization unit 141 collects the number of pickups and loads based on the collection registration data, the estimated delivery time registration data, and the delivery completion registration data in each trace record belonging to the trace record group A classified by the departure group and arrival group. The number of pieces and the number of deliveries are counted for each departure group / arrival group.
By doing so, the tabular totaling unit 141 sums up the collection number, loading number, and delivery number of the transport cargo transported from each departure group to each arrival group. (Also referred to as “counting data (number) data by departure group / arrival group”).

  The tabular totaling unit 141 sums up the number of cargoes collected, loaded, and delivered from each departure group to each arrival block based on the total (number) data for each departure group and arrival group. Aggregation (number) data by group / arrival block, aggregated (number) data by origin group, summarizing the number of picked up, loaded, and delivery shipments transported from each originating group, transported from each originating block Aggregate (number) data for each originating block / arrival group that aggregates the number of picked up, loaded, and delivered items of transport cargo, and totals the number of picked up, loaded, and delivered items of transported cargo transported to each destination group Create total data (count) data for each received group.

  The tabular totaling unit 141 creates the totaling (number) data for each departure group / arrival group, totalization (number) data for each departure group / arrival block, totalization (number) data for each departure group, and totalization for each departure block / arrival group ( Number) data and total (number) data by destination group (hereinafter also referred to as “group total (number) data”) are stored in the user work area A in association with parameters (search pattern type and collection date).

In addition, the tabular totalization unit 141 refers to the transportation history information (for example, the latest history information) of each trace record belonging to the trace record group A classified by the departure group and arrival group, and the number of collections and the number of loadings The number of unloaded items and the number of completed deliveries are counted for each group of departure and arrival groups.
By doing so, the total data collected by each originating group / arriving group (hereinafter referred to as “origin group”) that aggregated the total number of collections, loadings, unloading, and delivery completions transported from each originating group to each arrival group.・ It is also possible to create “total data (number of cases) by destination group”.

  Tabular tabulation unit 141 collects, loads, unloads, and deliveries of transported cargo transported from each departure group to each arrival block based on the total (number) data by departure group and arrival group Total data by originating group / arrival block that aggregates the number of completed items, total number of transported cargo transported from each originating group, total number of loaded items, unloaded items, and total number of completed delivery items (Count) Data, aggregated (number) data by originating block / arrival group that aggregated the number of cargoes collected from each originating block, the number of loaded cargoes, the number of unloaded cargoes, and the number of completed deliveries. It is possible to create aggregated (count) data for each arrival group that aggregates the number of cargoes to be transported, the number of loaded items, the number of unloaded items, and the number of completed deliveries.

  The tabular tabulation unit 141 creates the totaling (number) data for each departure group / arrival group, totalization (number) data for each departure group / arrival block, totalization (number) data for each departure group, totalization for each departure block / arrival group ( Number of records) and total (number of records) by arrival group (hereinafter also referred to as “total by group (number) data”) can be stored in the user work area A in association with parameters (search pattern type and collection date). it can.

  Further, when the trace record group A is stored in the user work area A for each collection date included in a date range including the previous day of the current date (for example, the past one week) in the user work area A, the tabular totalization unit 141 In addition, by referring to the delivery completion registration data of each trace record belonging to the trace record group A, picking up the pickup date on which there is a trace record that has not been registered for delivery completion, a list of pickup dates that have not been delivered can be obtained. A “incomplete pickup date list” can be created.

  The tabular totalization unit 141 can store the created incomplete collection date list in the user work area A in association with parameters (search pattern type and collection date).

  After that, the tabular totaling unit 141 sends the user ID and group total (number) data, group total (number) data, and uncompleted collection date list to the editing unit 15 together with parameters (search pattern type and collection date). provide.

[Processing for Search Pattern 3]
The processing for the search pattern 3 is basically the same as the processing for the search pattern 1 or the search pattern 2. However, search pattern 3 is slightly different in that it is the transportation of cargo between one parent group and a plurality of child groups.
Note that the tabular totalization unit 141 is not based on the group but also on the basis of the trace record group A stored in the user work area A in the case of the search pattern 3 as in the case of the search pattern 1 or the search pattern 2. In the specified collection date unit, one origin (landing) is the parent and the other landing (landing) is the child, the origin (parent) / landing (child) unit, and the origin (child) -You may make it total the number of collections, the number of loading, and the number of deliveries for every landing (parent). In the following description, the group-by-group tabulation will be described, but the processing in the case of tabulating at the origin (parent) / landing (child) unit and at the origin (child) / landing (parent) unit can be similarly performed.
Hereinafter, when the parent group is the departure place, it is described as the parent group (departure), and when the parent group is the arrival place, it is described as the parent group (arrival). Similarly, when a child group starts, it is described as a child group (departure), and when a child group ends, it is described as a child group (arrival).

[Parent Group (Departure) / Child Group (Destination)]
Based on the parent-child group information stored in the group information storage unit 24, the tabular totaling unit 141 determines the parent-child group from the shipper information of each trace record belonging to the trace record group A, and similarly determines the parent-child group from the shipper information. By associating with each other, each trace record belonging to the trace record group A is classified into two types of parent group (originating) / child group (arriving) and child group (departing) / parent group (arriving). At this time, a parent group name and a child group name may be added to each trace record.

The tabular totaling unit 141 collects and loads the numbers based on the collection registration data, estimated delivery time registration data, and delivery completion registration data in each trace record classified into the parent group (departure) and child group (arrival). The delivery number is counted in units of child groups.
By doing so, the tabular tabulation unit 141 aggregates the number of cargoes collected, loaded, and delivered from the parent group (from) to each child group (to). • Create aggregated data by child group (arrival) (hereinafter also referred to as “aggregate (number) data by parent group (departure) / child group (arrival))”.

  The tabular tabulation unit 141 tabulates the number of cargoes collected, loaded, and delivered based on the aggregate (number) data for each parent group (departure) and child group (arrival). Create parent group total (number) data.

  The tabular totaling unit 141 refers to the transportation history information (for example, the latest history information) of each trace record classified into the parent group (departure) and child group (arrival), and is in units of child groups (arrivals). By counting the number of pickups, the number of loads, the number of unloads, and the number of completed deliveries, the total number of pickups, the number of loads, and the number of unloaded items that are transported from the parent group (departure) to each child group (arrival) Creates aggregate data by parent group (departure) and child group (arrival) (hereinafter also referred to as "aggregation (number) data by parent group (departure) / child group (arrival))", which aggregates the number of cases and the number of completed deliveries can do.

  The tabular tabulation unit 141 is based on the total (number) data for each parent group (departure) and child group (arrival), and the number of cargoes collected from the parent group (departure), the number of loads, the number of unloading It is possible to create parent group (originating) total (number of cases) data that totals the number of cases and the number of completed deliveries.

[Child Group (Departure) Parent Group (Destination)]

The tabular totalization unit 141 counts the number of pickups, loadings and deliveries in units of child groups (originating) based on the registered data of each trace record classified into child groups (originating) and parent groups (arriving). To do.
By doing so, the tabular tabulation unit 141 sums up the number of pick-ups, loadings and deliveries of the transported cargo transported from each child group (departure) to the parent group (arrival). -Create aggregate data by parent group (arrival) (hereinafter also referred to as "child group (originating) / parent group (arrival) aggregated (number) data").

  The tabular tabulation unit 141 collects, loads, and delivers the transported cargo that is transported to the parent group (arrival) based on the data (total) by child group (departure) and parent group (arrival). Create parent group (arrival) tabulation (number) data.

  Further, the tabular form totaling unit 141 refers to the transportation history information (for example, latest history information) of each trace record classified into the child group (departure) and parent group (arrival), and the child group (departure) unit By counting the number of pickups, the number of loads, the number of unloads, and the number of completed deliveries, the total number of pickups, the number of loads, and the number of unloaded items that are transported from each child group (source) to the parent group (arrival) Create aggregate data by child group (originating) parent group (arrival) (hereinafter also referred to as "aggregation (number of cases) data by child group (departure) parent group (arrival)") that aggregates the number of cases and the number of completed deliveries. Can do.

  The tabular tabulation unit 141 collects, loads and unloads the transport cargo transported to the parent group (arrivals) based on the data (count) by child group (departure) parent group (arrivals). , And parent group (arrival) total (number of cases) data that totals the number of completed deliveries can be created.

  Further, when the trace record group A is stored in the user work area A for each collection date included in a date range including the previous day of the current date (for example, the past one week) in the user work area A, the tabular totalization unit 141 In addition, by referring to the delivery completion registration data of each trace record belonging to the trace record group A, picking up the pickup date on which there is a trace record that has not been registered for delivery completion, a list of pickup dates that have not been delivered can be obtained. A “incomplete pickup date list” can be created.

  The tabular tabulation unit 141 creates the total (number) data by parent group (departure) / child group (arrival), parent group (departure) total (number) data, and by child group (departure) / parent group (end). Aggregation (number) data, parent group (arrival) aggregation (number) data (hereinafter also referred to as “aggregation (number) data by parent and child group)” and parameters (search pattern type and collection date), user work area A To remember.

  In addition, the tabular tabulation unit 141 creates the total (number) data for each parent group (departure) / child group (end), parent group (outbound) count (number) data, child group (outbound) parent group (arrival) User work area by associating aggregated data (number) data, parent group (arrival) data (number) data (hereinafter also referred to as "summary data by parent group (number) data") with parameters (search pattern type and collection date) A can be stored.

  The tabular totalization unit 141 can store the created incomplete collection date list in the user work area A in association with parameters (search pattern type and collection date).

  After that, the tabular totaling unit 141 provides the editing unit 15 with the user ID, the totaling (number) data for each parent / child group, and the totaling (number of cases) data for each parent / child group together with the parameters (search pattern type and collection date).

[Processing for Search Pattern 4]
In the case of the search pattern 4, the map form totaling unit 142, based on the regional group (prefecture group) information stored in the group information storage unit 24, the shipper information of the shipper information of each trace record belonging to the trace record group B The departure group (prefecture code and prefecture name) is associated with the municipal JIS code, and the arrival group (prefecture code and prefecture name) is associated with the arrival municipality JIS code of the arrival party information. At this time, the source group name (prefecture name) and the destination group name (prefecture name) may be added to each trace record.

  The map format totaling unit 142 classifies each trace record belonging to the trace record group B in units of departure group (prefecture name).

The map form totaling unit 142 refers to the delivery completion registration data of each trace record classified by the departure group (prefecture name), and the delivery delay that has not been registered for each collection date and has a delivery delay has occurred. The group (prefecture name) is picked up, the collection date / delivery incomplete prefecture data (origin base) is created, and stored in the user work area B in association with the parameters (search pattern type and collection date).
Further, the map form totaling unit 142 picks up the collection date when the collection date / delivery incomplete prefecture data (origin base) is not an empty set, creates an “incomplete collection date list”, and sets parameters (search The data is stored in the user work area B in association with the pattern type and the collection date. The map format totaling unit 142 refers to the delivery completion registration data of each trace record belonging to the trace record group B for each collection date, and picks up the collection date on which there is a trace record that has not been registered for delivery completion. You may create an “Incomplete Pickup Date List”.

  In addition, the map form totaling unit 142 refers to the collection registration data of each trace record classified by the departure group (prefecture name), and selects the collection group (prefecture name) that is not registered for collection for each collection date. The data is picked up, and the prefectural data by collection date and no collection is created and stored in the user work area B in association with the parameters (search pattern type and collection date).

  Further, the map format totaling unit 142 classifies each trace record belonging to the trace record group B according to the arrival group (prefecture name) unit.

  The map form totaling unit 142 refers to the delivery completion registration data of each trace record belonging to the trace record group B classified by arrival group (prefecture name), and the delivery completion registration is not performed for each collection date. Picking up the delayed arrival group (prefecture name), creating the collection date / delivery incomplete prefecture data (landing base), correlating it with the parameters (search pattern type and collection date), and user work Store in area B.

  After that, the map form totaling unit 142 displays the user ID, collection date / delivery incomplete prefecture data (origin base), collection date / delivery incomplete prefecture data (landing base), collection date / no collection The prefecture data and the incomplete collection date list are provided to the editing unit 15 together with the parameters (search pattern type and collection date).

  Note that grouping in the map format is not limited by prefecture. It can be set as appropriate according to the characteristics of the regional distribution of the user's branch / branch / business office.

<Editor 15>
The editing unit 15 edits the delivery delay list data in a preset format based on each tabulated data tabulated by the tabulating unit 14, and at that time, predetermined data items to be alerted are preset. Edit the alert display format.

  The editing unit 15 includes a table format editing unit 151 and a map format editing unit 152.

[Table Format Editor 151]
In the case of the search pattern 1 or the search pattern 2, the table format editing unit 151 displays the group-by-group total (number) data (the total (number) data by calling group / arrival group) stored in the user work area A by the table-type totaling unit 141. Tabular data, totaling (number) data by calling group / arrival block, totaling (number) data by calling group, totaling data by calling block, totaling (number) data by calling group, and total tabulation (number) data) To edit.
Here, each total (number) data is composed of the number of collected goods, the number of loaded goods, and the number of delivered goods.
In addition, when the tabulated totaling unit 141 counts the number of picked up goods, the number of loaded goods, and the number of delivered items not for each group but for each departure and landing, the tabular editing unit 151 displays the tabulated data for each departure and landing. Can be edited into format data. In the following description, editing by group will be described, but the same processing is performed when editing by origin / landing.

When editing into tabular data, if the current time is past the loading alert threshold time preset in the alert time information storage unit 25, the total number of pieces of data (number) that the loaded number does not match the collected number The number of loaded items is edited into an alert display format (for example, a cell coloring format when displaying cells).
Further, when editing into tabular data, if the current time is past the delivery alert threshold time preset in the alert time information storage unit 25, the total number (number) of data for which the number of deliveries does not match the number of picked-up items The number of deliveries is edited into an alert display format (for example, in the case of displaying cells, a format for coloring cells).

In addition, when editing the table format data, the table format editing unit 151 links the collection number of each aggregate (number) data with the trace record set corresponding to the collection number.
When linking trace record sets, it is possible to link the search conditions used when creating the trace record list. For example, in the case of a collection number link, the search pattern type, collection date, departure group name, and arrival group name are used. The search condition may be a list of invoice numbers of trace records included in the trace record list.

In the case of the search pattern 3, the table format editing unit 151 stores the total (number) data and the parent group (source) by parent group (originating) / child group (arriving) stored in the user work area A by the tabular aggregation unit 141. ) Total (number) data, and tabular data ("Transportation status management table") for each child group (departure) and parent group (arrival), respectively (number) data and parent group (arrival) total (number) data Edit to
In addition, the tabular totaling unit 141 sets the number of pickups, loadings, and deliveries in units of origin (parent) / landing (child) and origin (child) / landing (parent), not by group. When tabulated, the table format editing unit 151 can edit the table format data in units of origin (parent) / landing (child) and origin (child) / landing (parent). In the following description, editing by group will be described, but the processing in the case of editing in units of origin (parent) / landing (child) and in units of origin (child) / landing (parent) is the same.
At that time, the tabular format editing unit 151 links the trace record set corresponding to the collected number to the collected number of each aggregated (number) data as in the case of the search pattern 1 and the search pattern 2.

  Similarly to the case of the search pattern 1 and the search pattern 2, the tabular format editing unit 151 displays the number of loads when the current time is past the loading alert threshold time preset in the alert time information storage unit 25. Is the number of the collected (count) data that does not match the number of collection, and if the current time is past the delivery alert threshold time preset in the alert time information storage unit 25, the delivery number is the number of collection The number of deliveries in each aggregated (number) data that does not match is edited in an alert display format (for example, in the case of cell display, a format for coloring the cell of the delivery number).

  Further, the table format editing unit 151 displays the number of collected items in an alert display format when the current time has passed the collection alert threshold time preset in the alert time information storage unit 25 and the number of collected items at the current time is zero. (For example, in the case of displaying cells, the number of cells collected is colored). By doing so, it is possible to warn the user that there is a high possibility that some irregular circumstances occur in the originating group and the transported cargo is in an uncollected state.

  Note that the table format editing unit 151, as in the case of the search pattern 1 and the search pattern 2, when editing in the alert display format, all the tabulations including the tabulated data edited in the alert display format as a breakdown ( The (number) data (for example, total column) is also edited in an alert display format (for example, a cell coloring format when displaying cells).

  Further, the table format editing unit 151 stores each uncollected pickup that is included in the unfinished collection date list that is stored in the user work area A by the table format totaling unit 141 and that is a list of uncollected collection dates. Each day, a set of trace records of the cargo collected on the collection date is linked (“collection date link”). When linking trace record sets, search conditions used when creating trace record sets can be linked. In the case of a collection date link, it is the type of search pattern and the collection date. The search condition may be a list of invoice numbers of trace records included in the trace record list.

  Referring to FIG. 7C, the table format editing unit 151, for example, has the total (number) data of the departure group “Dohoku” and the arrival group “Group B”, the number of pickups is 3, the number of loads is 1, When the number of deliveries is one and the current time is past the loading alert threshold time and the delivery alert threshold time, an alert display format (for example, a cell coloring format) is displayed for the loaded number and the delivered number of the aggregated data. ).

Referring to FIG. 7D, for example, in the child group (departure), the tabular format editing unit 151 has the aggregated (number) data of “Miyagi Prefecture” with 10 collection numbers, 8 loading numbers, and delivery. When the number is 10 and the current time has passed the first set time, the loaded number data of the aggregated data is edited in an alert display format (for example, a cell coloring format).
Note that the table format editing unit 151 also edits the total tabulation (number) data into an alert display format (for example, a format for coloring cells).

  The table format editing unit 151 can store the created transportation status collective management table and incomplete collection date list in the user work area A in association with parameters (search pattern type and collection date).

  After that, the table format editing unit 151 provides the user ID, the transport status collective management table, and the uncompleted collection date list to the inter-terminal interface unit 12 together with parameters (search pattern type and collection date).

[Map format editor 152]
The map format editing unit 152 stores the collection date / delivery incomplete prefecture data (origin base) stored in the user work area B by the map format totaling unit 142 and the collection date / delivery incomplete prefecture data (landing) Base) is edited into map format data (transportation status management map).
Specifically, as shown in FIG. 7A, the Japanese map format data describing each prefecture is edited on the basis of departure or landing. At that time, the map format editing unit 152 alerts the prefecture where the collection date is the previous day and the delivery has not been completed based on the incomplete delivery state data (origin base) or the incomplete delivery state data (landing base). Edit the display format (for example, specify a color for the corresponding prefecture).
For example, departure-based Japan map format data (referred to as “transportation status (departure-based) collective management map”) is created as a default and landing-based Japan map format data (“transportation status” (Landing base) collective management map ”).

  Further, the map format editing unit 152 edits the prefectures without collection into the alert display format when editing the Japanese map format data describing each prefecture based on the prefecture data without collection (for example, in the corresponding prefectures). Color designation) (referred to as “transportation status (no collection) collective management map”).

  Further, the map format editing unit 152 links a set of trace records starting and ending with the prefecture to the name of each prefecture based on the origin (prefecture name link). When linking trace record sets, it is possible to link search conditions used when creating a trace record list. In the case of the prefecture name link, the search condition is “type of search pattern (search pattern 4), collection date, designation of departure base or landing base, and prefecture code”. The search condition may be a list of invoice numbers of trace records included in the trace record list.

  The map format editor 152 creates the transport status (departure base) batch management map, the transport status (landing base) batch management map, the transport status (no pickup) batch management map (hereinafter referred to as “transport status batch management map”). , And each prefecture name link can be stored in the user work area B in association with parameters (search pattern type and collection date).

Thereafter, the map format editing unit 152 provides the inter-terminal interface unit 12 together with the parameters (search pattern type and collection date) along with the transportation status collective management map and each prefecture name link.
At this time, since session management is performed for the same transaction, the user ID, session management number, and the like are handed over to the editing unit 15.

<Group inquiry section 16>
The group inquiry unit 16 acquires parameters from the inter-terminal interface unit 12 and creates a trace record list. Here, as described above, the parameter can be the search condition used when creating the trace record list. For example, in the case of a collection number link, the search pattern type, collection date, departure group name, and arrival group name are used. In the case of the prefecture name link, the type of search pattern (search pattern 4), the date of collection, the designation of the departure base or landing base, and the prefecture code are used. In the case of a collection date link, it is the type of search pattern and the collection date.
The parameter may be a list of invoice numbers of trace records included in the trace record list.

  For example, as shown in FIG. 7E, the group inquiry unit 16 uses the data of each trace record (branch / branch / office information, invoice number, number, weight, collection store, delivery store, latest status, delivery completion date, etc.) Is edited into tabular data. At this time, the undelivered trace record is edited into an alert display format (for example, coloring is specified for a cell to be stored).

  Thereafter, the group inquiry unit 16 provides the trace record list together with the parameters to the inter-terminal interface unit 12.

<Single inquiry section 17>
The single inquiry unit 17 uses the designated invoice number as a key, for example, as shown in FIG. 7E, data items of the trace record, for example, latest transportation status, transportation status details, departure information, landing information, collection and delivery Edit history information in tabular format.

  Thereafter, the single case inquiry unit 17 provides the single case inquiry data to the inter-terminal interface unit 12 together with the parameters.

<Edit processing by the inter-terminal interface unit 12>
Finally, processing when the inter-terminal interface unit 12 transmits output data provided from another functional unit to the terminal 1 via the communication unit 30 will be described.

[Data acquired from the tabular format editing unit 151]
The inter-terminal interface unit 12 converts the transportation status batch management table and the aggregate date link respectively edited by the table format editing unit 151 into a preset record format and provides it to the terminal 1 via the communication network 3. .
When the inter-terminal interface unit 12 uses a preset record format as a document marked up by HTML (hereinafter also referred to as “HTML document”), the inter-terminal interface unit 12 shows, for example, those shown in FIGS. 7C and 7D. As shown, the transport status batch management table is edited in the alert display format, the cells storing the number of loaded and delivered items are colored, and the HTML record format is linked to the collection number link and the trace record list is linked Convert.
Further, the inter-terminal interface unit 12 edits the collection date link in which the delivery of all the transported cargo included in the incomplete list is not completed in the “incomplete” column.
As described above, when linking trace record sets, the search conditions used when creating the trace record list can be linked. For example, in the case of a collection number link, the search pattern type, collection date, departure group name, and arrival group name are used. In the case of a collection date link, it is the type of search pattern and the collection date. The search condition may be a list of invoice numbers of trace records included in the trace record list.
Further, the inter-terminal interface unit 12 newly adds an “update” button and a “download” button, respectively, and converts them into, for example, an HTML data format with a script.

In this way, the inter-terminal interface unit 12 creates an HTML document with a script corresponding to the transportation status batch management search screen shown in FIG. 7C, for example, and provides it to the terminal 1 via the communication network 3.
The terminal 1 can display the script-attached HTML document transmitted from the server 2 by the display control unit 12A.
By doing so, the terminal 1 can display a list of all the trace records included in the collection number by pressing (clicking) the collection number link.
In addition, when the collection date link in the “incomplete” column is pressed (clicked), the terminal 1 similarly displays a list of all trace records having the collection date as the date as shown in FIG. 7E. Can be displayed.
In addition, when the “update” button is pressed (clicked), the terminal 1 reprocesses from the search processing of the search unit 13 so that the latest data is reflected in the transportation status batch management table and the aggregate date link. In addition, a request can be made to the server 2.
Further, the terminal 1 can download the transportation status batch management table to the terminal 1 by pressing (clicking) the “download” button.

[Data acquired from the map format editor 152]
When the inter-terminal interface unit 12 converts the transportation status collective management map and the prefecture name link edited by the map format editing unit 152 into, for example, an HTML document, as shown in FIG. 7B, the inter-terminal interface unit 12 The transport status (departure base) collective management map, the transport status (landing base) collective management map, and the transport status (no pickup) collective management map edited by the map format editing unit 152 are edited in the alert display format. Edit the HTML document that colors the area where the prefecture name is stored. At that time, it is converted into the HTML data format in which the trace record list is linked to the prefecture name link.
At that time, the inter-terminal interface unit 12 edits the HTML data format in which the trace record list is linked to the prefecture name link, and designates “departure base”, “landing base”, or “no pickup”. It is possible to edit an HTML document with a script in which a radio button is newly provided.
As described above, when linking trace record sets, the search conditions used when creating the trace record list can be linked. In the case of the prefecture name link, the type of search pattern (search pattern 4), the date of collection, the designation of the departure base or landing base, and the prefecture code are used. The search condition may be a list of invoice numbers of trace records included in the trace record list.

In this way, the inter-terminal interface unit 12 creates an HTML document with a script corresponding to the transportation status batch management search screen shown in FIG. 7B, for example, and provides it to the terminal 1 via the communication network 3.
The terminal 1 can display the script-attached HTML document transmitted from the server 2 by the display control unit 12A.
By doing so, the terminal 1 displays the transportation status (origin base) collective management map when the “origin base” button is pressed (clicked).
Similarly, when the “landing base” button is pressed (clicked), the terminal 1 displays the transportation status (landing base) collective management map.
Further, the terminal 1 displays a transportation status (no pickup) collective management map when a “no pickup” button is pressed (clicked).
As described above, the terminal 1 can switch between the collective management maps of “departure base”, “landing base”, or “no pickup” according to the click of the radio button.
In addition, the terminal 1 can display a trace record list that starts and ends in the prefecture by pressing (clicking) the prefecture name link.

[For trace record list display]
When the inter-terminal interface unit 12 converts the trace record list edited by the group inquiry unit 16 into, for example, an HTML document, for example, as shown in FIG. 7E, the record edited in the alert display format is colored. The HTML document to be edited can be edited.
In that case, edit the HTML data format linked to the single inquiry that displays the detailed information of the trace record corresponding to the number in the invoice number of each record, and select “Display all items” or “Display only undelivered”. It is possible to edit an HTML document with script in which a radio button to be specified is newly provided.

In this way, the inter-terminal interface unit 12 creates an HTML document with a script corresponding to the trace record list shown in FIG. 7E, for example, and provides it to the terminal 1 via the communication network 3.
The terminal 1 can display the script-attached HTML document transmitted from the server 2 by the display control unit 12A.
By doing so, the terminal 1 can display the details of the trace record corresponding to the invoice number as shown in FIG. 7F when the invoice number in the trace record list is pressed (clicked).
Further, the terminal 1 can switch between displaying all items or displaying only undelivered in response to pressing (clicking) of the “display all items” button or the “display only undelivered” button.

[In case of single inquiry]
Referring to FIG. 7F, the inter-terminal interface unit 12 displays detailed information (for example, the latest transportation status, departure information, landing information, collection / delivery history information, etc.) of the trace record edited by the single case inquiry unit 17. Can be mapped to an HTML document.

  As described above, the inter-terminal interface unit 12 includes, for example, an HTML document conversion function. By doing so, for example, control buttons such as radio buttons and update buttons can be edited as appropriate.

(Operation of system 100)
The configuration of the transportation status batch management search system 100 has been described above. Next, the operation of the transportation status batch management search system 100 will be described. 8A to 8C are flowcharts showing the flow of processing of the transportation status batch management search system 100.

  First, with reference to FIG. 8A, a processing flow from when the terminal 1 is connected to the server 2 to when a screen for displaying a menu and a transportation status batch management map is received will be described.

[After connecting to the server 2 until the menu and the transport status management map are displayed]
Referring to FIG. 8A, in step ST101, the terminal 1 transmits a login request (connection request) to the server 2 using a user ID and a password.

  In step ST201, the server 2 (the inter-terminal interface unit 12) requests the login processing unit 11 to perform a connection process with the terminal 1.

In step ST202, the server 2 (retrieval unit 1) traces the trace records of all the transported cargo collected on the preset collection date (for example, the previous day) among the consignor's transported cargo linked to the user ID. Search and extract from the database 21.
In addition, about the user who uses three search patterns in combination, it corresponds to the search pattern with a high priority set beforehand among three search patterns.

  In step ST203, the server 2 (map format totaling unit 142) determines the collection date / delivery incomplete prefecture data (origin base), collection date / delivery incomplete prefecture data (landing base), collection date / Create prefectural data without collection and a list of incomplete collection days.

  In step ST204, the server 2 (map format editing unit 152) creates the collection date / delivery incomplete prefecture data (origin base), collection date / delivery incomplete prefecture data (landing base) created in step ST203. ) Based on the collection date / non-collection prefecture data and the uncompleted collection date table, create a transportation status management map and prefecture name link.

  In step ST205, the server 2 (the inter-terminal interface unit 12) converts the transportation status batch management map and the prefecture name link created in step ST204 into an HTML document.

  In step ST206, the server 2 adds the HTML document created in step ST205 to the menu and transmits it to the terminal 1.

  In step ST102, the terminal 1 displays the menu and the transport status collective management map received from the server 2 (see, for example, FIGS. 7A and 7B).

[Process when search pattern 1 or pattern 2 is selected]
Next, a processing flow when search pattern 1 is selected on the menu screen of terminal 1 will be described with reference to FIG. 8B. Since the processing flow when the search pattern 2 is selected is the same, the description is omitted.
In step ST <b> 111, the terminal 1 selects the search pattern 1 and the collection date and transmits it to the server 2.

  In step ST211, the server 2 (search unit 1) selects all the transport cargoes collected on the specified collection date among the consignor's transport cargoes linked to the user ID according to the search pattern 1 or the search pattern 2. Trace records are retrieved from the trace database 21.

  In step ST212, the server 2 (the tabular tabulation unit 141) sums up the number of picked up, loaded, and delivered items of the transported cargo transported from the originating group to the terminating group (total) by the originating group / arriving group. Create data. In addition, an unfinished collection date list that is a list of collection dates that have not been delivered is created.

  In step ST213, the server 2 (table format editing unit 151) determines the number of loadings determined to be unloaded or undelivered based on the total (number) data for each calling group / arrival group created in step ST212. Edit the delivery quantity in the alert display format and create a transportation status batch management table that links the collection of trace records corresponding to the collection quantity. In addition, a trace record set is linked to a pickup date that has not been delivered and is included in the incomplete pickup date list created in step ST212.

  In step ST214, the server 2 (the inter-terminal interface unit 12) converts the transportation status batch management table and the unfinished collection date list created in step ST213 into HTML data formats, respectively, and newly adds an “update button”. And an HTML data with script corresponding to the “download button”, and an HTML document with script corresponding to the transportation status batch management search screen is created.

  In step ST215, the server 2 transmits the script-attached HTML document created in step ST214 to the terminal 1.

  In step ST112, the terminal 1 displays the HTML document with script (pattern 1 or pattern 2) received from the server 2 (see FIG. 7C).

[Processing when search pattern 3 is selected]
Next, with reference to FIG. 8C, a processing flow when the search pattern 3 is selected on the menu screen of the terminal 1 will be described.

  In step ST <b> 121, the terminal 1 selects the search pattern 3 and the collection date and transmits it to the server 2.

  In step ST221, the server 2 (search unit 1) traces the trace records of all the transported cargo collected on the specified collection date among the consignor's transported cargo linked to the user ID according to the search pattern 3. Search and extract from the database 21.

  In step ST221, the server 2 (first search unit 1) traces the transportation cargo collected on the designated collection date among the transportation cargos of the shipper associated with the user according to the selected retrieval pattern 3. Records are retrieved from the trace database 21 and extracted.

  In step ST222, the server 2 (the tabular totaling unit 141) sums up the number of pick-ups, loadings, and deliveries of the transport cargo with the parent group as the originating group and the child group as the destination group. Create total (number) data B for each child group.

  In step ST223, the server 2 (the tabular totaling unit 141) sums up the number of pick-ups, loadings, and deliveries of the transport cargo having the child group as the originating group and the parent group as the destination group. Total data (number) data B by parent group (arrival) is created. In addition, an unfinished collection date list that is a list of collection dates that have not been delivered is created.

  In step ST224, the server 2 (table format editing unit 151) determines the total (number) data by parent group (originating) and child group (arrival) created in step ST222, or the child group (originating) created in step ST222. ) ・ Based on the aggregated (number) data by parent group (arrival), edit the number of picked-up, loaded or undelivered items that are judged as uncollected, unloaded or undelivered in the alert display format, and the number of collected items Create a transportation status batch management table that links trace record record sets corresponding to. In addition, the server 2 (table format editing unit 151) links the trace record set to the collection date with uncompleted delivery included in the uncompleted collection date list created in step ST222.

  In step ST225, the server 2 (the inter-terminal interface unit 12) converts the transportation status batch management table and the incomplete pickup date list created in step ST224 to the HTML data format, and newly adds an “update button”. And an HTML data with script corresponding to the “download button”, and an HTML document with script corresponding to the transportation status batch management search screen is created.

  In step ST226, the server 2 transmits the script-added HTML document created in step ST225 to the terminal 1.

  In step ST122, the terminal 1 displays the script-attached HTML document (pattern 1 or pattern 2) received from the server 2 (see FIG. 7D).

  The embodiment of each functional unit of the transportation status batch management search system 100 of the present invention has been described above based on the configuration of the terminal 1 and the server 2. However, the embodiment of each functional unit included in the transportation status collective management search system 100 of the present invention may be a single computer or a large number of computers in one place or distributed in several places and interconnected by a communication network. Can be deployed to run in a distributed manner. It can also be configured using a plurality of virtual computers on the cloud.

  For example, when the server 2 is distributedly processed by a plurality of computers, each function of the server 2 can be executed by any computer. Accordingly, those skilled in the art can appropriately design which computer the functions of the server 2 are assigned to.

  As mentioned above, although preferred embodiment was described, this invention can be implemented with a various form, without being limited to embodiment mentioned above. The effects described in the above-described embodiment only list the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described above.

[Modification 1]
In the first embodiment, when linking the trace record list, a parameter including a search condition for specifying the trace record list, for example, in the case of a collection number link, a search pattern type, a collection date, a group name, and For parameters that include the arrival group name, for the prefecture name link, for the search pattern type (search pattern 4), collection date, origination or landing base designation, and parameters that include the prefecture code, and for the collection date link The search pattern type, the parameter including the pickup date, or the set of invoice numbers included in the trace record list is linked, but the present invention is not limited to this.
For example, the trace record list is created in advance by the totaling unit 14 or the editing unit 15 and the created trace record list is included in the HTML document in the conversion to the HTML document by the inter-terminal interface unit 12. Then, it may be linked to the trace record list in the HTML document.
Further, a trace record list may be stored in the user work area A or the user work area B by the totaling unit 14 or the editing unit 15 and linked to the trace record list.

[Modification 2]
Although 1st Embodiment demonstrated the system aspect for users (customers) in which a user (customer) searches the trace record linked | related with own user ID, it is not limited to this.
For example, it is possible to provide a transportation status centralized management search function related to a user's transportation cargo to a customer representative of a secretary store corresponding to the user (customer). This can be done by giving the customer's person in charge at the managing store the authority to access the customer's user ID and the consignor code information associated therewith, and permitting the activation of the transportation status batch management search function unit.
For example, in the storage unit 20, the user ID of a customer who is permitted to perform the transportation status centralized management search for the customer representative is associated with the administrator ID of the administrator in advance, and stored in the user management information storage 23. The access authority to the customer's user ID and the shipper code information associated therewith is given, and the activation of the transportation status batch management search function unit is permitted.
Further, a search request including a menu for an administrator who can input a user ID of a customer who is a search target of transportation status in addition to a search pattern and a collection date, and a customer user ID of the manager in charge of the secretary store Prepare a request.
Then, when the login processing unit 11 performs authentication processing of the customer clerk ID and the inter-terminal interface unit 12 permits the customer clerk ID to perform a unified management search for the transportation status of the customer (user ID). By analyzing the search request request including the user ID of the customer from the customer staff and requesting the processing to the search unit 13, the transportation situation of the user's transportation cargo is unified with respect to the customer staff of the managing store. A management search function can be provided.
In addition to the inter-terminal interface unit 12 corresponding to the user (customer), a terminal-to-terminal interface unit corresponding to the customer representative of the managing store may be newly provided.

[Modification 3]
In the first embodiment, the tabular totaling unit 141 selects each trace record belonging to the trace record group A based on the group information stored in the group information storage unit 24 as a source group / termination group unit or a parent group (source group). ) ・ Child group (arrival) and child group (departure) / parent group (arrival) parent group / child group unit, the number of picked up goods, the number of loaded goods, and the number of delivered parts, respectively Or the parent group (departure) / child group (arrival) and child group (departure) / parent group (arrival) are counted in parent group / child group units, and the table format editing unit 151 is grouped by the table format aggregation unit 141. The counted summary data has been edited into a tabular format for each group, but is not limited to this.
The tabular tabulation unit 141 collects each trace record belonging to the trace record group A with the origin / landing unit or one origin (and landing) as the parent and the remaining origin (and landing) as the child. , Loading quantity and delivery quantity for each origin / landing unit or parent / child unit of parent origin (departure) / child landing (landing) and child origin (departure) / parent landing (landing) The tabular format editing unit 151 may count the tabulated data individually counted by the tabular format totaling unit 141 into a tabular format for each departure / landing.

[Modification 4]
As described above, the sales management database 22 manages accounts receivable in units of invoice numbers for identifying a waybill. In addition, it is possible to determine whether or not the transport cargo related to the waybill relates to the inter-company transport service, the external transport service, and the collection transport service based on the accounts receivable code.
Whether or not the user (customer) is a user of the transportation collective management search service can be determined by the user management information storage unit 23.
Therefore, based on the sales management database 22, for the user (customer) who uses the transportation collective management search service of the present invention, the transportation cargo related to the in-house transportation service, the outside transportation service, and the collection transportation service is conventionally known. In addition to the transportation fee, the transportation collective management search service utilization fee of the present invention can be charged.

  According to the transport status centralized management search system 100 described above, the following effects can be obtained.

  According to the transport status batch management search screen provided by the search pattern 1 (external transport service) in the transport status centralized management search system 100 of the above embodiment, it is randomly selected from the branches (branches / branches / offices) of users (customers) in the whole country. For example, the headquarters of the user (customer) can grasp the transportation status of the cargo sent to the customer (delivery destination) of the user (customer) in a unified manner, and can supervise the whole. By doing so, the customer's (customer) customer satisfaction is improved by seeing the transportation status from the collection of all cargo shipped from the user's (customer's) branch / branch office and office to the completion of delivery. This has the effect of reducing the number of inquiries from.

  According to the transport status collective management search screen provided by search pattern 2 (collected transport service) in the transport status centralized management search system 100 of the above embodiment, it is easy to check the collection schedule information, the procurement schedule information, and the collected transport status. In addition, it becomes possible to quickly catch up cases where collection, loading and delivery are delayed due to some irregular circumstances during collection and transportation. In addition, it has become easier to investigate “uncollected goods”, which conventionally cannot be known without confirming the telephone with the collection shop. In addition, it is possible to collectively check the arrival of all the amounts that have conventionally been performed on a paper basis.

  According to the transport status collective management search screen provided by search pattern 3 (in-house transport service) in the transport status centralized management search system 100 of the above embodiment, for example, it is possible to instantly grasp the transport status of cargo on the basis of arrival at the head office. . In-house transportation services are generally scheduled for daily collection and delivery times, as well as schedules for visiting branches, branch offices, and offices. By warning the case where loading and delivery are delayed, the user (customer) can catch up quickly. In addition, it has become easier to investigate “uncollected goods”, which conventionally cannot be known without confirming the telephone with the collection shop. In addition, it is possible to collectively check the arrival of all the amounts that have conventionally been performed on a paper basis. In addition, it is possible to grasp the reciprocal movement of intra-company transportation.

  According to the transport status collective management search screen provided by the search pattern 4 (transport status collective management map function) in the transport status centralized management search system 100 of the above embodiment, the external transport service and the recovered transport service which are set in advance are set. In addition, it is possible to intuitively grasp the transportation status in any one of the intra-company transportation services by switching between the departure base and the landing base. When an irregular situation occurs and the delivery is delayed, an alert is displayed for each irregular prefecture, so that the prefecture where the transportation delay occurs can be grasped instantly.

According to the uncompleted collection date list of the transportation status collective management search screen in the transportation status centralized management search system 100 of the above embodiment of the present invention, undelivered among the shipments whose collection date is the date of the past week. It is possible to warn when there is a freight in state.
By doing so, it becomes possible to instantly grasp the collection date on which the transportation delay has occurred in the past week, and thereafter, it becomes possible to efficiently investigate the situation in which the transportation delay has occurred.

In the transport status centralized management search system 100 of the above embodiment of the present invention, the transport delay status for each departure / landing is collectively displayed for each collection date, for example, the origin / landing where the transport delay occurs is identified. In addition, for example, when the collection number link or the prefectural link is pressed, a trace record list showing the transportation status at the departure / landing where the transportation delay occurs can be displayed. By doing so, it is possible to easily identify a case where delivery has not been completed, and to take measures against it.
Further, when displaying the trace record list, the display of all cases and the non-delivery case display can be switched with radio buttons, and only the non-delivery case items can be displayed. Further, the details of the trace record of the undelivered item can be displayed by the invoice number link.
In this way, it is possible to perform an efficient investigation by enabling the immediate display of the details of individual projects that are in a delayed delivery state from a batch display of the state of transportation delay by departure / landing for each pickup date. And

The transportation status batch management search function of the present invention can be executed by hardware or can be executed by software.
In other words, the functional configurations of FIGS. 3 and 4 are merely examples, and are not particularly limited. That is, it is only necessary that the terminal 1 and the server 2 have a function capable of executing a series of processes related to the transportation status collective management search function of the present invention as a whole, and what functional block is used to realize this function. Is not particularly limited to the examples of FIGS.
In addition, one functional block may be constituted by hardware alone, software alone, or a combination thereof.

When a series of processing is executed by software, a program constituting the software is installed on a computer or the like from a network or a recording medium.
The computer may be a computer incorporated in dedicated hardware. The computer may be a computer capable of executing various functions by installing various programs.

  A recording medium including such a program is provided not only to the removable medium 31 distributed separately from the apparatus main body in order to provide the program to the user, but also to the user in a state of being incorporated in the apparatus main body in advance. Recording medium. The removable medium 31 is composed of, for example, a magnetic disk (including a floppy disk), a Blu-ray disk, an optical disk, a magneto-optical disk, or the like. The optical disk is composed of, for example, a CD-ROM (Compact Disk-Read Only Memory), a DVD (Digital Versatile Disk), or the like. The magneto-optical disk is configured by an MD (Mini-Disk) or the like. In addition, the recording medium provided to the user in a state of being preinstalled in the apparatus main body includes, for example, the storage unit 20A in FIG. 3 in which the program is recorded, the hard disk included in the storage unit 20 in FIG. The

100: Transportation status collective management search system 1: Terminal 10A: Control unit 11A: Login processing unit 12A: Inter-terminal interface unit 20A: Storage unit 30A: Communication unit 40A: Display unit 50A: Input unit 2: Server 10: Control unit 11 : Login processing unit 12: Inter-terminal interface unit 13: Search unit 14: Totaling unit 141: Table format totaling unit 142: Map format totaling unit 15: Editing unit 151: Table format editing unit 152: Map format editing unit 16: Group inquiry Unit 17: Single case inquiry unit 20: Storage unit 21: Trace database 22: Sales management database 23: User management information storage unit 24: Group information storage unit 25: Alert time information storage unit 30: Communication unit 40: Display unit 50: Input unit 3: Communication network

Claims (10)

A server that is communicably connected to a terminal via a communication network,
The server
A communication department;
For collection of cargo handled by the carrier, at the time of collection of the shipment by the carrier, at least the invoice number, the collection date, the collection time, the number of collections, the shipper information, and the shipper information for identifying the waybill are registered. When registered and loaded on a transportation freight delivery vehicle, at least the loading processing date, loading time, and the number of loadings are registered, and the scheduled delivery time is registered. By registering delivery completion, registering delivery time and number of deliveries, it is possible to centrally register and manage the passing results of each stage of transportation from collection to delivery completion at the point of departure of all transported cargo A trace database that stores trace records;
The carrier provides an in-house transportation service for collecting and delivering transportation cargo between the user's head office and a plurality of branches, branch offices, offices, or group companies for a given user. In the case where the user's headquarters, a plurality of branches, branch offices, offices, or group companies provide an outside transportation service for collecting transportation cargo and delivering it to an outside consignee, or according to an instruction from the user In the case of carrying out a collection transportation service that collects transportation cargo from the user's business partner or group company and delivers it to a pre-designated delivery destination, each of the inter-company transportation service, the outside transportation service, or the collection transportation service User management for storing association information in which user identification information of the user and a shipper code as a billing destination for transportation freight charges are associated in advance for each service And the broadcast storage unit,
In response to a transport status search request including the collection date of transported cargo handled by the inter-company transport service, the external transport service, or the collection transport service, the user identification information stored in the user management information storage unit A search unit that searches and extracts a trace record of the transported cargo collected on the collection date from the trace database among all the transported cargo having the shipper code attached as a shipper;
Using the trace record extracted by the search unit as an input, the undelivered state of the transported cargo collected on the collection date is classified by the predetermined unit of the departure, by the predetermined unit of the landing, or by the predetermined of the departure A totaling unit that creates totaled information for each predetermined unit of departure / landing consisting of an arbitrary combination of a unit and a predetermined unit of the landing;
The totaling unit counts the predetermined unit of the departure, the predetermined unit of the landing, or the predetermined unit of the departure / landing including any combination of the predetermined unit of the departure and the predetermined unit of the landing. Based on the aggregate information on the undelivered status of the transported cargo collected on the date of collection, the transport status collective management information in a preset format is edited. Edit the predetermined unit of the ground, the predetermined unit of the landing, or the predetermined unit of the landing and the landing, which is an arbitrary combination of the predetermined unit of the landing and the predetermined unit of the landing, into a preset alert display format The place of departure / landing, which is edited in the transportation status collective management information, and includes a predetermined unit of the departure, a predetermined unit of the landing, or an arbitrary combination of the predetermined unit of the departure and the predetermined unit of the landing A trace record of the transport cargo collected on the date of collection with the unit as the origin or the landing is a predetermined unit of the origin, the predetermined unit of the landing, or any of the predetermined unit of the origin and the predetermined unit of the landing An editing section that links to a predetermined unit of departure / landing consisting of a combination,
The server, wherein the transportation status batch management information edited by the editing unit is transmitted to the terminal via the communication unit. The counting unit is
By using the trace record extracted by the search unit as an input, a departure point by a predetermined unit of the departure point, a predetermined unit of the landing point, or an arbitrary combination of the predetermined unit of the departure point and the predetermined unit of the landing point -A tabular totaling unit that totals the number of cargoes collected, loaded, and delivered for each predetermined unit of landing,
The editing unit
The tabular totaling unit sums up each predetermined unit of origin, each predetermined unit of landing, or each predetermined unit of origin / landing consisting of an arbitrary combination of the predetermined unit of landing and the predetermined unit of landing The number of picked up, loaded and delivered of the transported cargo is edited into tabular data with either one of the predetermined unit of departure and the predetermined unit of landing as a row and the other as a column,
When the current time has exceeded a preset loading alert threshold time, the totaling unit determines whether each of the predetermined units of the departure, each predetermined unit of the landing, or the predetermined unit of the departure and the landing When the total number of loadings is not the same as the number of picked up for each predetermined unit of departure / landing consisting of an arbitrary combination of predetermined units, edit the loading number in an alert display format,
When the current time has passed a preset delivery alert threshold time, the totaling unit performs the predetermined unit of the departure, the predetermined unit of the landing, or the predetermined unit of the departure and the predetermined of the landing. When the aggregated delivery quantity does not match the collection quantity for each predetermined unit of departure / landing consisting of an arbitrary combination of units, including a table format editing unit for editing the delivery quantity into an alert display format,
The server according to claim 1. The tabular format editing unit further includes:
When the current time has exceeded a preset collection alert threshold time, the totaling unit performs the predetermined unit of the departure, the predetermined unit of the landing, or the predetermined unit of the departure and the predetermined of the landing. When the total number of collections is zero for each predetermined unit of departure / landing consisting of an arbitrary combination of units, edit the collection number in an alert display format.
The server according to claim 2. The tabular format editing unit further includes:
A cell corresponding to each predetermined unit of departure, landing, or predetermined unit of landing, or any combination of the predetermined unit of landing and the predetermined unit of landing in the tabular data The predetermined number of landings, a predetermined unit of the landing, or a predetermined unit of the landing / landing consisting of any combination of the predetermined unit of the landing and the predetermined unit of the landing The server according to claim 2 or 3, wherein trace records of transportation cargo collected at the collection date to be landed are linked.   5. The server according to claim 1, wherein the predetermined unit of departure and the predetermined unit of landing are one departure and one landing, respectively. The server further includes:
Information on the originating group obtained by grouping the origin of the transport cargo in the inter-company transport service, the external transport service, or the collection transport service according to the conditions set in advance in each service; A group information storage unit that stores information on landing groups obtained by grouping the landing of the transport cargo in the external transportation service or the collection transportation service according to the conditions set in advance in each service;
The counting unit sets the departure group and the arrival group set based on the information on the departure group and the information on the arrival group stored in the group information storage unit as the predetermined unit of departure and the predetermined unit of landing, respectively. The server according to any one of claims 1 to 4. The predetermined unit of the departure point is a departure group obtained by grouping the departure point in a unit of a preset region,
The predetermined unit of landing is a landing group in which the landing is grouped by the unit of the region,
The pickup date is the day before the current date,
The editing unit
Map format data in which area names of units of the areas are arranged as aggregate information obtained by aggregating the undelivered state of transported cargo collected on the collection date by the origination group or the arrival group by the aggregation unit Edit to
When there is a transport cargo that has been picked up on the pick-up date and has not been delivered on the current date that is the next day of the pick-up date, the region name of the unit of the region that is the originating group including the origin of the transport cargo is placed Edit the location to alert display format,
Where there is a transported cargo that has been collected on the date of collection and has not been delivered on the current date that is the next day of the date of collection, the location where the name of the unit of the region that will be the landing group that includes the landing of the transported cargo is placed Including a map format editor that edits to alert display format
The server according to claim 1. The map format editing unit further includes:
The trace name of the transport cargo collected at the collection date is linked to the region name at the location where the region name is arranged, and the departure group or the arrival group is the origin or the landing respectively. Server. Server
For collection of cargo handled by the carrier, at the time of collection of the shipment by the carrier, at least the invoice number, the collection date, the collection time, the number of collections, the shipper information, and the shipper information for identifying the waybill are registered. When registered and loaded on a transportation freight delivery vehicle, at least the loading processing date, loading time, and the number of loadings are registered, and the scheduled delivery time is registered. By registering delivery completion, registering delivery time and number of deliveries, it is possible to centrally register and manage the passing results of each stage of transportation from collection to delivery completion at the point of departure of all transported cargo A trace database that stores trace records,
The carrier provides an in-house transportation service for collecting and delivering transportation cargo between the user's head office and a plurality of branches, branch offices, offices, or group companies for a given user. In the case where the user's headquarters, a plurality of branches, branch offices, offices, or group companies provide an outside transportation service for collecting transportation cargo and delivering it to an outside consignee, or according to an instruction from the user In the case of carrying out a collection transportation service that collects transportation cargo from the user's business partner or group company and delivers it to a pre-designated delivery destination, each of the inter-company transportation service, the outside transportation service, or the collection transportation service User management for storing association information in which user identification information of the user and a shipper code as a billing destination for transportation freight charges are associated in advance for each service Broadcast storage unit,
In response to a transport status search request including the collection date of transported cargo handled by the inter-company transport service, the external transport service, or the collection transport service, the user identification information stored in the user management information storage unit A search unit that searches and extracts a trace record of the transported cargo collected on the collection date from the trace database among all the transported cargo having the shipper code attached as a shipper;
Using the trace record extracted by the search unit as an input, the undelivered state of the transported cargo collected on the collection date is classified by the predetermined unit of the departure, by the predetermined unit of the landing, or by the predetermined of the departure A totaling unit that creates totaled information for each predetermined unit of departure / landing consisting of an arbitrary combination of a unit and the predetermined unit of landing;
The totaling unit counts the predetermined unit of the departure, the predetermined unit of the landing, or the predetermined unit of the departure / landing including any combination of the predetermined unit of the departure and the predetermined unit of the landing. Based on the aggregate information on the undelivered status of the transported cargo collected on the date of collection, the transport status collective management information in a preset format is edited. Edit the predetermined unit of the ground, the predetermined unit of the landing, or the predetermined unit of the landing and the landing, which is an arbitrary combination of the predetermined unit of the landing and the predetermined unit of the landing, into a preset alert display format The place of departure / landing, which is edited in the transportation status collective management information, and includes a predetermined unit of the departure, a predetermined unit of the landing, or an arbitrary combination of the predetermined unit of the departure and the predetermined unit of the landing A trace record of the transport cargo collected on the date of collection with the unit as the origin or the landing is a predetermined unit of the origin, the predetermined unit of the landing, or any of the predetermined unit of the origin and the predetermined unit of the landing An editorial department that links to a predetermined unit of departure / landing consisting of a combination,
Program to function as. The program is
Server,
Information on the originating group obtained by grouping the origin of the transport cargo in the inter-company transport service, the external transport service, or the collection transport service according to the conditions set in advance in each service; A group information storage unit for storing information on landing groups obtained by grouping landings of transport cargo in an external transportation service or a collection transportation service according to conditions set in advance in each service;
Function as
The counting unit sets the departure group and the arrival group set based on the information about the departure group and the information about the arrival group stored in the group information storage unit as the predetermined unit of departure and the predetermined unit of landing, respectively. 10. The program according to claim 9, wherein

Images