JP2023159551A - Item management system, item management method, and item management program - Google Patents

Abstract

To provide an item management system, an item management method, and an item management program for promoting a user to register master data.SOLUTION: A management server 20 comprises: a master information storage unit 22 for recording master information regarding items; a user information storage unit 23 for recording information regarding individual items of a user; and a control unit 21 connected to a user terminal 10. When the control unit 21 acquires item information as to the individual items from the user terminal 10 and acquires a master registration request for the item information, the control unit records new master information in the master information storage unit 22, performs item registration in the user information storage unit 23 in association with the master information recorded in the master information storage unit 22, and records a master usage state in the master information used for the item registration.SELECTED DRAWING: Figure 1

Description

The present invention relates to an item management system, an item management method, and an item management program for managing items that constitute a user's assets.

2. Description of the Related Art Technologies that can centrally manage user assets on the Internet are being considered (see, for example, Patent Document 1). The asset management server described in this document registers products (items) purchased at an online shop server using a user terminal as assets in an asset database. The assets registered in the asset database are used for transactions.

Here, in order to efficiently register assets, it is convenient to have shared master data that allows items (products) to be used by other users in advance. Therefore, techniques for prompting the registration of master data are also being considered (see, for example, Patent Document 2). The technology described in this document promotes registration in a translation dictionary (master data) and use of the translation dictionary. Then, the amount to be paid to the user of the translation dictionary is calculated according to the number of times the translation dictionary is used.

JP2013-257727A Japanese Patent Application Publication No. 2005-250746

However, master data registered by users is diverse. For example, if there is little master data, the usability for other users will be poor. Furthermore, multiple pieces of master data may be registered for the same item. In this case, the frequency of use of master data may vary depending on the registered contents. If such master data cannot be managed accurately, it will be inconvenient for users.

An item management system that solves the above problems includes a master information storage unit that records master information regarding items, a user information storage unit that records information regarding individual items of users, and a control unit that is connected to a user terminal. Be prepared. When the control unit acquires item information about an individual item from the user terminal and acquires a master registration request for the item information, the control unit records new master information in the master information storage unit, and records the new master information in the master information storage unit. The item is registered in the user information storage unit in association with the master information recorded in the storage unit, and the master usage status is recorded in the master information used for the item registration.

The present invention can facilitate registration of master data.

FIG. 1 is an explanatory diagram of an item management system according to an embodiment. FIG. 2 is an explanatory diagram of the hardware configuration of the embodiment. FIG. 2 is an explanatory diagram of a storage unit of the embodiment, in which (a) is an explanatory diagram of a master information storage unit, and (b) is an explanatory diagram of a user information storage unit. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment. It is an explanatory diagram of a processing procedure of an embodiment.

An embodiment of an item management system, an item management method, and an item management program will be described according to FIGS. 1 to 11. In this embodiment, it is assumed that a service is provided in which users register their possessions and desired items (individual items of users) and mediate transactions regarding individual items.

As shown in FIG. 1, a user terminal 10, a management server 20, and a market site 30 are used, which are connected via a network.
(Hardware configuration example)
FIG. 2 shows an example of the hardware configuration of the information processing device H10 that functions as the user terminal 10, the management server 20, the market site 30, and the like.

The information processing device H10 includes a communication device H11, an input device H12, a display device H13, a storage device H14, and a processor H15. Note that this hardware configuration is just an example, and other hardware may be included.

The communication device H11 is an interface that establishes a communication path with other devices and executes data transmission and reception, and is, for example, a network interface card, a wireless interface, or the like.

The input device H12 is a device that receives input from a user or the like, and is, for example, a mouse, a keyboard, or the like. The display device H13 is a display, touch panel, or the like that displays various information.

The storage device H14 is a storage device that stores data and various programs for executing various functions of the user terminal 10, the management server 20, and the market site 30 (for example, the master information storage section 22 and the user information storage section 23, which will be described later). It is. Examples of the storage device H14 include ROM, RAM, hard disk, and the like.

The processor H15 controls each process in the user terminal 10, the management server 20, and the market site 30 (for example, the process in the control unit 21 described later) using programs and data stored in the storage device H14. Examples of the processor H15 include a CPU, an MPU, and the like. This processor H15 expands a program stored in a ROM or the like into a RAM and executes various processes corresponding to various processing. For example, when an application program of the user terminal 10, management server 20, or market site 30 is started, the processor H15 operates a process that executes each process described below.

The processor H15 is not limited to performing software processing for all processes that it executes. For example, the processor H15 may include a dedicated hardware circuit (for example, an application-specific integrated circuit: ASIC) that performs hardware processing for at least part of the processing that it executes. That is, the processor H15 may be configured as follows.

(1) one or more processors that operate according to a computer program (software); (2) one or more dedicated hardware circuits that execute at least some of the various processes; and (3) a circuit that includes a combination thereof. (circuitry)
A processor includes a CPU and memory, such as RAM and ROM, where the memory stores program codes or instructions configured to cause the CPU to perform processing. Memory or computer-readable media includes any available media that can be accessed by a general purpose or special purpose computer.

(Functions of each information processing device)
The user terminal 10 in FIG. 1 is a computer terminal used by a user who uses this service. An asset management application is installed on this user terminal 10. Using this asset management application, the user terminal 10 accesses the management server 20.

The management server 20 is a computer system for managing items (assets) owned by users. This management server 20 includes a control section 21, a master information storage section 22, and a user information storage section 23.

This control unit 21 performs processing (processing including a registration stage, an evaluation stage, an intermediary stage, etc.) to be described later. By executing the item management program for this purpose, the control unit 21 functions as a registration unit 211, an evaluation unit 212, an intermediary unit 213, and the like.

