Ticket-based order processing server

Abstract

It is economically difficult to build an IT system tailored to the specific needs of a loss-making project site. [Solution] The server 50 has a basic application provision unit 51 that provides basic applications for use in the IT system, and a custom unit 52 that receives orders for application development to customize the basic applications. The custom unit 52 has a ticket management unit 53 that processes ticket issuance and other operations, and a ticket display unit 54 that displays tickets. The ticket management unit 53 issues tickets to users when the user completes the purchase process. Vendors sell a certain number of tickets to users in advance, and users pay vendors with tickets according to the site. Extra tickets can be purchased at profitable sites and the surplus tickets can be used at unprofitable sites, so an IT system can be built at any site.

Description

Technical Field

[0001] The present invention relates to a ticket-based order receiving and issuing server used for projects such as subcontracting work.

Background Art

[0002] Particularly in small and medium-sized enterprises in the construction industry, the progress of IT implementation is slow. Also, in the unique structure of the construction industry, from the beginning, a site can be distinguished as a profitable site or a loss-making site in terms of subcontracting work units. However, in any case, the order-receiving side has no choice but to accept the order. In the future, in order to ensure the efficiency and transparency of the site, whether it is profitable or loss-making, an IT system must be introduced.

[0003] Particularly, because the situation varies from site to site in the IT system, existing IT systems cannot be diverted, or similar IT systems cannot be directly applied, so customization may be required. The introduction of an IT system can almost never be billed to the client including the construction cost, so the order receiver has to procure it by themselves. [[ID=--]]

[0004] However, since it is difficult to bear the cost of the IT system especially in the case of a loss-making site, there are many cases where the introduction of the IT system is hesitated when accepting an order for a loss-making site.

[0005] Although there is currently no known prior art for solving such problems, as technologies related to the IT system at the construction site, those described in Patent Document 1 are known. [[ID=--]] [[ID=2--]]

Prior Art Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] The present invention aims to enable the introduction of IT systems tailored to each specific site, even when profitability varies significantly from site to site, as described above. [Means for solving the problem]

[0008] The ticket-based order placement and receiving server according to the present invention is a server that performs order placement and receiving processing online and has ticket management means that pre-purchases electronic tickets from vendors for a user based on user information and vendor information, and processes payment to the vendor from the user based on the user information and vendor information, and ticket display means that displays the status of the tickets held. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram showing an IT system according to an embodiment of the present invention. [Figure 2] This is an explanatory diagram showing an example of a screen displayed by the ticket display unit. [Figure 3] This block diagram shows the configuration of an IT system that can be applied across different industries. [Modes for carrying out the invention]

[0010] Figure 1 is a block diagram showing a system according to an embodiment of the present invention. This system 100 includes a user terminal 1 owned by a user, a vendor terminal 2 owned by a vendor, a server 50 configured with the following functions using software and hardware, and a network 3 connecting the user terminal 1, the vendor terminal 2, and the server 50. The vendor terminal 2 and the user terminal 1 are arbitrary general-purpose terminals. The server 50 may be composed of one or more hardware and software components connected by the network 3 to form the whole system.

[0011] This system 100 is suitable when a vendor is engaged in a different business (in this embodiment, construction work) from IT system construction and software development, and introduces a ticket system to transactions for IT system construction and construction work. The server 50 has a basic application provision unit 51 that provides basic applications to be used in the IT system, and a custom unit 52 that receives orders for application development to customize the basic applications.

[0012] The custom unit 52 includes a ticket management unit 53 that processes ticket issuance and other operations, and a ticket display unit 54 that displays tickets. The ticket display unit 54 displays predetermined information on the vendor terminal 2, the user terminal 1, and the display of a designated computer (not shown).

[0013] The ticket management unit 53 issues a ticket to a user upon the user's purchase process. The ticket is issued electronically based on user information and vendor information and can be displayed and verified on the ticket display unit 54. The ticket display unit 54 is processed to be displayed on the screens of the vendor terminal 2 and the user terminal 1. The ticket displays who currently holds it based on the user information and vendor information.

[0014] Ticket ownership information is stored in the ticket management unit 53, and the history of its transfer is also stored in the ticket management unit 53. Only users registered in the ticket management unit 53 are eligible to transfer tickets. Third parties who can receive tickets are registered in the ticket management unit 53. Users can only transfer tickets to registered third parties. In order for users and third parties to be registered in the ticket management unit 53, they must meet certain conditions set by the vendor. This eliminates the need for vendors to conduct transactions with unwanted users or third parties.

