JP2004067308A - Self-propelled cargo damage management system, its management program and its management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide system to analyze the cause of damage of a self-propelled cargo in an early stage and easily understandable form. <P>SOLUTION: The system has a damage management server 1 which performs the management of the information regarding the self-propelled cargo, and the analysis and the notice of the damage tendency of the self-propelled cargo, and a damage management database 2 storing the damage information and the transportation information of the self-propelled cargo. The damage management database 2 consists of the basic information database storing the basic information consisting of the maker information, the outlet store information, and the number information regarding the self-propelled cargo, the damage information database storing the information regarding the damage places and the kind of damage of the self-propelled cargo, and the transportation information database storing the information regarding transportation contractor, transportation place or the transportation route of the self-propelled cargo. The damage management server 1 has an analysis means analyzing the damage information by the drill down system, and a notice means notifying the analyzed information or the damage information to the handling person of the self-propelled cargo through the network. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a self-propelled cargo damage management system, a self-propelled cargo damage management program, and a self-propelled cargo damage management method, and more particularly, to a system for performing statistics and analysis of damage in a logistics process of a self-propelled cargo.
[0002]
[Prior art]
2. Description of the Related Art Conventionally, self-propelled cargo such as a commercial vehicle for sale, a ship, or an airplane, for example, drives the cargo itself, mounts it on a large vehicle, transports it to a port or airport, and transports it to a foreign country by ship or aircraft. Then, after arriving at a foreign port or airport, the cargo itself is driven again or mounted on a large vehicle and delivered to a vehicle dealer such as a dealer.
As described above, self-propelled cargo has a feature that it is sold through a complicated route before being manufactured by a manufacturer and sold at a dealer such as a dealer.
[0003]
[Problems to be solved by the invention]
However, such self-propelled cargo is more likely to be damaged from various sources in the logistics process than any other cargo transported in a packaged state. Unless the cause and countermeasures are taken at an early stage, similar damages occur one after another.
[0004]
Self-propelled cargo, such as vehicles, is usually transported without packing, using the functions of the cargo (ie, traveling, parking, berthing, parking, opening and closing doors when boarding, etc.). At the same time as the frequency increases, the causes and types of damage become diverse. In addition, as described above, since the cargo is often transported through various distribution routes both in Japan and overseas, it is difficult to immediately identify the cause. In order to find the cause of such damage, it was necessary to investigate the distribution network all over the world and collect information manually, one by one, and the workload was heavy.
[0005]
On the other hand, the cause of damage in the logistics process differs depending on each company and the logistics method, and the most common damage cause for a specific company in charge of logistics may hardly occur in other companies. In addition, it is unlikely that it is necessary to investigate the global distribution network, collect information and take countermeasures for sudden or rare damage.
[0006]
In the past, it was necessary to individually investigate and analyze which logistics route, what cause, and at what rate the cargo was damaged. Therefore, it is difficult to grasp the cause of the damage and the correct measures for each company at an early stage by simply providing information items indicating the conventional numbers and parts and simply processing the information with a computer or the like.
[0007]
In addition, in the case of cargo that is transported domestically and internationally through various logistics routes, we will immediately contact self-propelled cargo handlers such as transportation companies, dealers, repair companies or manufacturers around the world for damages. Information must be exchanged to determine the cause and take countermeasures. Therefore, it is necessary to use mutually operable analysis tools to perform analysis in an environment that is mutually understandable and easy to understand.
[0008]
The present invention has been made in view of the above circumstances, and provides a system that analyzes the cause of damage to a self-propelled cargo in an early and easy-to-understand format and appropriately notifies a handler of the self-propelled cargo. The purpose is to:
[0009]
[Means for Solving the Problems]
In order to achieve the above object, a self-propelled cargo damage management system according to a first aspect of the present invention is an information management system for managing damage to a self-propelled cargo, which manages information related to the self-propelled cargo, It has a damage management server that analyzes and notifies the damage tendency of mobile cargo, and a damage management database that stores damage information and transport information of self-propelled cargo. A basic information database that stores basic information consisting of dealer information and number information, a damage information database that stores information on the location and type of damage of self-propelled cargo, a carrier and destination of self-propelled cargo Alternatively, the damage management server includes a transportation information database that stores information on transportation routes, and the damage management server analyzes information on damages by a drill-down method. And analysis means, a notifying means for notifying the self-propelled cargo handlers via the network the analysis information or information damage, and further comprising.
[0010]
Further, the analysis means starts with an analysis in which a predetermined period or the handler is an attribute, sequentially advances the analysis to a lower stage, and the analysis of the lower stage is performed within the range of the attribute of the analysis in the upper stage. You may do so.
[0011]
Further, the analysis means selects a display portion corresponding to a specific attribute in the screen used in the analysis of the upper stage, thereby performing the analysis at the next lower stage within the range of the attribute. May be displayed.
[0012]
Further, the notifying means of the damage management server may determine whether or not to notify according to information about damage set in advance.
[0013]
Further, the notifying means of the damage management server may determine whether or not to notify the handler according to the information on the damage set for each handler.
[0014]
Further, the notifying means of the damage management server may notify the cause of the damage in addition to the information stored in any of the basic information database, the damage information database, or the transport information database.
[0015]
Further, the cause of the damage may be specified by a combination of information on any one of the transportation section, the operator, and the vehicle type, information on the damaged part, and information on the type of damage.
[0016]
Further, the notifying means of the damage management server may notify a damage prevention measure corresponding to the cause of the damage together with the cause of the damage.
[0017]
The damage management database may store an analysis history of the damage tendency analyzed by the analysis means, and the notification means of the damage management server may notify the analysis history information of the damage tendency analyzed by the analysis means. Good.
[0018]
In addition, the damage management server may further include a report file creating unit capable of browsing the analysis result of the drill-down method.
[0019]
A self-propelled cargo damage management program according to a second aspect of the present invention is a program for causing a computer to function as a self-propelled cargo damage management system. Storage means for information on the type of damage to the self-propelled cargo, the degree of damage to the self-propelled cargo, the carrier, destination or route of the self-propelled cargo, the manufacturer of the self-propelled cargo, the dealer and the number of the self-propelled cargo; Analysis is performed based on the information, the analysis result is attached as a report file by drilldown method, analysis means that can analyze the information, recommendation to recommend the cause of damage to the analysis result and preventive measures means,
It is characterized by functioning as
[0020]
A self-propelled cargo damage management method according to a third aspect of the present invention is an information management method for managing damage to a self-propelled cargo, wherein the cause of damage is analyzed based on damage information and transport information of the self-propelled cargo. The analysis result is created as a drill-down electronic file based on the damage information and the transportation information, and the electronic file also stores the cause of damage to the self-propelled cargo and the preventive measures. The present invention is characterized in that it provides a method for analyzing the damage of a self-propelled cargo of a drill-down type by providing it to a handler of the self-propelled cargo and manages the damage of the self-propelled cargo.
[0021]
In addition, the damage information may include information on a damage location and a type of damage of the self-propelled cargo, and the transport information may include information on a carrier, a destination, or a transport route of the self-propelled cargo. .
[0022]
Further, the damage information may include repair information, and the repair information may be information relating to a repair cost of the self-propelled cargo.
[0023]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 1 is a diagram showing a configuration of a self-propelled cargo damage management system according to a first embodiment of the present invention. As shown in this figure, the self-propelled cargo damage management system includes a damage management server 1, a damage management database 2, a network 3, a dealer (dealer) 4, a repair shop 5, a production factory (manufacturer) 6, and a transporter 7. It is composed of
[0024]
The damage management server 1 is a server that manages and integrates the self-propelled cargo damage management system according to the present embodiment, and is installed, for example, at the headquarters of an insurance company. The damage management server 1 is connected to a plurality of distribution routes (self-propelled cargo handlers, etc.) via the network 3 and exchanges information with each of the related parties to thereby damage the self-propelled cargo. It implements a management system.
[0025]
The damage management database 2 includes a plurality of databases for realizing a damage management system for a self-propelled cargo, and includes, for example, a damage information database, a damage specification database, a repair information database, a transportation information database, and the like. . In the present embodiment, although not particularly limited, the damage management database 2 is configured as a database group including a lower database. The network 3 is assumed to be the Internet, but may be, for example, a LAN (Local Area Network).
[0026]
The dealer (dealer) 4 sells self-propelled cargo managed by the present embodiment to customers. The repair shop 5 is a factory that repairs self-propelled cargo. The production factory (maker) 6 is a factory that produces self-propelled cargo.
[0027]
The transport company 7 is a transport company that transports self-propelled cargo from a production factory (maker) 6 to a dealer (dealer) 4. The transporter 7 is composed of a plurality of transporters when importing and exporting between domestic and foreign countries. For example, in the case of self-propelled cargo such as vehicles, transport companies that drive the cargo itself or transport it to large ports and transport them to ports and airports, transport companies that ship overseas by ship or aircraft, and foreign ports and airports After arriving, there are transport companies that drive the self-propelled cargo itself or mount it on a large vehicle and transport it to the dealer 4. Further, a part of these transportations may be performed by the production factory 6 (manufacturer) or the dealer 4 (dealer).
[0028]
FIG. 2 is a diagram showing the configuration of the damage management server 1 of FIG. The damage management server 1 has a plurality of functions. In this embodiment, the damage information management function unit F101, the damage information notification function unit F102, the damage tendency analysis function unit F103, the report file creation function unit F104, and the operator management function unit F105, an information transmission / reception function unit F106, and a database management function unit F107.
[0029]
The damage information management function unit F101 manages information on damage to the self-propelled cargo.
More specifically, information is collected and processed so that damage information received by the self-propelled cargo can be individually analyzed through a database. The damage information notification function unit F102 notifies information on damage to the self-propelled cargo. Specifically, when certain conditions are satisfied, for example, when the damage frequency exceeds a preset damage frequency, the damage information is notified to a dealer (dealer) 4 or the like. The numerical values related to the damage include, for example, the percentage of damage occurrence frequency (5%, etc.) and the amount of damage (repair cost). Detect as a value. Further, an abnormal value detected during the analysis may be further analyzed, processed, and notified.
[0030]
The damage tendency analysis function unit F103 analyzes the tendency of damage to the self-propelled cargo. Specifically, drilldown analysis data for analysis is created based on the information collected and processed by the damage information management function unit F101. The cause of damage in the logistics process varies depending on the individual handler and the logistics method, and the most common damage reason for a specific handler may hardly occur in other companies.
[0031]
As analysis means used in such a case, the drilldown analysis data is analyzed by data having each attribute such as a predetermined period and a handler, and then another attribute is added within the range of the data. And it refers to data that is further specialized (drilled down) for further investigation and analysis.
[0032]
The analysis of the drill-down method refers to an analysis method in which the information collection screens arranged in a multilayer using such drill-down analysis data are narrowed down from top to bottom one after another. As a result, it is possible to clearly analyze which combination of attributes causes the most damage, and to search for the cause in an early and easy-to-understand format.
[0033]
In the drill-down analysis, the data used in the analysis at each stage is sequentially narrowed down, and the attribute causing the damage can be specified. The image of the data narrowing used in the drill-down analysis is as follows. First, the data in the first drill-down analysis has a larger range than the data in the second drill-down analysis, and the data in the next second drill-down analysis is The range of the data of the third drill-down analysis is larger than that of the data of the fourth drill-down analysis.
[0034]
This relationship indicates that the data in the Nth drilldown analysis has a larger range than the data in the (N + 1) th drilldown analysis. In other words, in the analysis at each stage, for example, an attribute having a high damage frequency (for example, manufacturer AAA) is confirmed, and another attribute having a high damage frequency (for example, a damaged portion is a rear bumper) is further confirmed as another attribute. The analysis proceeds in the form of
[0035]
For example, an example will be described in which damage analysis is performed with respect to monthly maritime transport of self-propelled cargo to the United States in the past two years. First, the damage tendency analysis function unit F103 reads out a graph displaying the average value of damages of US ports from a predetermined database based on the information collected and processed by the damage information management function unit F101. Then, when this graph is drilled down and narrowed down, a graph showing the transition of the damage occurrence rate for each port for two years is displayed.
[0036]
If the damage rate of self-propelled cargo at a port shows a peculiar trend in a particular month, further drilling down and narrowing down that month will result in damage to each ship arriving at that port in that month. Data representing the incidence is displayed. Then, when the ship is further drilled down and narrowed down, detailed data of the cargo related to the damage caused on the ship is displayed. In this way, by using the drill-down analysis method, after analyzing the damage tendency due to the combination of specific attributes, grasping a certain situation, we will proceed to individual investigation and analysis for each case It becomes possible.
[0037]
The report file creation function unit F104 creates a report file related to damage to the self-propelled cargo. More specifically, the report summarizes the causes of damage found by the above-described drill-down analysis and measures to prevent the damage. Then, this report is sent to a dealer (dealer) 4, a repair shop 5, a production factory (manufacturer) 6, a transporter 7, or the like as necessary.
[0038]
The handler management function unit F105 manages information about the handler of the self-propelled cargo.
More specifically, a production plant (manufacturer) 6 is in a position to manufacture and carry out the self-propelled cargo, and a carrier 7 is a carrier in which the self-propelled cargo is picked up and transported in Japan and overseas. The dealer, the dealer (dealer) 4 receives the self-propelled cargo and sells it to the customer, and the repairer 5 is taken out of the production plant (manufacturer) 6 to the customer via the dealer (dealer) 4. If the self-propelled cargo is damaged before it is sold, it is the operator responsible for repairing it.
[0039]
The handler management function unit F105 integrates and manages information on the handlers around the world (location, business contents, etc.) and information on the past damage status involving the handlers.
The information transmission / reception function unit F106 transmits / receives information relating to damage to the self-propelled cargo via a network. The database management function unit F107 manages information stored in the damage management database.
[0040]
FIG. 3 is a diagram showing a configuration of the damage management database 2 of FIG. The damage management database 2 is not particularly limited, but is a database group including a plurality of databases, and includes a damage information database 31, a damage detail database 32, a repair information database 33, a transportation information database 34, a basic information database 35, and a damage tendency analysis database 36. And a report file database 37. Each of the databases 31 to 37 is not particularly limited, but may be configured as a database group including a plurality of databases.
[0041]
The damage information database 31 is a database that stores damage information, repair information, and transport information of self-propelled cargo. The damage description database 32 is a database that stores information on the location, type, and degree of damage. The repair information database 33 is a database that stores information on parts used for repairing self-propelled cargo, repair shops, and repair costs. The transport information database 34 is a database that stores information on a carrier, a source, a destination, and a transport route of a self-propelled cargo.
[0042]
The basic information database 35 is a database for storing basic information including maker information, dealer information, and number information (for example, a vehicle number in the case of a vehicle) relating to a self-propelled cargo. The damage tendency analysis database 36 is a database that stores a history (analysis history) of causes of damage, preventive measures, and analysis results thereof. The report file database 37 is a database that stores report files created by the report file creation function unit F104.
[0043]
These databases are read and written by the above-mentioned database management function unit F107, and the information is transmitted to the store (dealer) 4, the repair shop 5, the production factory ( Maker 6 or carrier 7.
[0044]
FIG. 4 is a diagram showing a configuration of the damage statement database 32 of FIG. Although not particularly limited, the damage description database 32 is configured as a database group including a plurality of databases. The damage specification database 32 includes a damage location information database 41, a damage type information database 42, and a damage degree information database 43.
[0045]
The damaged part information database 41 stores information on the damaged part of the self-propelled cargo. Specifically, the damage location information database 41 stores, as damage locations, front right door (RFDOOR), front left door (LFDOOR), rear right door (RRDOOR), rear left door (LRDOOR), hood (HOOD), interior ( INTERIOR) or information such as tires (RIMS / TIRE).
[0046]
The damage type information database 42 stores information on the type of damage to the self-propelled cargo. Specifically, the damage type information database 42 stores information such as dents (DENTS), scratches (SCRATCHES), loss (MISSING), and air leaks (FLAT / PUNCTURED).
[0047]
The damage degree information database 43 stores information on the degree of damage to the self-propelled cargo. Specifically, the damage degree information database 43 stores information such as repairable, difficult to repair, or impossible to repair, and furthermore, the degree of damage is large, medium, or small.
[0048]
In addition to causing the database group to function as the above-described system, or all or a part of a program required to execute the above-described steps, a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc.) for distribution and distribution.
[0049]
FIG. 5 is a diagram showing the stored contents of the damage statement database 32 of FIG. The damage specification database 32 stores a great deal of information on damage location information, damage type information, damage degree information, and the like. In this database, for example, as shown in this figure, a record is created for each information number that is an identification number of a damage specification, and each record includes a vehicle type, a chassis number, damage location information, damage type information, and damage information. Information indicating degree information and the like is stored.
[0050]
The vehicle type is information on the type of self-propelled cargo. In the example shown in the figure, since there is a MOTER02 model, it is a 2002 model of a model called MOTER. The chassis number is a number stamped on the body of the self-propelled cargo. In the illustrated example, the chassis number is 325609.
[0051]
Damage location information is information on the location of damage to the self-propelled cargo. In the example of the figure, since it is LFDOOR, the left front door is shown. The damage type information is information on the type of damage. In the example of the figure, a scratch is shown because there is SCRAMCHES. The damage degree information is information on the degree of damage. In the example of FIG. When the detail button is pressed, individual detailed information data on other damage is displayed.
[0052]
FIG. 6 is a diagram showing a configuration of the repair information database 33 of FIG. Although not particularly limited, the repair information database 33 is configured as a database group including a plurality of databases. The repair information database 33 includes a repair part information database 61, a repair shop information database 62, and a repair cost information database 63.
[0053]
The repair parts information database 61 stores information on repair parts of self-propelled cargo. Specifically, the repair part information database 61 stores information on a door, a hood, a windshield, and the like. The repair shop information database 62 stores information on a repair shop for self-propelled cargo. Specifically, the repair shop information database 62 stores information such as contact information and location of the repair shop. The repair cost information database 63 stores information on repair costs of self-propelled cargo.
Specifically, the information database 63 stores information on how much the repair cost has been charged.
[0054]
Note that, in addition to causing the database group to function as the above-described system, or all or a part of a program necessary to execute the above-described steps, a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc.) for distribution and distribution.
[0055]
FIG. 7 is a diagram showing the stored contents of the repair information database 33 of FIG. The repair information database 33 stores a great deal of information on repair parts information, repair shop information, repair cost information, and the like. In this database, for example, as shown in the figure, a record is created for each information number that is an identification number of repair information, and each record includes a vehicle type, a chassis number, repair part information, a repair shop information, and a repair shop information. Information indicating cost information and the like is stored.
[0056]
The vehicle type is information on the type of self-propelled cargo. In the example shown in the figure, since there is a MOTER02 model, it is a 2002 model of a model called MOTER. The chassis number is a number stamped on the body of the self-propelled cargo. In the illustrated example, the chassis number is 325609. The repair parts information is information on repair parts for self-propelled cargo.
In the example of the figure, there is a hood. The repair shop information is information on a factory that performs repair. In the example shown in the figure, there is a repair shop ○.
[0057]
The repair cost information is information on repair costs. In the example of the figure, it is 20,000 yen. When the detail button is pressed, individual detailed information data relating to other repairs is displayed. The repair cost data recorded here is also recorded in the damage information database as damage information in the damage information database 31 as damage amount data.
[0058]
FIG. 8 is a diagram showing a configuration of the transport information database 34 of FIG. Although not particularly limited, the transport information database 34 is configured as a database group including a plurality of databases. The transport information database 34 includes a transporter information database 81, a source information database 82, a destination information database 83, and a transport route information database 84.
[0059]
The carrier information database 81 stores information on the carrier of the self-propelled cargo. The source information database 82 stores information on the source of the self-propelled cargo. The destination information database 83 stores information on the destination of the self-propelled cargo. The transport route information database 84 stores information on transport routes of self-propelled cargo.
[0060]
In addition to causing the database group to function as the above-described system, or all or a part of a program required to execute the above-described steps, a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc.) for distribution and distribution.
[0061]
FIG. 9 is a diagram showing the contents stored in the transport information database 34 of FIG. The transport information database 34 stores a great deal of information on transporter information, transport source information, transport destination information, transport route information, and the like. In this database, for example, as shown in the figure, a record is created for each information number which is an identification number of transport information, and each record includes a vehicle type, a chassis number, a transporter information, a transport source information, a transport Information indicating destination information and transport route information is stored.
[0062]
The vehicle type is information on the type of self-propelled cargo. In the example shown in the figure, since there is a MOTER02 model, it is a 2002 model of a model called MOTER. The chassis number is a number stamped on the body of the self-propelled cargo. In the illustrated example, the chassis number is 325609. The carrier information is the name of the carrier that transported the self-propelled cargo. In the example in the figure, it is Kimura Transportation. The source information is the source of the self-propelled cargo.
[0063]
In the example of the figure, there is Tokyo. The destination information is the destination of the self-propelled cargo. In the example of the figure, it is Detroit. The transportation route information is a method or a route for transporting the self-propelled cargo. In the example of the figure, there is "sea transportation". When the detail button is pressed, individual detailed information data relating to other transportation is displayed.
[0064]
FIG. 10 is a diagram showing a configuration of the damage tendency analysis database 36 of FIG. Although not particularly limited, the damage tendency analysis database 36 is configured as a database group including a plurality of databases. The damage tendency analysis database 36 includes a damage cause information database 101, a damage prevention measure information database 102, and an analysis history information database 103.
[0065]
The damage cause information database 101 stores information on the cause of damage to the self-propelled cargo. Specifically, the damage cause information database 101 stores information that has caused damage such as damage due to fixing ropes and damage due to collision between cargoes. The damage prevention information database 102 stores information on damage prevention measures for self-propelled cargo. Specifically, the damage prevention measure information database 102 stores information such as not using a fixing rope or widening the interval between cargoes. The analysis history information database 103 stores information on the analysis history (analysis history) that has led to the analysis result.
[0066]
In addition to causing the database group to function as the above-described system, or all or a part of a program required to execute the above-described steps, a recording medium (ROM, flexible disk, hard disk, CD-ROM, MO, CD-R, flash memory, etc.) for distribution and distribution.
[0067]
FIG. 11 is a diagram showing the contents stored in the damage tendency analysis database 36 of FIG. The damage tendency analysis database 36 stores a great deal of information on damage cause information, damage prevention measure information, analysis history information, and the like. In this database, for example, as shown in this figure, a record is created for each information number which is an identification number of damage tendency analysis information, and each record includes a vehicle type, a chassis number, damage cause information, damage prevention measures. Information indicating information and analysis history information is stored.
[0068]
The vehicle type is information on the type of self-propelled cargo. In the example shown in the figure, since there is a MOTER02 model, it is a 2002 model of a model called MOTER. The chassis number is a number stamped on the body of the self-propelled cargo. In the illustrated example, the chassis number is 325609. The damage cause information is information on the cause of damage to the self-propelled cargo. In the example of the figure, there is a collision between cargoes. Damage prevention measure information is information on damage prevention measures for self-propelled cargo. In the example of the figure, the interval between cargoes is to be increased.
[0069]
The analysis history information is information on the history (analysis history) that has led to the analysis result. In the example of the figure, there is a drill-down A. The drilldown A is the information number of the history information using the drilldown analysis method. According to this information number, it is possible to refer to the history information using the drill-down analysis method. When the detail button is pressed, individual detailed information data on other damage tendencies is displayed.
[0070]
FIG. 12 is a diagram showing a login procedure of the self-propelled cargo damage management system according to the first embodiment of the present invention. The log-in procedure of the self-propelled cargo damage management system includes an address input screen 120, a security warning screen 121, a client authentication screen 122, a log-in screen 123, and a menu screen 124.
[0071]
The address input screen 120 is provided for accessing the self-propelled cargo damage management system. When an address is input on the address input screen 120, the screen shifts to the next security warning screen 121. The address input screen 120 may be created in the form of a homepage on the Internet, or may be operated on software distributed in advance.
[0072]
As the software distributed in advance, an information medium storing the software storing the drill-down analysis method is provided as a single unit, and the damage management database 2 is accessed via the network 3. You may use it. Further, predetermined information among information stored in the damage management database 2 may be provided in the form of a package attached to software storing the drill-down analysis method.
[0073]
In addition, the damage management server 1 has established a homepage that discloses information on the self-propelled cargo, and the software may be downloaded from the homepage. Furthermore, information may be analyzed and notified by downloading the information.
[0074]
The security warning screen 121 is a screen for issuing a warning regarding the security of the self-propelled cargo damage management system before proceeding to the next client authentication screen 122 or login screen 123. The client authentication screen 122 is a screen that allows the operator to select a certificate used when accessing the self-propelled cargo damage management system. The login screen 123 is a screen displayed when an operator logs in to the self-propelled cargo damage management system. The menu screen 124 is a menu screen for selecting a function of the self-propelled cargo damage management system.
[0075]
FIG. 13 is a diagram showing the client authentication screen 122 of FIG. The client authentication screen 122 is a screen that allows the operator to select a certificate used when accessing the self-propelled cargo damage management system. A plurality of certificates are prepared and can be selected according to the authentication level of the worker. The certificate is an electronic encryption key or the like for authenticating a terminal used for access. For example, a VeriSign electronic encryption key is an example. The type is not limited to this, and various types can be selected.
[0076]
FIG. 14 is a diagram showing the login screen of FIG. A person who intends to use the self-propelled cargo damage management system inputs a user name, a password, and the like in the user password input box 140, and presses a connection button to log in. If there is an error in the input item, an error screen is displayed and re-input is requested.
[0077]
FIG. 15 is a diagram showing the menu screen of FIG. Upon logging into the self-propelled cargo damage management system, a menu screen 124 is first displayed. Then, the operator selects an analysis lower-level screen from the selection items 150 according to a predetermined purpose. For example, the selection item 150 contains the name of the country of manufacture. The operator selects a certain country (GERMANY) from the selection items 150.
[0078]
Then, a drill-down screen 151 is displayed, and a plurality of selection items 152 are further displayed. The selection items 152 include “Monthly / Factory Total (monthly list of all manufacturers total)”, “Monthly / FactoryIndividual (monthly list of individual manufacturers, that is, manufacturers AAA and the like)”, “MAT / Factory Total” (total of all manufacturers total). Items such as a 12-month moving average list) are displayed.
[0079]
Here, for example, by selecting “Monthly / Factory Total”, a view mark 155 is displayed in the upper right column. When the view mark 155 is clicked, the screen shown in FIG. 16 is displayed.
[0080]
FIG. 16A is a diagram illustrating an example of such a drilled-down detailed information screen. The detail screen of FIG. 16A is displayed based on the attribute selected in FIG. 15, for example, a monthly list of the average damage occurrence frequency of the entire maker. Further, when the operator of the present system selects a predetermined part of the graph in the figure, a drill-down display is further performed, and it is possible to narrow down to detailed individual information.
[0081]
For example, by clicking any part of the screen of FIG. 16A, the screen of FIG. 16B is displayed. That is, a monthly graph of the damage occurrence frequency for each manufacturer can be obtained from the monthly graph of the average damage occurrence frequency for all manufacturers.
[0082]
The place to be clicked on the screen of FIG. 16A can be set arbitrarily.
For example, the selection item 161 may be displayed as a selection item new like the selection item 161, or the “All Sources Together” display portion of the selection item 163, the graph screen 165, and the graph line 167 may be selected. (B) may be displayed.
[0083]
FIG. 17 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the first embodiment of the present invention. The analysis procedure of the self-propelled cargo damage management system according to the present embodiment includes a preview screen 170, a first drill-down screen 171, a second drill-down screen 172, a third drill-down screen 173, a fourth drill-down screen 174, and a fifth drill-down screen. It comprises a drill-down screen 175 and a sixth drill-down screen 176.
[0084]
The self-propelled cargo damage management system processes information in various formats, such as information displayed in a list, information displayed in a pie chart, and information displayed in a line graph, and performs drill-down analysis. It can be carried out.
[0085]
The preview screen 170 is a screen that displays a list of repair details of self-propelled cargo for a predetermined period in the past. The first to sixth drilldown screens 171 to 176 are screens displayed by performing a drilldown analysis from the preview screen 170, respectively. In the drill-down analysis method, the screen displayed at each stage of the drill-down is different, and individual investigation and analysis can be performed.
[0086]
FIG. 18 is a diagram showing the preview screen 170 of FIG. In the present embodiment, the preview screen 170 displays all record information for a predetermined period. Although not particularly limited, on the preview screen 170, in addition to the period, the manufacturer, the country of production, and the final destination, the type of vehicle, the chassis number, the damaged portion and the type of damage of the self-propelled cargo, and the like can be viewed. Various items can be selected as necessary for the items displayed on the preview screen 170.
[0087]
FIG. 19 is a diagram showing the first drill-down screen 171 and the sixth drill-down screen 176 of FIG. First, when a selection item 190 on the preview screen 170 is selected, data for that period is displayed. In the example of the figure, the worker has selected the information of February 2002.
[0088]
Then, a first drill-down screen 171 as information on the self-propelled cargo damaged in February 2002 is displayed. Information regarding self-propelled cargo damaged during other periods can be displayed by selecting a period in selection item 191.
Then, when information is narrowed down one by one by the drill-down method, a sixth drill-down screen 176 which is a final information screen is reached.
[0089]
The sixth drilldown screen is data for February 2002 (first drilldown screen), the manufacturer is AAA data (second drilldown screen), and the manufacturing country is TAP = Taiwan data (third drilldown screen) The final destination is derived from the data of France (fourth drilldown screen) and the model is derived via the data of the BBB vehicle (fifth drilldown screen). The data narrowed down by a plurality of attributes up to and including February 1, 2002 is further narrowed down (sixth drill-down screen) and displayed.
[0090]
In other words, on the preview screen, the number of damage occurrences for each month is confirmed, and the data of February in which the number of damage occurrences (or damage amount, the same applies hereinafter) is large is selected by selecting 190 (first drill). Down screen 171). In addition, the data for each manufacturer is called out from the data for February, and it is confirmed that the number of occurrences of damage to the self-propelled cargo of the manufacturer AAA is large (second drilldown screen 172). .
[0091]
The screen of the manufacturer AAA is displayed by selecting 192.
Similarly, the selection items for selecting the drill-down screen at each stage are displayed by double-clicking the selection items of the upper screen, and by selecting any of the newly displayed lower selection items, The corresponding drilldown screen is displayed.
[0092]
Furthermore, data is confirmed for the manufacturer AAA by production country, and it is confirmed that self-propelled cargo manufactured in Taiwan has a large number of damages (third drilldown screen 173). In addition, when the situation of the final destination for the products manufactured in Taiwan is checked, it can be seen that the number of damages generated to France was large (fourth drilldown screen 174).
[0093]
From the self-propelled cargo for France, the number of cases is confirmed by model (cargo model, for example, vehicle type if a vehicle) by the fifth drill-down screen. Then, it is confirmed on the fifth drill-down screen (175) that the number of cases for the model MORTER02 year was large. In addition, in order to confirm on which day of February 2002, when the number of damage occurrences was large, the number of accidents was large, data for each day is displayed on the sixth drill-down screen (176). Then, it is confirmed that the number of damage occurrences was large on February 1.
[0094]
Here, it is assumed that the details of the accident are individually confirmed on the sixth drill-down screen 176, and for example, it is assumed that the “dent” having the “bumper” as a damaged portion is frequently damaged.
Also, as separate information, let's say that it was confirmed that a ship that was transporting off Taiwan on the day encountered stormy weather. In other words, the reason why much damage was caused to the cargo of the model MORTER02 model manufactured at the Taiwan factory of the manufacturer AAA in February 2002 is that the ship was transported from the port of Taiwan on February 1 for the model MORTER02 model. It is presumed that, for example, the transporter who was in charge of was not properly stopping the vehicle's wheel.
[0095]
In this case, it is presumed that the vehicles collided between front and rear due to shaking due to stormy weather, and that many accidents occurred. In order to prevent an accident due to such a cause, a warning that the vehicle should be stopped accurately is sent to the shipping company or a shipping company that is expected to transport a route that is affected by stormy weather.
[0096]
In this way, the operator can analyze the cause of the damage and the countermeasure based on the information on the sixth drill-down screen 176. In addition, the damage management system stores the processes from the first drilldown screen 171 to the fifth drilldown screen 175 until the worker reaches the sixth drilldown screen 176 as a damage tendency analysis history, The other party receiving the analysis result can also be notified as information serving as a basis for the analysis result.
[0097]
When performing the analysis, if the cause of the accident can be identified without reaching the sixth drill-down screen, the drill-down may be terminated halfway. Further, the order of the drill-down shown here is an example, and the order can be set by an arbitrary permutation combination. Further, during the drill-down, there are a plurality of directions to lower stages, and it is possible to analyze a plurality of routes. For example, the number of attributes such as damage frequency is not always limited to one. In such a case, it is necessary to analyze the attributes whose damage frequency is high and to drill down.
[0098]
FIG. 20 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the second embodiment of the present invention. The analysis procedure of the self-propelled cargo damage management system according to the present embodiment includes a pie chart drill-down screen 200, a pie chart drill-down screen 201, a pie chart drill-down screen 202, and a detailed data display screen 203.
[0099]
The pie chart drill-down screen 200 to the detailed data display screen 203 are used when analyzing the contents of each damaged portion during a predetermined period. The pie chart drill-down screen is not particularly limited. In the present embodiment, the pie chart is a screen 200 to a screen 202. The detailed data display screen 203 is a detailed list of self-propelled cargo narrowed down by the drill-down analysis. ing.
[0100]
FIG. 21 is a diagram showing the drilldown analysis screens 200 and 201 of FIG. The drill-down analysis screen 200 is a pie chart of the damage site analysis in 2002. By selecting the selection item 210, selection items of different years are displayed, and the selection item 211 is selected from the displayed items. Thus, the information of February 2002 can be displayed.
[0101]
When there are a plurality of pages of information, information of different pages can be displayed by the page move box 212 or 213. Then, the drilldown analysis screen 201 is displayed by selecting the selection item 211 in the damage site analysis pie chart of February 2002.
[0102]
FIG. 22 is a diagram showing the drill-down analysis screen 202 and the detailed data display screen 203 of FIG. The drill-down analysis screen 202 is an analysis pie chart for each damage type in the rear bumper (REAR BUMPER) in which the ratio of the number of damages is high in the drill-down screen 201. That is, it is displayed next to the drilldown analysis screen 201. Then, when the selection item 220 is selected, a detailed data display screen 203 is displayed.
[0103]
The detailed data display screen 203 is the detailed information of the self-propelled cargo in which the rear bumper was damaged in scratches (SCRACHECHES) in February 2002. From this detailed information, the worker searches for common items and analyzes the causes of damage and countermeasures. In this way, it is possible to find out the cause of the contents of the detailed data for each attribute displayed in the pie chart while viewing the detailed list of the attributes with a large number of damages as the data for displaying the list. .
[0104]
By selecting a damage type in the selection item 221, information on other damage types can also be displayed. In addition, by providing stages for the selection items, it is possible to analyze the damage by displaying the lower selection items step by step from the higher selection item and displaying the graph while selecting the selection item at each stage. it can.
[0105]
FIG. 23 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the third embodiment of the present invention. The analysis procedure of the self-propelled cargo damage management system according to the present embodiment includes a list drill-down screen 230, a list drill-down screen 231 and a list drill-down screen 232.
[0106]
When the list drill-down screen 230 displays, for example, a ranking of damage amounts (or repair cost billing amounts) in each country regarding EU dealers (dealers) that sell self-propelled cargo of a certain manufacturer XXX. Used for The list drill-down screen 231 is, for example, a ranking in descending order of the amount charged for repair costs by dealer in 2002 in a certain country. The list drilldown screen 232 is, for example, a list of billing amounts such as a monthly repair cost of a dealer in the list drilldown screen 231. On the list drill-down screen 232 displaying the detailed data, for example, a list of billing amounts such as repair costs of a certain dealer is described.
[0107]
FIG. 24 is a diagram showing the drill-down analysis screen 230 of FIG. The drilldown analysis screen 230 displays the ranking of the dealers handling the manufacturer XXX in each country in the EU in 2002. Then, by selecting the selection item 240, information of different periods can be displayed as selection items. When there are a plurality of pages of information, information of different pages can be displayed by the page move boxes 241 or 242. Then, by selecting the selection item 243, information for each dealer in Germany can be displayed.
[0108]
FIG. 25 is a diagram showing the drilldown analysis screen 231 of FIG. The drilldown analysis screen 231 is, for example, a screen that narrows down information to a certain dealer in Germany. Then, when the selection item 250 is selected, information on the detailed data of the self-propelled cargo handled by the dealer (PPP) is displayed.
[0109]
FIG. 26 is a diagram showing the detailed data display screen 232 of FIG. The detailed data display screen 232 displays individual damage information of a self-propelled cargo handled by a German dealer (PPP). The operator can analyze the cause of the damage and the countermeasure based on the common items and characteristic points from this information.
[0110]
FIG. 27 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the fourth embodiment. The analysis procedure of the self-propelled cargo damage management system according to the present embodiment is such that, by clicking (selecting) a part related to a certain attribute in the data or graph shown in the upper screen, the analysis is performed within the range of the attribute. By displaying more detailed lower-order data, graphs, and the like. By doing so, it is possible to further dig into the content related to the relevant part of the screen that is likely to cause a problem or cause damage, and to investigate the cause efficiently and visually .
[0111]
In order to realize such an analysis method, each display portion such as a graph on the screen includes, for example, link information indicating a file address of a lower graph screen. For example, as shown in FIG. 27A, first, the damage occurrence ratio for each manufacturer is displayed as a pie chart. Then, it turns out that the self-propelled cargo manufactured by the maker A has much damage. Then, when the graph display part for "Maker A" of the pie chart is clicked, FIG. 27B is displayed. In other words, the graph display portion (271) corresponding to "Manufacturer A" in FIG. 27A includes the file address information in FIG. 27B, and clicks on the corresponding portion in FIG. As a result, FIG. 27B is called up on the screen.
[0112]
Further, from FIG. 27B, it can be seen that there is much damage at the carrier AAA. Therefore, when the graph display portion (272) corresponding to the carrier "AAA" in FIG. 27B is clicked, FIG. 27C is similarly called up on the screen. The graph display portion corresponding to the carrier “AAA” in FIG. 27B includes the file address code of the screen in FIG. 27C.
[0113]
Similarly, by clicking on the graph display portion (273) corresponding to the damaged portion “RF Door (front right door)” in FIG. 27C, FIG. 27D is called up on the screen. By selecting the graph display portion (234) corresponding to "Scratches" in FIG. 27D, a list of individual data (not shown) is displayed. By confirming the data, the cause of the damage and the like can be confirmed in more detail.
[0114]
As described above, the attribute causing the damage can be visually narrowed down by drilling down the analysis by clicking on a problem part such as a graph. In this way, it is confirmed that the vehicle manufactured by the manufacturer A has a large number of scratches at the right front door by the transporter AAA.
[0115]
Here, due to a combination of various attributes such as a damaged portion and a type of damage, a person in charge of a carrier AAA responsible for transporting a self-propelled cargo manufactured by the manufacturer A has a right driver's seat for transporting a vehicle. When boarding the vehicle, it is speculated that this is because the door portion is in random contact with the door.
[0116]
The order of the attributes to be drilled down can be set arbitrarily, and the order is such that some cumulative patterns are created in advance so that rational analysis can be performed and recorded in the database management function unit F107. Then, when these patterns are analyzed, they are taken into the damage tendency analysis function unit F103.
[0117]
Next, a description will be given of a process for notifying each handler of the self-propelled cargo of information regarding damage and analyzed information. The database management function unit F107 of the damage management server 1 detects predetermined information from data recorded in the damage management database 2. For example, information that the monthly damage occurrence frequency of a certain manufacturer exceeds a certain rate (for example, 5%), or the damage occurrence frequency or damage rate of a certain operator during a predetermined period (for example, The information is obtained that the ratio of the cost required for damage repair to the price exceeds the average of all the operators by a predetermined value (for example, 2%).
[0118]
In that case, the management server 1 detects the information and transmits a warning display to a terminal (not shown) of the person in charge of the insurance company, for example, to urge the start of analysis. A predetermined numerical value serving as a key for issuing such a warning is stored in the damage management database 2 in advance. Such a numerical value can be changed according to a related operator or the like, and a different value can be set for each operator. FIG. 28 shows an example in which a numerical value or the like serving as a key for issuing a warning is set for each operator.
[0119]
As shown in FIG. 28, the condition that triggers the warning transmission can be set for each operator. When the condition set by each handler arrives, the damage management server sends a warning display to the terminal of the handler to prompt the analysis in order to prompt the analysis on the damage. Further, a warning display may be transmitted to a terminal of a person in charge of a company that coordinates this system such as an insurance company.
[0120]
As shown in FIG. 28, the trigger condition can be set based on various factors and conditions. For example, for the manufacturer A, a warning display is sent when the damage occurrence rate becomes 3% or more, or when a large damage with a repair cost of 500,000 yen or more occurs.
[0121]
The trigger condition may be set by one factor or condition, or may be set by a combination of a plurality of factors or conditions. For example, in FIG. 28, the trigger condition is set as a trigger for each damaged part by three factors or conditions of a damaged part, the number of cases, and a period. In other words, in the case of the manufacturer A, a warning is set to be displayed when a situation such that ten door damages occur in one year. The setting of such trigger conditions is determined by the actual conditions and policies of each operator.
[0122]
For example, in the case of manufacturer A, damage related to doors has frequently occurred in the past, and there has been a history of efforts to prevent such damage. In particular, these conditions have been set for the purpose of paying particular attention to door damage. Have been.
[0123]
The operator who receives the warning and the person in charge of the insurance company analyze the cause of the damage using the drill-down analysis. Since the analysis is performed based on the warning information, the drilldown proceeds in the range of the attribute specified by the information. For example, when information is obtained from a manufacturer that the frequency of occurrence of damage has exceeded a certain value, the person in charge checks the status of each month for the period during which the frequency of damage has increased (for example, the first half of 2001). We will proceed with the drilldown analysis in the direction.
[0124]
In addition, if information indicating that "the number of accidents on the door portion has already increased to 10 as of July 2002 in July 2002" is sent to the manufacturer A in FIG. The person in charge starts the drilldown analysis by checking the number of damages by carrier.
[0125]
In addition, the damage management server 1 confirmed from the damage data related to transportation in July 2002 that the damage occurrence frequency of all manufacturers was 2% higher than that of the previous month, and notified the insurance company staff. The insurance company personnel will do the analysis. As a result, it is assumed that a graph as shown in FIG.
[0126]
As described with reference to FIG. 27, it was confirmed that the cause of the frequent damage in July 2002 was mainly that the vehicle manufactured by the manufacturer A had a large number of scratches at the right front door by a carrier called AAA. . The information of the analysis result thus confirmed is recorded in the damage management database 2.
[0127]
Further, as described above, the person in charge of the drill-down analysis may perform the analysis while arbitrarily performing trial and error on various attributes. Further, a plurality of methods for performing the drill-down analysis (that is, the selection order of the attributes) may be stored in the damage management database 2 in advance, and the damage management server 1 may perform the analysis while sequentially adopting the analysis method.
[0128]
In the above description, an example in which the warning display is transmitted first when the trigger condition is satisfied has been described. However, at the time when the trigger condition is satisfied, the damage management server 1 determines based on the attribute relating to the trigger condition. A drill-down analysis can be performed and information about the results of the analysis and the cause of the damage can be sent to the operator.
[0129]
Next, the cause of the damage and the preventive measures are specified based on the analysis results. The cause and the preventive measure may be determined individually by the person in charge of the analysis, and may be created in consideration of the guess. On the other hand, for example, the cause may be automatically specified based on a combination of attributes such as a corresponding transport section, a handler, a vehicle type, a damaged portion, and a type of damage.
Then, preventive measures are associated with the cause.
[0130]
FIG. 29 shows a database structure relating to such combinations of various attributes and information on the cause of damage and measures to prevent damage. These pieces of information are recorded in the damage cause information database 101 and the damage prevention measure information database 102 of the damage tendency analysis database 36 provided in the damage management database 2.
[0131]
Each key code is assigned to each attribute and cause / prevention information. A combination of a key code relating to an attribute is associated with a key code relating to a cause of damage and a measure for preventing damage. Even with the same combination of attributes, there may be multiple causes and preventive measures. Therefore, a branch number (FIG. 29C) may be given to the damage cause code and the damage prevention measure code.
[0132]
The cause of the damage is specified by, for example, a combination of information such as a transportation section, a handling person, and a vehicle type, and a damage location and a damage type. The damage location and damage type are indispensable for specifying the cause, but the attributes added thereto can be arbitrarily selected or selected in combination.
[0133]
Damage prevention measures are recorded corresponding to the cause of damage. These are related by a key code. These key codes may be stored in the respective databases and held in a form that can be associated with each other, or may be stored in one of the databases without being stored in a separate database. Good.
[0134]
For example, in the case of FIG. 29 (a), since a lot of scratches are generated on the bottom of the vehicle during the handling by the shipper, it is determined that "when loading / unloading the ship, There are places where the steps are large. " As for the cause, a preventive measure of "confirming that there is no step between the ship and the pier between the port and the ship and removing the step" is extracted. Information regarding these causes and precautions is identified by the damage management server and transmitted to the relevant handler.
[0135]
In the case of FIG. 29 (b), it is confirmed that the right front door has a lot of scratches for a plurality of vehicle types. The cause is presumed, and for the cause, a preventive measure of "checking whether the ring or wristwatch of the cargo person is in contact or not handling the key violently" is extracted. In this case, even if the transporter is not necessarily specified from the information that there are a plurality of vehicle types, the cause is specified by combining the information of the damaged part and the content of the damage.
[0136]
As described above, the attribute information for specifying the cause differs depending on the mode of the damage. At that time, the damage location and the type of damage are important judgment factors, and by combining them with some other attribute information, the cause of the damage and the damage prevention measures associated therewith are specified.
[0137]
In the case of the fourth embodiment, when a person in charge of a transporter AAA, who handles a self-propelled cargo manufactured by a manufacturer A, gets on a Japanese vehicle in the right driver's seat to transport the vehicle, a door portion is used. It is presumed that the cause of FIG. Then, as a preventive measure, an item is specified in which it is checked whether a ring or a wristwatch of a cargo person is in contact with the key or whether handling of the key is violent.
[0138]
The damage management server 1 attaches the damage cause and the damage prevention measure thus obtained to the analysis history screen obtained by the drilldown analysis shown in FIG. 27, and transmits the screen to the corresponding carrier AAA. . At the same time, a copy is sent to the related manufacturer A or its dealer. Upon receiving the information, the carrier confirms the contents and takes countermeasures for prevention.
[0139]
In the cases of FIGS. 29 (c) and 29 (e), the cause of the damage is specified by the attributes of the transportation section, the vehicle type, the damaged part, and the type of the damage, and the cause damage preventive measures are associated therewith.
[0140]
In the case of FIG. 29D, the cause of the damage is specified by the attributes of the transport section, the damaged part, and the damage type, and the cause is associated with the damage prevention measure.
[0141]
In the case of FIG. 29 (f), the cause of the damage is specified by attributes such as the transportation section, the degree of damage, the damaged part, and the type of damage, and the cause is associated with a damage prevention measure. As described above, the cause of the damage is specified by a combination of the attributes such as the transportation section, the operator, and the vehicle type, in addition to the damage location and the damage type, and the damage prevention measure is associated with the cause.
[0142]
FIG. 30 is a diagram showing a relationship of stored information of the self-propelled cargo damage management system according to the fifth embodiment of the present invention. Information used in this embodiment is a view for explaining how advance what ties have been made. In this figure, the damage summary data is processing information in the case of land transportation. Items can be selected from this damage summary data as needed. Then, for example, the damage summary data is associated with the dealer master or damage specification data in a one-to-many item relation.
[0143]
For example, the file numbers of the damage summary data stored in the basic information database 35 are linked to the data stored in the damage specification database 32, the repair part information database 61, and the repair cost information database 63. The damage location, damage type, and damage degree are managed for each file number of the damage summary data.
[0144]
This information association is used when the above-described drill-down analysis method is used. In the process of narrowing down the information, linked information is read from the database as necessary and displayed as a drill-down screen. It will be. Damage summary data for other marine transportation etc. will be provided in the same manner.
[0145]
Note that the present invention is not limited to the above embodiment, and various modifications and applications are possible. The system configuration and the screen configuration can be appropriately changed. Further, if substantially the same function can be realized, the processing procedure and the like can be appropriately changed.
[0146]
For example, the damage management server 1 may be installed at the head office of the manufacturer instead of the insurance company headquarters. Devices such as terminals operated by employees belonging to each operator are connected to the damage management server via a network, and send and receive information to and from the damage management server through the terminals and operate the management server. Is also good.
[0147]
Also, a terminal operated by an employee of the insurance company may be connected, and the employee of the insurance company may transmit and receive information to and from the damage management server, or operate the management server.
[0148]
【The invention's effect】
As described above, according to the self-propelled cargo damage management system, the self-propelled cargo damage management program, and the self-propelled cargo damage management method of the present invention, the cause of the self-propelled cargo damage can be quickly and easily understood. The purpose is to provide a system for analysis in a format. Then, this analysis system can prevent damages that occur in physical distribution and contribute to reduction of physical distribution costs.
[Brief description of the drawings]
FIG. 1 is a diagram showing a configuration of a self-propelled cargo damage management system according to a first embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of a damage management server in FIG. 1;
FIG. 3 is a diagram showing a configuration of a damage management database of FIG. 1;
FIG. 4 is a diagram showing a configuration of a damage statement database of FIG. 3;
FIG. 5 is a diagram showing stored contents of a damage statement database of FIG. 4;
FIG. 6 is a diagram showing a configuration of a repair information database of FIG. 3;
FIG. 7 is a diagram showing stored contents of a repair information database of FIG. 6;
FIG. 8 is a diagram showing a configuration of a transportation information database of FIG. 3;
FIG. 9 is a diagram showing stored contents of a transportation information database of FIG. 8;
FIG. 10 is a diagram showing a configuration of a damage tendency analysis database of FIG. 3;
FIG. 11 is a diagram showing stored contents of a damage tendency analysis database of FIG. 10;
FIG. 12 is a diagram showing a login procedure of the self-propelled cargo damage management system according to the first embodiment of the present invention.
FIG. 13 is a diagram showing the client authentication screen of FIG.
FIG. 14 is a diagram showing the login screen of FIG.
FIG. 15 is a diagram showing the menu screen of FIG. 12;
FIG. 16 is a diagram showing an example of a drilled-down detailed information screen.
FIG. 17 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the first embodiment of the present invention.
FIG. 18 is a diagram showing a preview screen of FIG. 17;
FIG. 19 is a diagram showing a drilldown analysis screen of FIG. 17;
FIG. 20 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the second embodiment of the present invention.
FIG. 21 is a diagram showing a drilldown analysis screen of FIG. 20.
FIG. 22 is a diagram showing a drilldown analysis screen of FIG. 21.
FIG. 23 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the third embodiment of the present invention.
24 is a diagram showing a drilldown analysis screen of FIG. 23.
FIG. 25 is a diagram showing a drilldown analysis screen of FIG. 23.
FIG. 26 is a diagram showing the drilldown analysis screen of FIG. 23.
FIG. 27 is a diagram showing an analysis procedure of the self-propelled cargo damage management system according to the fourth embodiment of the present invention.
FIG. 28 is a diagram showing an example in which numerical values and the like serving as keys for issuing a warning are set for each handler.
FIG. 29 is a diagram showing a database structure related to a combination of various attributes and information on a cause of damage and a measure for preventing damage.
FIG. 30 is a diagram showing a relationship of information stored in a self-propelled cargo damage management system according to a fifth embodiment of the present invention.
[Explanation of symbols]
1 Damage management server
2 Damage management database
3 network
4 dealers
5 Repair shop
6 Production factory
7 Transporter
31 Damage management information database
32 Damage Details Database
33 Repair Information Database
34 Transportation Information Database
35 Basic Information Database
36 Damage Trend Analysis Database
37 Report File Database
41 Damage location information database
42 Damage type information database
43 Damage degree information database
61 Repair parts information database
62 Repair shop information database
63 Repair cost information database
81 Carrier Information Database
82 Transport Information Database
83 Transportation Information Database
84 Transportation Route Information Database
101 Damage cause information database
102 Damage prevention measure information database
103 Analysis history information database
120 Address input screen
121 Security Warning Screen
122 Client Authentication Screen
123 Login screen
124 Menu screen
140 User password input field
150 selection items
151 Drilldown screen
152 selection items
153 Drilldown screen
154 selection items
155 View mark
161 selection items
163 selection items
165 Graph screen
167 Graph line
161 selection items
170 Preview screen
171 First drill down screen
172 Second drilldown screen
173 Third Drilldown Screen
174 Fourth Drill Down Screen
175 Fifth drill down screen
176 6th drill down screen
180 page move box
181 Page Move Box
190 Selected items
191 selection items
192 choices
200 pie chart drill down screen
201 Pie chart drill down screen
202 Pie chart drill down screen
203 Detailed data display screen
210 Choice
211 selection items
212 Page Move Box
213 Page move box
220 selection items
221 selection item
230 List Drilldown Screen
231 List Drilldown Screen
232 List Drilldown Screen
240 choices
241 Page Move Box
242 Page move box

Claims (14)

In an information management system that manages damage to self-propelled cargo,
A damage management server that manages information on self-propelled cargo, analyzes and notifies the tendency of damage to self-propelled cargo,
A damage management database that stores damage information and transport information for self-propelled cargo,
The damage management database includes a basic information database for storing basic information including maker information, store information, and number information on a self-propelled cargo, and a damage for storing information on a damage location and a type of damage of the self-propelled cargo. It consists of an information database and a transport information database that stores information about the carrier, destination or route of the self-propelled cargo,
The damage management server further includes analysis means for analyzing information on damage by a drill-down method, and notification means for notifying the analyzed information or the information on damage to a handler of the self-propelled cargo via a network. A self-propelled cargo damage management system. The analysis means starts with an analysis in which the attribute is the predetermined period or the handler, sequentially advances the analysis to the lower stage, and performs the analysis of the lower stage within the range of the attribute of the analysis at the upper stage. The self-propelled cargo damage management system according to claim 1, wherein: The analysis means selects a display portion corresponding to a specific attribute in the screen used in the analysis of the upper stage, so that the screen on which the analysis at the next lower stage is performed within the range of the attribute is displayed. The self-propelled cargo damage management system according to claim 1 or 2, wherein the system is operated. The self-propelled cargo damage management according to any one of claims 1 to 3, wherein the notification means of the damage management server can determine whether or not to give a notification in accordance with information on damage set in advance. system. The notification means of the damage management server determines whether or not to notify the handler in accordance with information on the damage set for each of the handlers. Self-propelled cargo damage management system as described in section. The notification means of the damage management server notifies the cause of the damage in addition to the information stored in any one of the basic information database, the damage information database, and the transportation information database. The self-propelled cargo damage management system according to any one of claims 1 to 5. 7. The vehicle according to claim 6, wherein the cause of the damage is specified by a combination of information on any one of a transportation section, a handler, and a vehicle type, information on a damaged portion, and information on a type of damage. Mobile cargo damage management system. 8. The self-propelled cargo damage management system according to claim 7, wherein the notification unit of the damage management server notifies a damage prevention measure corresponding to the cause of the damage together with the cause of the damage. system. The damage management database stores an analysis history of the damage tendency analyzed by the analysis means, and the notification means of the damage management server notifies analysis history information of the damage tendency analyzed by the analysis means. The self-propelled cargo damage management system according to any one of claims 1 to 8. The self-propelled cargo according to any one of claims 1 to 9, wherein the damage management server further includes a report file creating unit capable of browsing the analysis result of the drill-down method. Damage management system. A program for functioning as a self-propelled cargo damage management system, comprising:
Self-propelled cargo damage location, type of self-propelled cargo damage, degree of self-propelled cargo damage, self-propelled cargo carrier, destination or route, self-propelled cargo manufacturer, dealer and Means for storing information about the number of the self-propelled cargo,
An analysis unit that performs analysis based on the information, and the analysis result is attached as a report file by a drill-down method, and the information analysis can be performed;
Recommended means to recommend the cause of damage and its prevention measures in the analysis results,
Self-propelled cargo damage management program to function as a service. In an information management method for managing damage to self-propelled cargo,
Based on damage information and transportation information of self-propelled cargo, analyze the cause of damage,
Create the analysis result as a drill-down electronic file based on the damage information and transport information,
The electronic file also stores the cause of damage to the self-propelled cargo and its preventive measures,
By providing the electronic file to a handler of a self-propelled cargo, an analysis method for damage of the self-propelled cargo of a drill-down type is provided, and the damage of the self-propelled cargo is managed. Driving type cargo damage management method. The said damage information consists of the information regarding the damage location and the kind of damage of self-propelled cargo, The said transport information consists of the information about the carrier, the destination, or the transportation route of self-propelled cargo. 13. The self-propelled cargo damage management method according to item 12. 14. The self-propelled cargo damage management method according to claim 12, wherein the damage information includes repair information, and the repair information includes information on a repair cost of the self-propelled cargo.

Images