The registration unit 211 executes processing for registering items. The registration unit 211 holds an asset target table for identifying item types that specify items to be registered as assets. Using this asset target table, for example, items that are consumed in a short period of time (for example, consumables such as food) are excluded from asset targets.

The evaluation unit 212 executes processing to evaluate the user's assets. The evaluation unit 212 maintains a status adjustment table in which adjustment ratios for adjusting the estimated transaction amount are recorded in association with item statuses. Furthermore, the evaluation unit 212 holds a value calculation function for calculating the expected transaction price from the desired item price of the desired item management record 233 in which the same item is recorded. This value calculation function uses the statistical value (for example, average value) of the price of the desired item, the ownership status (the number of desired item management records 233), etc. as variables.

Furthermore, the evaluation unit 212 also calculates the asset value of the item master record 220. For this reason, the evaluation unit 212 holds a master evaluation function. This master evaluation function calculates a master evaluation amount using the usage status of the item master record 220 as a variable. Here, when the master usage status (master usage count) is equal to or greater than the reference value, a master evaluation amount is calculated according to the master usage status.

As the master usage status, for example, the number of individual item registrations of individual item IDs of possessions and desired items registered by each user using the master item ID of the item master record 220 can be used.

Furthermore, as the master usage status, for example, a business entity that makes recommendations to users who have registered their possessions or desired items can use the number of recommendations and recommendation unit price when using the master item ID. In this case, the number of recommendations of the individual item ID and the predetermined recommendation unit price are used for the possessions and desired items registered using the master item ID. This recommendation unit price is a unit price for determining the usage fee at the time of recommendation. Note that the recommendation unit price may be determined according to the number of recommendations.

The evaluation unit 212 also holds a benefit calculation function. A benefit to be given to give preferential treatment to a user (master user) who has registered the item master record 220 is calculated. This benefit calculation function can use a function that uses the master usage status as a variable. For example, the number of individual item registrations using the master item ID is set as a variable. Further, the master usage status using the master item ID is used as a variable. When using the master usage status, a predetermined percentage of a portion of the "usage fee at the time of recommendation" obtained from the business that makes the recommendation is returned to the master user as a coefficient. Benefits for the master user include points that can be used for transactions, gift certificates, and the like.
The intermediary unit 213 executes processing for proposing and intermediating transactions related to user assets.

As shown in FIG. 3A, an item master record 220 is recorded in the master information storage unit 22. This item master record 220 is recorded when master registration for an item is performed. The item master record 220 records data regarding the master item ID, registration date and time, master user ID, master usage status, item type, name, item description, initial price, shareability, and expected transaction price.

The master item ID data area records data regarding an identifier for identifying each item.
In the registration date and time data area, data regarding the year, month, day, and time when the item master record 220 was registered is recorded.

In the master user ID data area, data related to an identifier for identifying a user (master user) who has registered the master data of this item is recorded.
In the master usage status data area, data regarding the usage status of this master item ID is recorded. The individual item ID of the property management record 232 registered using the master item ID is used as the master usage status (individual registration information). Furthermore, when a business operator or the like recommends a transaction to a user who has registered an item using this master item ID, the master usage status (recommendation destination information) is also recorded. In this case, in addition to the number of recommendations and the recommendation unit price, the ID of the individual item targeted for recommendation and the user ID of the destination of the transaction proposal are recorded. Furthermore, the date and time when the master item ID was used is recorded.

The item type data area records data regarding an identifier for specifying the type to which this item belongs.
Data regarding the name of this item is recorded in the name data area.

In the item description data area, data regarding the description of this item is recorded. For items distributed in the market, identification information (JAN code, etc.) that can be identified in the market, such as model number, is recorded. For items that are not distributed on the market, record the contents of the items. Further, in this data area, an image taken of this item and the feature amount of this image (item feature amount) are recorded. This item feature amount is used when identifying each item in an image.

In the initial price data area, data regarding the price when the master user registers this item is recorded.
In the shareability data area, data regarding a flag for determining whether information about this item can be shared with other users is recorded. Common items on the market are set to be shareable. On the other hand, items that are not distributed on the market and are confidential cannot be shared. Furthermore, the user may be able to arbitrarily specify a desired information sharing destination.

In the expected transaction price data area, data regarding the price assumed for the case where this item is traded is recorded. The expected transaction price is a price assumed by a third party different from the master user.

As shown in FIG. 3(b), the user information storage unit 23 records a user management record 230 regarding the user of this service. In the present embodiment, users include not only individual users but also businesses that carry out item buying and selling businesses. This user management record 230 is recorded when user registration is performed. The user management record 230 is associated with a property management record 232, a desired property management record 233, and a possession master management record 234.

The user management record 230 records data regarding the user ID, contact information, address, and total value.
The user ID data area records data regarding an identifier for identifying each user.

In the contact data area, data regarding the contact information of this user is recorded. As the contact information, for example, an e-mail address, an application ID of an asset management application installed on the user terminal 10, etc. can be used.
Data regarding the address of this user is recorded in the address data area.
The total value data area records data regarding the total value of the user's belongings.

The property management record 232 records data regarding the individual item ID, registration date and time, update date and time, master item ID, desired offer price, item value, item status, item memo, and whether or not the price can be updated for the user's property. Ru. These possessions include not only tangible things, but also intangible things such as financial products, ideas, data such as digital assets, and skills and qualifications.

In the individual item ID data area, data related to an identifier for identifying an item that is a property is recorded.
In the registration date and time data area, data related to the date and time when the property management record 232 was registered is recorded.
In the update date and time data area, data regarding the latest date and time when the property management record 232 was viewed by the user is recorded.

The master item ID data area records data related to the master item ID used to register this item.
In the desired offer price data area, data regarding the desired price for offering this property is recorded. This price includes a desired price for sale, a desired price for rental, etc.