[0015] The value of a ticket corresponds to the purchase price. For example, one ticket may be purchased for 1000 yen. The current value of a ticket is displayed in the ticket display unit 54. The ticket management unit 53 can set the value of a single ticket. Since the value of a single ticket can be changed after purchase, it can be adjusted according to fluctuations in raw material prices, etc. In this case, it is possible to make a de facto price adjustment without changing the number of tickets paid for a single service (for example, one type of construction work). In the relative relationship between the user and the vendor, there is no de facto change if the number of tickets is the same, but the current ticket price can be reflected in the valuation when the user transfers tickets to a third party. Even if the price of a ticket at the time of purchase differs for the user, the vendor, and the third party, when trading using only tickets, there is no change among those within the scope of the parties involved (those trading with tickets).

[0016] In construction projects, some sites are expected to be profitable, while others are expected to be unprofitable. Users purchase extra tickets when building IT systems for profitable sites. The IT systems for profitable sites are customized by the vendor based on the user's selection of appropriate applications from the basic application provider unit 51. For example, if a basic application is a site communication (email) IT system, and that site requires a special process for communication, the user selects a specific basic application and requests the vendor to customize it to perform the aforementioned special process.

[0017] The customization unit 52 receives requests from users and processes the payment to the vendor for these requests using tickets. Specifically, as shown in Figure 2, the ticket display unit 54 displays the price of various customizations as the number of tickets. When a customization is selected, the customization unit 52 processes the request for that customization from the user terminal 1 to the vendor terminal 2. In the ticket management unit 53 of the customization unit 52, when the user makes a payment to the vendor, the ticket is transferred from the user to the vendor, and this transfer information is stored.

[0018] The ticket display unit 54 displays the current ticket ownership status. Unused tickets are stored in the ticket management unit 53 under the name of the user who purchased them. The ticket management unit 53 has folders for each user and vendor to store tickets, similar to wallets. After the transfer, the tickets are placed in the user's or vendor's folder, allowing them to visually check how many tickets they currently own. The method of displaying tickets (design, etc.) is optional.

[0019] A user uses some of their tickets to procure IT systems at a profitable site, but still has remaining tickets. The user then uses these surplus tickets at a different site, one that is operating at a loss. The user or vendor determines whether a site is profitable or not based on experience or arithmetic. For example, efficient operations will result in a profit, while inefficient operations will result in a loss. Since those skilled in the art can predict the balance of income and expenses to some extent in advance based on material costs, labor costs, etc., they purchase extra tickets at profitable sites to prepare for loss-making sites.

[0020] When commencing work on a project that is operating at a loss, the user selects an appropriate basic application from the basic application provider unit 51 from user terminal 1 and places an order with the custom unit 52 for customization of this basic application. The custom unit 52 receives the order information from user terminal 1 and processes it to receive payment in the form of a ticket. In this case as well, the customization request information from user terminal 1 is sent to vendor terminal 2 via server 50.

[0021] Thus, according to the system of the present invention, a ticket system is adopted for payment of fees for contract work. These tickets are purchased at the expense of profitable construction sites, and any remaining tickets are used to build IT systems for unprofitable construction sites. This makes it possible to build IT systems tailored to the specific needs of each site, even in unprofitable locations. Furthermore, because users hold extra tickets, there is an incentive to consume them, leading to increased ordering and receiving of IT systems. As a result, the IT transformation of construction sites is promoted.

[0022] [Use across different industries] Next, in this server 50, tickets can be used in different operations. When a user requests an IT system construction from a vendor, the user can pay the IT system development cost with the tickets purchased once, and pay for the content requested from the vendor with the remaining tickets. For example, when the user requests a construction project from a vendor, this consideration can be paid with tickets. In this case, the user requests different operations of IT system development and construction project from the vendor, and can pay with tickets respectively.

[0023] FIG. 3 is a block diagram showing the configuration of a system applicable to different industries. In this system 150, the server 50 has a basic construction providing unit 55. The customization unit 52 has a function of trading customization work with tickets. The user requests a construction from the server 50 from the user terminal 1. When the request information is transmitted from the user terminal 1 to the server 50, the request information is transmitted to the vendor terminal 2. In the basic construction providing unit 55, the vendor can select basic construction from the vendor terminal 2. Payment with tickets is also required for basic construction. The ticket display unit 54 displays the content of the basic construction together with the required number of tickets, and also displays the required number of tickets for the customization work for the basic construction. [[ID=]10]