In the item value data area, data regarding the price when this property is distributed is recorded. For financial products, data regarding the amount at which this financial product was valued is recorded.

The item state data area records data regarding an identifier for specifying the state of an item.
In the item memo data area, data regarding the user's memorandum regarding this property is recorded.
In the price updateability data area, a flag indicating whether the evaluation price of this item can be updated is recorded.

The desired item management record 233 records data regarding the individual item ID, registration date and time, update date and time, master item ID, and desired acquisition price for the item that the user desires to own.

In the individual item ID data area, data regarding an identifier for specifying a desired item is recorded.
In the registration date and time data area, data regarding the year, month, day, and time when the desired object management record 233 was registered is recorded.
In the update date and time data area, data regarding the latest date and time when the desired item management record 233 was viewed by the user is recorded.

The master item ID data area records data related to the master item ID used to register this item.
In the desired acquisition price data area, data regarding the price for acquiring the desired item is recorded. This price includes a purchase price, a rental price, etc. Furthermore, the price may be recorded in association with the item status (new, used). As this desired acquisition price, a price (the same amount or a predetermined ratio) determined based on the expected transaction price recorded in the master information storage unit 22 can be used.

The owned master management record 234 records data regarding the master item ID and master evaluation amount for the item master record 220 registered by this user.
In the master item ID data area, data regarding an identifier for specifying the item master record 220 registered by this user is recorded.

In the master valuation data area, data regarding the valuation of this item master record 220 is recorded. In this embodiment, this evaluation amount is determined based on the master usage status of the master item ID. The master evaluation amount is calculated using, for example, the number of individual item registrations, the number of recommendations, and the recommendation unit price.

Market site 30 is a computer system that manages user transactions. The market site 30 is assumed to be an auction site, an EC portal site, or the like. The market site 30 publishes, as transaction information for each item, contract information (contract date and time, contract amount) on which the transaction was concluded, and board information displaying the desired sales price and purchase price (last publication date, amount). In this market site 30, item master records 220 can also be bought and sold.

(overview)
An overview of this service will be explained.
First, the control unit 21 of the management server 20 executes item registration processing. Here, through the user input process, the control unit 21 acquires information regarding the user's belongings and desired items from the user terminal 10. In this case, the master information registered in the master information storage section 22 is checked. Here, if there is no item registered, a new item is registered in the master information storage section 22. Then, using the master information registered in the master information storage section 22, information regarding the user's belongings and desired items is registered in the user information storage section 23.

Furthermore, the master information registered in the master information storage unit 22 is subjected to duplication management processing and asset conversion processing, which will be described later.
Furthermore, information regarding the user's possessions and desired items is updated in the user information storage unit 23 through processing at the time of transaction.

Next, the control unit 21 of the management server 20 executes market price calculation processing and property evaluation processing. Specifically, the control unit 21 specifies the price of the user's property. Note that there are prices for selling and for renting, but these are different transaction forms, and the following will be explained using the case for selling.

Next, the control unit 21 of the management server 20 executes a property transaction proposal process. Specifically, the control unit 21 proposes a transaction to the user and mediates the transaction. This transaction proposal includes a recommendation from a business operator to a user who has registered a property or desired item.

(Processing at user input)
First, the user input process in the item registration process will be described with reference to FIG.
Here, the control unit 21 of the management server 20 executes an information registration screen display process (step S101). Specifically, a user who wishes to register information starts an asset management application on the user terminal 10 and accesses the management server 20. In this case, the registration unit 211 of the control unit 21 outputs a menu screen to the user terminal 10. When the information input button is selected on this menu screen, the registration unit 211 outputs an information registration screen to the user terminal 10. This information registration screen is provided with an input field for item information (including financial assets, possessions, and desired items) that the user desires to register.

The control unit 21 of the management server 20 executes an item information acquisition process (step S102). Specifically, the user uses the information registration screen to input item information (including financial assets, possessions, and desired items) desired to be registered. For financial assets, enter the financial asset type and appraisal value. For owned items, input the item details, desired offer price, item status, item memo, and whether or not the price can be updated. For desired items, enter the item details and desired price. The item contents include keywords such as item type, name, item description (including item status), and the like. In this case, the registration unit 211 of the control unit 21 acquires registration desired item information from the user terminal 10.

Next, the control unit 21 of the management server 20 executes a search process (step S103). Specifically, the registration unit 211 of the control unit 21 uses the master information storage unit 22 to search the item master record 220 (master information) using the desired registration item information acquired from the user terminal 10 as a search key. In this case, a fuzzy search is performed to identify similar items whose keywords match at a predetermined rate.

Next, the control unit 21 of the management server 20 executes a determination process as to whether there is a similar registration (step S104). Specifically, when the registration unit 211 of the control unit 21 identifies item master records 220 with matching keywords at a predetermined ratio, it determines that there is similar registration.

If it is determined that there is a similar registration (“YES” in step S104), the control unit 21 of the management server 20 executes a confirmation screen display process (step S105). Specifically, the registration unit 211 of the control unit 21 generates a confirmation screen that displays a list of similar items in a selectable manner. Then, the registration unit 211 outputs it to the display device H13 of the user terminal 10. This confirmation screen includes a master registration request button depending on whether or not a new registration is desired.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not a registered master is to be used (step S106). Specifically, when the registration unit 211 of the control unit 21 detects selection of a similar item on the confirmation screen, it determines that a registered master is to be used. On the other hand, when the registration unit 211 detects selection of the master registration request button, it determines that the registered master is not used.

Next, if it is determined that the registered master is not to be used ("NO" in step S106), the control unit 21 of the management server 20 executes a new item master registration process (step S107). Specifically, the registration unit 211 of the control unit 21 assigns a master item ID to the desired registration item information acquired from the user terminal 10. Further, the registration unit 211 generates an item master record 220 (new master information) in which the master item ID is recorded based on the item information desired to be registered, and records it in the master information storage unit 22.

On the other hand, if it is determined that there is no similar registration ("NO" in step S104), the control unit 21 of the management server 20 performs a process of displaying a confirmation screen (step S105), and a process of determining whether or not to use an already registered master. (Step S106) is skipped. Then, in response to the selection of the master registration request button, the registration unit 211 of the control unit 21 executes a new item master registration process (step S107).

Further, when it is determined that a registered master is to be used (“YES” in step S106), the control unit 21 of the management server 20 specifies the master item ID of the selected similar item. Then, the control unit 21 skips the new item master registration process (step S107).

Next, the control unit 21 of the management server 20 executes user information registration processing (step S108). Specifically, the registration unit 211 of the control unit 21 uses the user information acquired from the user terminal 10 to generate a property management record 232 and a desired property management record 233, and records them in the user information storage unit 23. In this case, the master item ID registered as a master in the master information storage section 22 is used. Furthermore, the registration unit 211 records individual registration information (individual item ID) as the master usage status in the item master record 220 of the used master item ID.

(duplicate management process)
Next, the duplication management process will be explained using FIG. 5. This duplication management process is periodically executed for the shareable item master record 220. Note that the execution timing is not limited to a regular period, and may be determined by the administrator or any timing that satisfies preset execution conditions.

Here, the control unit 21 of the management server 20 executes duplicate registration confirmation processing (step S201). Specifically, the registration unit 211 of the control unit 21 mutually compares the item type, name, and item description of the item master records 220 in which the shareable flag is recorded in the master information storage unit 22. Then, the registration unit 211 checks whether there is duplicate registration for the same item.

Next, the control unit 21 of the management server 20 executes a determination process as to whether there is any duplication (step S202). Specifically, when the registration unit 211 of the control unit 21 identifies item master records 220 whose item types, names, and item descriptions match at a predetermined ratio, it determines that there is duplication. In this case, a plurality of item master records 220 having a common item are treated as a duplicate registration group.

If it is determined that there is no duplication (“NO” in step S202), the control unit 21 of the management server 20 ends the duplication management process.
On the other hand, if it is determined that there is overlap ("YES" in step S202), the control unit 21 of the management server 20 repeats the following process for each overlap registration group.

First, the control unit 21 of the management server 20 executes usage status identification processing (step S203). Specifically, the registration unit 211 of the control unit 21 identifies each master item ID recorded in each item master record 220 belonging to the duplicate registration group. Next, the registration unit 211 specifies the master usage status of the immediately adjacent period in the item master record 220 for each specified master item ID.

The control unit 21 of the management server 20 executes a determination process as to whether or not integration is possible (step S204). Specifically, the registration unit 211 of the control unit 21 compares the master usage status for each master item ID. Here, we will compare the number of individual registrations and the number of recommendations. Then, the registration unit 211 checks whether each master usage status satisfies the integration condition. In this integration condition, conditions for integrating records regarding common items are recorded. For example, if the master item ID with the highest number of master uses (number of individual registrations and number of recommendations) is equal to or greater than the reference number, it is determined that integration is possible.

If it is determined that integration is possible (“YES” in step S204), the control unit 21 of the management server 20 executes the integration process (step S205). Specifically, the registration unit 211 of the control unit 21 adds the master usage status of the item master record 220 of the integration source to the master usage status of the item master record 220 of the integration destination. Then, the registration unit 211 deletes the item master record 220 of the integration source from the master information storage unit 22. Furthermore, the registration unit 211 extracts from the user information storage unit 23 the property management record 232 and the desired item management record 233 in which the master item ID of the integration source is recorded. Then, the registration unit 211 updates the master item ID of the integration source to the master item ID of the integration destination.

On the other hand, if the integration condition is not satisfied and it is determined that integration is not possible (“NO” in step S204), the control unit 21 of the management server 20 skips the integration process (step S205) and Terminates the process.
Then, the above process is repeated for all duplicate registration groups.

(Asset processing)
Next, the asset conversion process will be explained using FIG. 6. This asset conversion process is periodically executed for the shareable item master record 220.

Here, the control unit 21 of the management server 20 repeats the following process for each item master record.
First, the control unit 21 of the management server 20 executes a value evaluation process according to usage status (step S301). Specifically, the evaluation unit 212 of the control unit 21 acquires the master usage status of the item master record 220. Next, the evaluation unit 212 uses the master evaluation function to calculate a master evaluation amount according to the master usage status. Then, the evaluation unit 212 records the calculated master evaluation amount in the retained master management record 234 of the user information storage unit 23.

Next, the control unit 21 of the management server 20 executes privilege processing according to the evaluation result (step S302). Specifically, the evaluation unit 212 of the control unit 21 uses a benefit calculation function to determine a benefit according to the master evaluation amount. The evaluation unit 212 then sends the benefit to the contact information in the user management record 230.
The above process is repeated until completed for all item master records.

(Processing at the time of transaction)
Next, the processing at the time of transaction will be explained using FIG.

First, the control unit 21 of the management server 20 executes transaction monitoring processing (step S401). Specifically, the registration unit 211 of the control unit 21 uses the asset management application of the user terminal 10 to monitor the execution state of the transaction application used for transactions.

Next, the control unit 21 of the management server 20 executes buying and selling information acquisition processing (step S402). Specifically, when the registration unit 211 of the control unit 21 detects buying and selling in the trading application, it acquires buying and selling information in the transaction. This sales information includes information regarding items purchased by the user and items provided by the user. Furthermore, this buying and selling includes buying and selling of the item master record 220.