[0024] Unlike applications, construction always involves work, so tickets are required for basic construction. In customization work, when part of the work is omitted, etc., the work is reduced, so a negative number of tickets may be displayed from the tickets for basic construction. When the user is in a deficit situation, it is convenient for the user if not only the above IT system but also the construction project can be ordered from the vendor and paid with the surplus tickets.

[0025] In this way, the customization unit 52 defines the content when customizing the basic service, and shows the consideration with tickets. In the above, examples of IT system development and construction project are given, but combinations of other industries may also be possible.

[0026] [assignment] Furthermore, tickets are transferable to business partners (third parties) other than the vendor and the user. The third party to whom the ticket can be transferred is limited to those authorized by the vendor. Once authorized, the third party can freely transfer and acquire the ticket thereafter. A ticket has characteristics between an assignment of receivables that requires authorization and currency that does not require authorization. Information on users to whom tickets can be transferred is registered in the ticket management unit 53. Information on the transfer of tickets is also registered in the ticket management unit 53.

[0027] The aforementioned third party, if authorized, can make direct payments to the vendor using the ticket. If authorization is not obtained, the ticket may be used only for payment to the user to whom it was transferred. In this case, an agreement on the value is formed between the parties when the payment is made using the ticket. Furthermore, a third party is free to make payments to other third parties using the ticket, but if the transferred third party is not authorized by the vendor, it can only be used to pay the transferor, as described above. If authorization is obtained, it can be used to make payments to the vendor. Authorization can be granted either before or after the transfer.

[0028] Furthermore, payment by a third party using the ticket may be limited to users in the ticket's transfer route. Since the transfer route corresponds to a commercial flow, the use of the ticket will not come as a surprise to the parties involved in the transaction. All of the above transfer regulations are handled by the ticket management unit 53. All of the above transfer regulations are displayed in the ticket display unit 54.

[0029] [Securing Cash Flow] Next, the ticket management unit 53 also allows the vendor to transfer tickets as payment when they commission work to a user. The ticket management unit 53 has an optional step of allowing the vendor to pay the user with tickets when they commission work. The vendor can use the cash received from the client to temporarily hold onto it and secure cash flow. This is useful when the vendor is working on a loss-making project and the user is working on a profitable project.

[0030] Payment methods can be selected based on a combination of profitable and unprofitable projects. For example, efficient operations will result in a profit, while inefficient operations will result in a loss. The contractor can predict the income and expenses to some extent in advance based on material costs, labor costs, etc.

[0031] Vendors and users can select the following payment methods in the ticket management unit 53 based on whether the site is operating at a loss or at a profit. The selection of whether a site is operating at a loss or at a profit shall be made by the parties involved on the screen. Vendor requests premium ticket payment (new ticket issuance) for unprofitable projects. Profitable venues: Cash payment / Payment with premium tickets (new ticket issuance) User request: Ticket payment for a loss-making event (using surplus tickets) Profitable site; payment made with purchased tickets.

[0032] Vendors may, in order to secure cash flow, pay users with tickets at a premium (for example, by increasing the number of tickets by 10%) when paying with tickets, even at profitable sites as well as loss-making sites. The ticket management unit 53 can be configured to automatically apply a premium when payment is made with tickets. By paying directly with tickets, it is possible to flatten the cash flow.

[0033] [Value changes between off-season and peak season] Furthermore, the value of tickets may be made variable depending on the time of year. Since construction projects have off-peak and peak seasons, increasing the value of tickets during off-peak seasons (those already purchased by the user) makes ordering during off-peak seasons more advantageous for the user. The settings for off-peak and peak seasons, as well as the setting of ticket values, are handled by the ticket management unit 53, and this can be confirmed by the user on the ticket display unit 54. Peak and off-peak seasons can be set, for example, on a monthly or weekly basis. [Explanation of Symbols]

[0034] 100 IT Systems 50 servers 51 Basic Application Provision Department 52 Customization Department 53 Ticket Management Department 54 Ticket display section

Claims

[Claim 1] A server that processes orders online, A ticket management means that pre-purchases an electronic ticket from a vendor for a user based on user information and vendor information, and processes payment from the user to the vendor using the ticket based on the user information and vendor information, A ticket display means for displaying the status of the aforementioned tickets, A ticket-based order placement and receiving server.

Images