Next, the control unit 21 of the management server 20 executes user information update processing according to the buying and selling results (step S403). Specifically, when detecting an item purchase, the registration unit 211 of the control unit 21 identifies the item type of the purchased item and determines whether it is an asset target using the asset target table. Then, when the registration unit 211 determines that the item is an asset, it generates a property management record 232 and records it in the user information storage unit 23 . Further, when detecting the provision of an item, the registration unit 211 specifies the property management record 232 based on the provided item, and takes action when the item has been sold. For example, it may be deleted from the user information storage unit 23 or a provided flag may be recorded in the property management record 232.

When the item master record 220 is bought or sold, the registration unit 211 generates a master management record 234 owned by the purchasing user and records it in the user information storage unit 23. Further, the registration unit 211 identifies the master management record 234 owned by the sales user and deletes it from the user information storage unit 23 . Further, the registration unit 211 changes the master user of the item master record 220 from the user ID of the user who sold the item master record 220 to the user ID of the user who purchased it.

(Market price calculation process)
Next, the market price calculation process will be explained using FIG. 8. This process is executed periodically.

First, the control unit 21 of the management server 20 repeats the following process for each item recorded in the master information storage unit 22.
Here, the control unit 21 of the management server 20 executes a search process for transaction completion information (step S501). Specifically, the evaluation unit 212 of the control unit 21 accesses the market site 30 and checks whether there is contract information for a transaction that was completed within the most recent predetermined period for the same item as the user's property.

Next, the control unit 21 of the management server 20 executes a determination process as to whether or not a transaction has been concluded (step S502). Specifically, the evaluation unit 212 of the control unit 21 determines that a transaction has been concluded if contract information can be identified.

If it is determined that the transaction has been concluded (“YES” in step S502), the control unit 21 of the management server 20 executes an update process based on the contract information (step S503). Specifically, the evaluation unit 212 of the control unit 21 calculates a statistical value (for example, an average value) of the transaction amount of contract information within a predetermined period with the latest contract date. The evaluation unit 212 then updates the estimated transaction price in the item master record 220 of the master information storage unit 22 with the calculated statistical value.

If it is determined that there is no transaction ("NO" in step S502), the control unit 21 of the management server 20 executes a board information search process (step S504). Specifically, the evaluation unit 212 of the control unit 21 accesses the market site 30 and searches for transaction information for the same item as the user's property. The evaluation unit 212 then checks for transaction information for the same item to see if there is board information for which the item is on sale but no transaction has been completed.

Next, the control unit 21 of the management server 20 executes a determination process as to whether there is board information (step S505). Specifically, the evaluation section 212 of the control section 21 determines that there is board information when the board information can be identified.

If it is determined that there is board information (“YES” in step S505), the control unit 21 of the management server 20 executes an update process based on the board information (step S506). Specifically, the evaluation unit 212 of the control unit 21 calculates statistical values (for example, average values) of the desired sales price and desired purchase price of board information within a predetermined period with the latest publication date. The evaluation unit 212 then updates the estimated transaction price in the item master record 220 of the master information storage unit 22 with the calculated statistical value. Note that prices may be predicted from board information using not only statistical values but also machine learning or the like.

If it is determined that there is no board information (“NO” in step S505), the control unit 21 of the management server 20 executes a search process for the desired item price (step S507). Specifically, the evaluation unit 212 of the control unit 21 searches the user information storage unit 23 for the desired item management record 233 of the same item as the user's property. The evaluation unit 212 then checks whether there is a desired item management record 233 updated within a predetermined period for the same item.

Next, the control unit 21 of the management server 20 executes a determination process as to whether there is a desired price for the item (step S508). Specifically, if the evaluation unit 212 of the control unit 21 is able to identify the desired item management record 233, it determines that there is a desired item price.

If it is determined that there is a desired item price (“YES” in step S508), the control unit 21 of the management server 20 executes an update process based on the desired item price (step S509). Specifically, the evaluation unit 212 of the control unit 21 calculates the expected transaction price by introducing the desired item prices of all specified desired item management records 233 into a value calculation function. The evaluation unit 212 then updates the item master record 220 in the master information storage unit 22 with the calculated expected transaction price.

If it is determined that there is no desired price (“NO” in step S508), the control unit 21 of the management server 20 executes an initial value setting process (step S510). Specifically, the evaluation unit 212 of the control unit 21 updates the expected transaction price in the item master record 220 of the master information storage unit 22 with the initial price.
Repeat the above process until completed for all items.

(Processing of evaluation of property)
Next, the property evaluation process will be explained using FIG. 9. This process is also executed periodically.

Here, the control unit 21 of the management server 20 repeats the following process for each user and for each property recorded in the user information storage unit 23.
Here, the control unit 21 of the management server 20 executes a determination process as to whether the price can be updated (step S601). Specifically, the evaluation unit 212 of the control unit 21 checks the price update availability data area of the property management record 232. If the updatable flag is recorded in the price updatable data area, the evaluation unit 212 determines that the price is updatable. On the other hand, if the update prohibition flag is recorded, the evaluation unit 212 determines that the price cannot be updated.

If it is determined that the price can be updated (“YES” in step S601), the control unit 21 of the management server 20 executes processing to obtain the expected transaction price (step S602). Specifically, the evaluation unit 212 of the control unit 21 acquires the expected transaction price of the property (item) from the item master record 220 of the master information storage unit 22.

Next, the control unit 21 of the management server 20 executes price information update processing (step S603). Specifically, the evaluation unit 212 of the control unit 21 uses the status adjustment table to specify an adjustment rate according to the item status, and calculates the item value using the adjustment rate with respect to the expected transaction price. The evaluation unit 212 then updates the item value in the property management record 232.

On the other hand, if it is determined that the price cannot be updated ("NO" in step S601), the control unit 21 of the management server 20 performs the process of acquiring the estimated transaction price (step S602) and the process of updating price information (step S603). skip.

Then, the control unit 21 of the management server 20 repeats the above process for all the belongings of this user.
When the processing for all the possessions is completed, the control unit 21 of the management server 20 executes the process of acquiring the value of the possession master (step S604). Specifically, the evaluation unit 212 of the control unit 21 obtains the master evaluation amount of the owned master management record 234 if the owned master management record 234 is recorded for this user. The evaluation unit 212 then calculates the total amount of the acquired master evaluation amounts.

Next, the control unit 21 of the management server 20 executes a total value calculation process (step S605). Specifically, the evaluation unit 212 of the control unit 21 totals the item values of all property management records 232 recorded in the user information storage unit 23 for this user. Calculate the total value by adding the total amount.

The evaluation unit 212 then records the calculated total value in the user management record 230 of this user. The above process is repeated for each user.
Next, the control unit 21 of the management server 20 executes value information output processing (step S606). Specifically, when the evaluation unit 212 of the control unit 21 receives access from the asset management application of the user terminal 10, it outputs an asset information screen to the user terminal 10. This asset information screen includes information regarding the price of each property, the master appraisal value of each item master record 220, and the total value.

(Recommendation processing)
Next, recommendation processing will be explained using FIG. 10. A business operator or the like (user) accesses the management server 20 using the user terminal 10 in order to make a transaction proposal (recommendation).

First, the control unit 21 of the management server 20 executes a transaction target search process (step S701). Specifically, the intermediary unit 213 of the control unit 21 outputs an item search screen to the user terminal 10. This item search screen is provided with a keyword input field for searching for items. In this case, the user inputs the keyword of the desired item (including the master item ID) into the keyword input field. The intermediary unit 213 that has acquired the keyword input on the item search screen uses the master information storage unit 22 to identify an item master record 220 related to the keyword. Then, the intermediary unit 213 outputs the search result screen to the user terminal 10. This search result screen includes information recorded in the specified item master record 220. Then, the user specifies a desired item on the search result screen. In this case, the intermediary unit 213 specifies the master item ID of the specified item as a transaction target.

Next, the control unit 21 of the management server 20 executes recommendation destination candidate identification processing (step S702). Specifically, the intermediary unit 213 of the control unit 21 outputs a recommendation destination search screen to the user terminal 10. This recommendation destination search screen includes a selection column for the type of transaction for owned items and desired items. When making a purchase proposal, select the property. On the other hand, when making a sales proposal, the desired item is selected. When the transaction type "purchase proposal" is selected, the intermediary unit 213 searches the user information storage unit 23 for the property management record 232 in which the master item ID of the transaction target is recorded. When the transaction type "sales proposal" is selected, the intermediary unit 213 searches the user information storage unit 23 for the desired item management record 233 in which the master item ID of the transaction target is recorded. Then, the intermediary unit 213 outputs the search result screen to the user terminal 10. This search result screen includes information regarding the individual item IDs of the searched property management records 232 and desired property management records 233.

Here, search conditions other than keywords may be set on the recommendation destination search screen. As the search conditions, information recorded in the user information storage unit 23, such as user attributes, registration time, and price, can be used. In this case, the individual item ID is specified using the user management record 230, property management record 232, and desired item management record 233 that satisfy the set search conditions.

Next, the control unit 21 of the management server 20 executes a recommendation destination specifying process (step S703). Specifically, when the user terminal 10 specifies the individual item ID to be traded (the item to be traded), the intermediary unit 213 of the control unit 21 associates it with the property management record 232 and the desired item management record 233. The specified user management record 230 is identified. Then, the intermediary unit 213 specifies the user ID of the specified user management record 230 as a recommendation destination.

Next, the control unit 21 of the management server 20 executes a transaction proposal transmission process for each recommended destination (step S704). Specifically, the intermediary unit 213 of the control unit 21 identifies the user's contact information in the user management record 230. Then, the intermediary unit 213 makes a transaction proposal to the user's contact information. The trade proposal includes information about the item and price information.

Next, the control unit 21 of the management server 20 executes a process of recording recommendation results (step S705). Specifically, the intermediary unit 213 of the control unit 21 adds recommendation destination information (individual item ID or user ID) to the item master record 220 of the used master item ID in the master information storage unit 22 as the master usage status. Record. This recommendation record is used when a service provider requests a usage amount from a business that proposes a transaction.

(Transaction proposal processing)
Next, the transaction proposal process will be explained using FIG. 11. This process is also executed periodically.
First, the control unit 21 of the management server 20 executes a desired item information acquisition process (step S801). Specifically, the intermediary unit 213 of the control unit 21 acquires any desired item management record 233 from the user information storage unit 23.

Next, the control unit 21 of the management server 20 executes matching processing with property information (step S802). Specifically, the intermediary unit 213 of the control unit 21 extracts the property management record 232 in which the specified desired item is recorded from the user information storage unit 23. Next, the intermediary unit 213 identifies a record in which the desired acquisition price recorded in the desired item management record 233 is higher than the desired offer price recorded in the property management record 232.

Next, the control unit 21 of the management server 20 executes a determination process as to whether there is a transaction candidate (step S803). Specifically, the intermediary unit 213 of the control unit 21 determines that there is a transaction candidate if it can identify a record whose desired acquisition price is higher than the desired offer price.

If it is determined that a record with a desired acquisition price higher than the desired offer price cannot be identified and there are no transaction candidates (“NO” in step S803), the control unit 21 of the management server 20 executes a price proposal process. (Step S804). Specifically, the intermediary unit 213 of the control unit 21 calculates the statistical value of the desired offer price recorded in the property management record 232. Then, when the intermediary unit 213 receives an access from the asset management application of the user terminal 10, it outputs an asset information screen including information regarding the statistical value of the desired item to the user terminal 10.

On the other hand, if it is determined that there is a transaction candidate ("YES" in step S803), the control unit 21 of the management server 20 sequentially identifies the property management records 232 as processing targets and performs the following processing for each transaction candidate. Execute the process.

Here, first, the control unit 21 of the management server 20 executes transaction inquiry processing (step S805). Specifically, the intermediary unit 213 of the control unit 21 uses the user ID of the user management record 230 associated with the property management record 232 and the contact information of the user of the user management record 230 associated with the desired item management record 233. Identify. Then, the intermediary unit 213 makes a transaction proposal to the contact information of both users. The trade proposal includes information about the item and price information.

Next, the control unit 21 of the management server 20 executes a determination process as to whether the transaction is concluded (step S806). Specifically, the intermediary unit 213 of the control unit 21 determines that the transaction has been completed when receiving notifications of acceptance of the transaction proposal from both users within a predetermined period. On the other hand, if any user contacts the user to reject the transaction proposal, or if there is no response within a predetermined period, the intermediary unit 213 determines that the transaction is unsuccessful.

If it is determined that the transaction is unsuccessful (“NO” in step S806), the control unit 21 of the management server 20 ends the process for this transaction candidate and starts the transaction inquiry process (step S805) for the next transaction candidate. repeat.

On the other hand, if it is determined that the transaction has been completed ("YES" in step S806), the control unit 21 of the management server 20 executes remittance instruction processing (step S807). Specifically, the intermediary unit 213 of the control unit 21 instructs the contact information of the user of the desired item to send money to the service provider. For remittance, account transfer, credit card payment, electronic money remittance, etc. can be used.

Then, the control unit 21 of the management server 20 that has received the remittance executes delivery instruction processing (step S808). Specifically, the intermediary unit 213 of the control unit 21 instructs the contact information of the provider of the property to ship it to the address of the service provider. In this case, only the address and transaction ID of the service provider are set in the destination label. The service provider who purchased the property acquires the address of the user of the desired item from the user information storage unit 23 based on the transaction ID, and outputs a destination label on which this address is printed. In this case, anonymous delivery may be used. In this case, the delivery company is provided with information regarding the delivery source and the delivery destination, so that the delivery source and the delivery destination are not made aware of the address, etc. of the other party. Then, forward the delivery. When the intermediary unit 213 obtains delivery completion information from the tracking information of the delivery item, the intermediary unit 213 remits the transaction amount to the provider.
The above processing is performed for each transaction candidate.

According to this embodiment, the following effects can be obtained.
(1) In this embodiment, the control unit 21 of the management server 20 executes a process upon user input. This allows the user to register their possessions and desired items. In this case, the user can register the expected price.

(2) In this embodiment, the control unit 21 of the management server 20 executes a search process (step S103). If it is determined that there is a similar registration (“YES” in step S104), the control unit 21 of the management server 20 executes a confirmation screen display process (step S105). Thereby, it is possible to confirm whether or not the item master record 220 exists for the item desired to be registered.

(3) In the present embodiment, when it is determined that the registered master is to be used ("YES" in step S106), the control unit 21 of the management server 20 executes a user information registration process (step S108). This allows the item master record 220 to be used to register possessions.

(4) In the present embodiment, if it is determined that the registered master is not used (“NO” in step S106), the control unit 21 of the management server 20 executes a new item master registration process (step S107). Further, if it is determined that there is no similar registration (“NO” in step S104), the control unit 21 of the management server 20 executes a new item master registration process (step S107). Thereby, registration of the item master record 220 can be promoted.

(5) In this embodiment, the control unit 21 of the management server 20 executes duplication management processing. As a result, the duplicately registered master data is integrated depending on the situation, so it is possible to suppress the item master records 220 from becoming too crowded.

(6) In this embodiment, the control unit 21 of the management server 20 executes asset conversion processing. Thereby, registration of the item master record 220 can be promoted. In particular, since the master evaluation amount is determined according to the master usage status of the item master record 220, it is possible to promote the registration of item master records 220 that are easy to use.

(7) In this embodiment, the control unit 21 of the management server 20 executes processing at the time of transaction. This allows the purchased item to be registered as a property. You can also remove sold items from your inventory.

(8) In the present embodiment, when it is determined that a transaction has been concluded (“YES” in step S502), the control unit 21 of the management server 20 executes an update process based on the contract information (step S503). ). Thereby, the expected transaction price (market value) can be calculated using the contract information.

(9) In the present embodiment, if it is determined that there is board information (“YES” in step S505), the control unit 21 of the management server 20 executes an update process based on the board information (step S506). ). This makes it possible to predict the expected transaction price (market value) even if the transaction has not been completed.

(10) In the present embodiment, if it is determined that there is a desired item price (“YES” in step S508), the control unit 21 of the management server 20 executes an update process based on the desired item price ( Step S509). This makes it possible to predict the expected transaction price (market value) based on the potential price even when there is no product on the market.

(11) In the present embodiment, the control unit 21 of the management server 20 executes property evaluation processing. Thereby, the value of the user's possessions can be objectively evaluated. As a result, it is possible to visualize the potential total assets of the user's belongings and promote transactions.

In this embodiment, a master item registered by a master user is also evaluated as the user's property. Thereby, by increasing the value of item masters that are actively used, it is possible to promote registration of appropriate item masters.

(12) In this embodiment, the control unit 21 of the management server 20 executes recommendation processing. Thereby, using the master item, it is possible to make a transaction proposal to a user who has registered his or her possessions or desired items. Furthermore, the control unit 21 of the management server 20 executes transaction proposal processing. Thereby, it is possible to make a transaction proposal by matching the property that is a potential transaction target with the desired item.

This embodiment can be modified and implemented as follows. This embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
- In the above embodiment, the control unit 21 of the management server 20 executes the information registration screen display process (step S101) and the item information acquisition process (step S102). Acquisition of item information is not limited to user input. For example, regarding financial assets (for example, investment products, corporate stocks, financial institution accounts), information (product information and holding balances) may be obtained through system cooperation with financial institutions, financial business operators, and the like.

- In the above embodiment, the control unit 21 of the management server 20 executes the value evaluation process according to the usage status (step S301). In this case, the master evaluation function is used to calculate the master evaluation amount according to the master usage status. The method for evaluating the item master record 220 is not limited to using the master usage status. For example, the expected transaction price of the item may also be used as a variable in the master evaluation function. For example, a master evaluation function may be used in which the master evaluation amount increases depending on the expected transaction price.

Furthermore, the item master record 220 may be evaluated using a user ID using the master item ID. For example, when a variety of users use the master item ID, a master evaluation function that increases in accordance with the number of user IDs may be used, with the number of user IDs using the master item ID being used as a variable.

- In the above embodiment, the control unit 21 of the management server 20 executes the integration process (step S205). Here, the individual item ID of the integration source and the individual item ID of the integration source may be able to be identified. In this case, the integrated history is recorded in the property management record 232 or the desired property management record 233.

- In the above embodiment, the evaluation unit 212 executes the process of evaluating the user's assets. The evaluation unit 212 maintains a status adjustment table in which adjustment ratios for adjusting the estimated transaction amount are recorded in association with item statuses. Alternatively, item states may be classified according to levels, and the same item may be treated as different items according to the classification. For example, item conditions are classified into condition 1 (new, unused), condition 2 (almost unused), condition 3 (no noticeable scratches), condition 4 (with scratches), condition 5 (generally poor), etc. do. Regarding item A, if it is "new and unused", it is managed as "item A1", and if it is "no noticeable damage", it is managed as "item A3", and so on, and is managed as a separate item for each item condition.

- In the above embodiment, the control unit 21 of the management server 20 calculates the value of the property using contract information, board information, and desired item price. How to calculate the value of your possessions. It is not limited to this. For example, the value of a possession may be calculated using all of contract information, board information, and desired item price for a predetermined item. In this case, the value of the property is calculated by weighting the contract information, board information, and desired item price for the predetermined item in that order.

- In the above embodiment, the control unit 21 of the management server 20 executes transaction inquiry processing (step S805). In addition, the desired offer price and desired acquisition price may be anonymously published and used as board information.

- In the above embodiment, the control unit 21 of the management server 20 executes the user information registration process. In this case, the asset management application of the user terminal 10 and the control unit 21 of the management server 20 cooperate to execute the process. The hardware that executes each process is not limited to the above.

- In the above embodiment, the control unit 21 of the management server 20 calculates the value of the property based on contract information, board information, and desired item price. Here, the value may be calculated taking other factors into consideration.

For example, if the transaction history of similar items can be acquired, the estimated transaction price may be calculated using the prices of the similar items.
Furthermore, the date of acquisition of the property may be recorded in the property management record 232, and changes in value over time may be evaluated according to the number of days that have passed since the date of acquisition. In this case, the life of each item is recorded in the master information storage unit 22. Then, the expected transaction price is adjusted according to the ratio between the number of elapsed days and the life.

DESCRIPTION OF SYMBOLS 10... User terminal, 20... Management server, 21... Control part, 211... Registration part, 212... Evaluation part, 213... Intermediary part, 22... Master information storage part, 23... User information storage part, 24... Learning result storage part , 30...Market site.

Claims (8)

a master information storage unit that records master information about the item;
a user information storage unit that records information regarding individual items of the user;
An item management system comprising: a control unit connected to a user terminal;
The control section,
Obtaining item information about individual items from the user terminal,
When a master registration request is obtained for the item information, recording new master information in the master information storage unit;
registering an item in the user information storage unit in association with master information recorded in the master information storage unit;
An item management system characterized in that a master usage status is recorded in the master information used for the item registration. 2. The control unit, when acquiring item information from the user terminal, searches for master information regarding the item information in the master information storage unit and outputs it to the user terminal. Item management system. The item management system according to claim 1 or 2, wherein the control unit calculates a master evaluation amount of the master information according to the master usage status. 4. The item management system according to claim 3, wherein the control unit provides a benefit to the user who has registered the master information according to the master evaluation amount. The user information storage unit records information regarding the item value of individual items owned by each user,
4. The item management system according to claim 3, wherein the control unit outputs asset information including the item value and the master evaluation amount to the user terminal. The control section,
Obtaining a transaction proposal for the individual item registered in the user information storage unit,
3. The item management system according to claim 1, wherein the master usage status is recorded in master information used to register the target item of the transaction proposal. a master information storage unit that records master information about the item;
a user information storage unit that records information regarding individual items of the user;
A method for managing items using an item management system comprising: a control unit connected to a user terminal;
The control section,
Obtaining item information about individual items from the user terminal,
When a master registration request is obtained for the item information, recording new master information in the master information storage unit;
registering an item in the user information storage unit in association with master information recorded in the master information storage unit;
An item management method characterized by recording master usage status in master information used for item registration. a master information storage unit that records master information about the item;
a user information storage unit that records information regarding individual items of the user;
An item management program for managing items using an item management system comprising a control unit connected to a user terminal,
The control section,
Obtaining item information about individual items from the user terminal,
When a master registration request is obtained for the item information, recording new master information in the master information storage unit;
registering an item in the user information storage unit in association with master information recorded in the master information storage unit;
An item management program for functioning as a means for recording master usage status in master information used for item registration.

Images