JP7670604B2 - Dwelling unit sales management device, dwelling unit sales management method, and dwelling unit sales management program - Google Patents

Description

The present invention relates to a residence sales management device, a residence sales management method, and a residence sales management program.

For example, in condominium sales, delays in delivery dates due to contract changes or external factors are not uncommon, and collection plans cannot be accurately determined until delivery is confirmed. For example, Patent Document 1 is an example of a conventional management system for condominium sales.

JP 2019-95972 A

However, Patent Document 1 does not state anything about creating a sales forecast (for example, based on the number of units and amount) linked to delivery schedules for residential unit sales, understanding the status and trends of residential unit sales, reservation contract status, and monthly sales progress from the start of the contract, and analyzing the trends.

The present invention has been made in consideration of the above, and aims to provide a dwelling unit sales management device, dwelling unit sales management method, and dwelling unit sales management program that can create a sales forecast linked to delivery schedules in dwelling unit sales, and can grasp and analyze the status and trends of dwelling unit sales, reservation contract status, and monthly sales progress from the start of a contract.

In order to solve the above problems and achieve the objective, the present invention provides a dwelling unit sales management device equipped with a control unit, the control unit being configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, and characterized in that the device is equipped with a contract processing means for registering contract information data including a contract number, project, property name, dwelling unit number, application date, contract date, and scheduled delivery date, and a delivery status data processing means for aggregating the contract information data by year and month for each property in the project, and creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not yet contracted as of that year and month, and the sales amount obtained by aggregating the sales prices of the dwelling units to be delivered by referring to the first master.

According to one aspect of the present invention, the delivery status data processing means may create and output delivery status data for all properties of the project by tallying up all properties of the project by year and month based on the delivery status data, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered dwelling units/total number of dwelling units x 100.

According to one aspect of the present invention, the control unit may be configured to be able to access a second master in which a target amount is registered for each project, and may include a project-specific transition processing means for creating and outputting project-specific transition data based on delivery status data for all properties in the project, the project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount/target amount of the project in the second master x 100, for each year and month of the project.

According to one aspect of the present invention, the dwelling unit may include an apartment or a detached house.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a method for managing the sale of dwelling units executed by an information processing device equipped with a control unit, the control unit being configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, and the method includes a contract processing step executed by the control unit to register contract information data including the contract number, project, property name, dwelling unit number, application date, contract date, and scheduled delivery date, and a delivery status data processing step to create and output delivery status data for each property of the project by aggregating the contract information data by year and month, and including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not yet contracted as of that year and month, and the sales amount obtained by aggregating the sales prices of the dwelling units to be delivered by referring to the first master.

In order to solve the above-mentioned problems and achieve the object, the present invention is a dwelling unit sales management program to be executed by an information processing device having a control unit, the control unit being configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered, and the control unit is configured to execute a contract processing step of registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date, and a delivery status data processing step of aggregating the contract information data by year and month for each property in the project, and creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of the year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not yet contracted as of the year and month, and the sales amount obtained by aggregating the sales prices of the dwelling units to be delivered by referring to the first master.

According to the present invention, in the sale of residential units, it is possible to create a sales forecast linked to the scheduled delivery date, and to grasp and analyze the status and trends of residential unit sales, reservation contract status, and monthly sales progress from the start of the contract.

FIG. 1 is a block diagram showing an example of the configuration of a dwelling unit sales management device according to the present embodiment. FIG. 2 is a diagram showing an example of the configuration of the property room information master. FIG. 3 is a diagram showing an example of the configuration of the project goal master. FIG. 4 is a diagram showing a flow for explaining an outline of the overall processing of the control unit of the information processing device in this embodiment. FIG. 5 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device according to the present embodiment. FIG. 6 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device in this embodiment. FIG. 7 is a diagram showing sample data for explaining a specific example of the process of the control unit of the information processing device in this embodiment.

The embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
For example, in condominium sales, delays in handover due to contract changes or external factors are not rare, and it is not possible to accurately grasp the expected recovery until the handover is confirmed. In addition, in the real estate developer industry that uses an investment recovery model, management of financial plans is essential, and visualization of the expected recovery is a very important issue. In addition, when deciding how to deal with unsold properties (hold them as they are, rent them out, sell them to a competitor, etc.), it is desirable to be able to analyze them both inside and outside the project.

In this embodiment, a sales forecast (based on number of units and amount) is created based on the delivery schedule, and the collection schedule at the contract stage (not yet delivered) is clarified using delivery status data. In addition, sales progress and trends are analyzed on a project-by-project basis, and if properties are not sold out after the project is launched and completed, and there are unsold properties, the subsequent sales, number of remaining properties, and the number of months elapsed are analyzed from the start of the contract.

This allows you to compare progress and trends on a project-by-project basis, which contributes to planning for individual projects (rentals and sales) as well as for future projects. In addition, by clarifying the recovery schedule, it becomes possible to more concretely consider the start date for the next development project.

The present invention is widely applicable to industries that sell residential units, such as the real estate development industry and the real estate distribution industry. In the following example, condominium sales are used as an example, but the residential unit sales management device of the present invention is applicable not only to condominium sales, but also to sales of detached houses, etc.

2. Configuration
FIG. 1 is a block diagram showing an example of the configuration of a dwelling unit sales management device 100 according to the present embodiment. In FIG. 1, the dwelling unit sales management device 100 is, for example, a commercially available desktop personal computer. The dwelling unit sales management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. The dwelling unit sales management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. Each unit included in the dwelling unit sales management device 100 is connected to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the residence sales management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the residence sales management device 100 to the server 200 and the bank system 400 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give commands to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, optical disks, and the like can be used.

The storage unit 106 includes a property room information master (first master) 106a, a project goal master (second master) 106b, and a data file 106c. Figure 2 is a diagram showing an example of the configuration of the property room information master 106a. Figure 3 is a diagram showing an example of the configuration of the project goal master 106b.

As shown in FIG. 2, the property room information master 106a can be configured as a table in which data on property name, room number, and sales price are associated and registered. In the example shown in FIG. 2, the first line has the property name "Property A", room number "101", and sales price "40,000,000". The property room information master 106a is linked to the contract information data using the property name and room number as keys, and the sales price is read out using the property name and room number as keys.

As shown in FIG. 3, the project goal master 106b can be configured as a table in which project numbers and target amounts are associated and registered. In the example shown in FIG. 3, the first line has the project number "P001" and the target amount "200,000,000." The target amount is read from the project goal master 106b using the project number as a key.

Data file 106c is a file for storing various data such as contract information data, delivery status data, delivery status data for all properties in the project, and progress data by project.

The contract information data may include the contract number, project number, property name, room number, application date, contract date, scheduled delivery date, and delivery date.

The delivery status data may include data on the year and month, the number of delivered units, delivered units, undelivered units, and vacant units, the subtotal, and the sales amount. The delivery status data for all properties in the project may include data on the number of delivered units, the sales amount, the cumulative sales amount, and the delivery rate.

Project-specific progress data may include project number, number of units delivered, cumulative sales amount, delivery rate, and achievement rate.

Returning to FIG. 1, the control unit 102 is a CPU or the like that provides overall control of the residence sales management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

The control unit 102 is configured to be able to access the property room information master 106a, the project goal master 106b, the data file 106c, and the like, which are stored in the memory unit 106. Note that the property room information master 106a, the project goal master 106b, and the data file 106c may be provided in another location (e.g., the server 200), as long as the control unit 102 is able to access them.

The control unit 102, in terms of its functional concept, comprises a contract processing unit 102a, a delivery status processing unit 102b, a project-specific transition processing unit 102c, a master maintenance unit 102d, and a screen display control unit 102e.

The contract processing unit 102a inputs contract information data including the contract (contract number and/or contract name), project (project number and/or project name), property name, room number (apartment number), application date, contract date, and scheduled delivery date in response to, for example, an operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data file 106c.

The delivery status processing unit 102b aggregates the contract information data registered in the data file 106c by year and month for each property in the project, creates delivery status data including the number of units to be delivered that are scheduled to be delivered as of that year and month, units that have already been delivered, units that have not been delivered, and vacant units that are not under contract as of that year and month, as well as the sales amount calculated by aggregating the sales prices of the units to be delivered by referencing the property room information master 106a, and registers the data in the data file 106c or displays it on the monitor 114.

In addition, the delivery status processing unit 102b tally up all properties in the project by year and month based on the delivery status data, and creates delivery status data for all properties in the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered dwelling units / total number of dwelling units x 100, and registers this data in the data file 106c or displays it on the monitor 114.

The project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount/target amount of the project in the project goal master 106b x 100 for each project by year and month based on the delivery status data of all properties in the project, and registers the data in the data file 106c or displays it on the monitor 114.

The master maintenance section 102d is used to perform settings such as inputting, adding, changing, and updating data to the property room information master 106a and the project goal master 106b in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

The screen display control unit 102f controls the display of various screens (e.g., master maintenance screen, various input screens, various output screens, etc.) displayed on the monitor 114 and the acceptance of input.

3. Specific Examples
1 to 7, a specific example of the processing performed by control unit 102 of residence unit sales management device 100 in this embodiment will be described.

(3-1. Overall processing)
4 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment. With reference to FIG. 4, an outline of the overall processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment will be explained.

In FIG. 4, the master maintenance unit 102d executes a master maintenance process (step S1). Specifically, in the master maintenance process, the master maintenance unit 102d sets data in the property room information master 106a and the project goal master 106b in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

The contract processing unit 102a executes a contract information data registration process (step S2). Specifically, in the contract information data registration process, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, contract information data including a contract number, project, property name, dwelling unit number, application date, contract date, and scheduled delivery date is input and registered in the data file 106c.

The delivery status processing unit 102b executes the delivery status data creation process (step S3). Specifically, in the delivery status data creation process, the delivery status processing unit 102b aggregates the contract information data registered in the data file 106c by year and month for each property in the project, creates delivery status data including the number of delivered dwelling units whose delivery date is scheduled for the year and month, delivered dwelling units whose delivery has already been completed, undelivered dwelling units, and vacant dwelling units that are not under contract for the year and month, and the sales amount obtained by aggregating the sales prices of the delivered dwelling units by referring to the property room information master 106a, and registers the data in the data file 106c or displays it on the monitor 114.

In addition, in the delivery status data creation process, the delivery status processing unit 102b tally up all properties of the project by year and month based on the above delivery status data, creates delivery status data for all properties of the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered dwelling units / total number of dwelling units x 100, and registers the data in the data file 106c or displays it on the monitor 114.

The project-specific transition processing unit 102c executes a project-specific transition data creation process (step S4). Specifically, in the project-specific transition data creation process, the project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount/target amount of the project in the project goal master 106b x 100 for each year and month for each project based on the delivery status data of all properties in the project, and registers the data in the data file 106c or displays it on the monitor 114.

(3-2. Sample data)
5 to 7 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment. A specific example of the processing of the control unit 102 of the dwelling unit sales management device 100 in this embodiment will be explained with reference to FIG. 5 to FIG.

(S1: Master maintenance process)
The master maintenance unit 102d sets data in the property room information master 106a and the project goal master 106b in response to, for example, an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

Figure 5 (B) is a diagram showing an example of data in the property room information master 106a. In the example of the property room information master 106a shown in Figure 5 (B), the first line contains the property name "Property A", the room number "101", and the sales price "40,000,000". The sales price is read from the property room information master 106a using the property name and room number as keys.

Figure 7 (C) is a diagram showing an example of data in the project goal master 106b. In the example of the project goal master 106b shown in Figure 7 (C), the first line shows the project number "P001" and the target amount "200,000,000." The target amount is read from the project goal master 106b using the project number as a key.

(S2: Contract information data registration process)
The contract processing unit 102a inputs contract information data including the contract number, project number, property name, apartment number, application date, contract date, and scheduled delivery date, for example, in response to operator operations on an input screen (not shown) displayed on the monitor 114, and registers the data in a data file 106c.

(1) Register the contract information data.
Fig. 5 (A) is a diagram showing an example of contract information data. In Fig. 5 (A) , the first line of the contract information data example contains contract number "K001", project number "P001", property name "Property A", room number "101", application date "020/04/10", contract date "2020/04/21", and scheduled delivery date "2020/10/31". Here, an example for project number "P001" is shown, but contract information data for project numbers "P002" and "P003" are also registered.

(S3: Delivery status data creation process)
The delivery status processing unit 102b compiles the contract information data registered in the data file 106c by year and month for each property in the project, and creates delivery status data including the number of delivered dwelling units whose delivery date is scheduled as of that year and month, delivered dwelling units that have already been delivered, undelivered dwelling units, and vacant dwelling units that are not yet contracted as of that year and month, as well as the sales amount obtained by tallying up the sales prices of the delivered dwelling units by referring to the property room information master 106a, and registers this data in the data file 106c or displays it on the monitor 114.

Here, "delivered units" refer to units for which delivery has already been completed as of that year/month (not including deliveries in the current month). "Delivered units" are used to manage how many deliveries have occurred out of the total number of rooms. "Undelivered units" are used to manage units that have been contracted as of that year/month and are scheduled to be delivered in the future. "Vacant units" refer to units that have not yet been contracted as of that year/month. By registering this information at the time of contracting, it is possible to predict trends from the present to the future.

(2) Delivery status data is created based on the dates stored in the contract information data. Contract information data is compiled by year and month, and the number of contracts is obtained according to each condition from vacant units to delivered units. The sales amount is calculated only when the unit is delivered. In addition, the year and month are extracted from the minimum and maximum values of the target contract information data. The sales amount is calculated by obtaining the sales price from the property room information master 106a using the property name and room number as keys.

Figure 5 (C) shows an example of delivery status data, indicating the delivery status of property name "Property A" in project "P001". In the example of delivery status data in Figure 5 (C), for the year and month "2020/4", the number of delivered units is "0", the number of delivered units is "0", the number of undelivered units is "1", the subtotal is "7", the subtotal is "8", and the sales amount is "0". For the year and month "2020/4", the contract number "K001" in the contract information data was contracted in 2020/4 and is scheduled to be delivered in 2020/10, so at this point, the number of undelivered units is "1".

For the year and month "2020/5", the number of delivered units is "0", the number of delivered units is "0", the number of undelivered units is "2", the number of vacant units is "6", the subtotal is "8", and the sales amount is "0". For the year and month "2020/5", the contract information data's contract number "K002" was concluded in 2020/5 and is scheduled to be delivered in 2020/10, so at this point, the number of undelivered units is "2".

For the year and month "2020/8", the number of delivered units is "0", the number of delivered units is "0", the number of undelivered units is "3", the number of vacant units is "5", the subtotal is "8", and the sales amount is "0". For the year and month "2020/8", the contract number "K003" in the contract information data was concluded in 2020/8 and is scheduled to be delivered in 2020/11, so at this point, the number of undelivered units is "3".

For the year and month "2020/10", the number of delivered units is "0", the number of delivered units is "2", the number of undelivered units is "1", the number of vacant units is "5", the subtotal is "8", and the sales amount is "0". Since the contract information data contract numbers "K001, K002" are scheduled to be delivered in 2020/10, the number of delivered units is "2". The sales amount is the sales price "40,000,000" of the property name "Property A" and room number "101" of the contract information data contract number "K001" + the sales price "30,000,000" of the property name "Property A" and room number "102" of the contract information data contract number "K002" = "70,000,000".

For the year and month "2020/11", the following are the delivered units: "2", delivered units: "1", undelivered units: "0", vacant units: "5", subtotal: "8", and sales amount: "70,000,000". Contract number "K003" in the contract information data is scheduled for delivery in 2020/11, so the delivered units are set to "1", and the cumulative past delivered units are set as delivered units, so the delivered units are set to "2" (contract numbers "K001, K002").

Furthermore, the delivery status processing unit 102b tally up all properties in the project by year and month based on the delivery status data, and creates delivery status data for all properties in the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amounts up to the specified year and month, and delivery rate calculated by total delivered dwelling units / total number of dwelling units x 100, and registers this data in the data file 106c or displays it on the monitor 114.

(3) The delivery status data created in (2) is managed for each project, and delivery status data for all properties in the project is created. Figure 6 is a diagram showing an example of delivery status data for all properties in the project, and shows an example of the progress (based on number and amount) of all properties in project "P001". The example shown in Figure 6 includes items such as year and month, delivered units, sales amount, delivered units, cumulative sales amount, and delivery rate. The cumulative sales amount is the accumulated amount of sales amount up to the specified year and month. The delivery rate is calculated as follows: total delivered units / total number of units x 100.

Note that while an example for project number "P001" is shown here, delivery status data will also be created for project numbers "P002" and "P003."

(S4: Project-specific transition data creation process)
The project-specific transition processing unit 102c creates project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by dividing the cumulative sales amount by the target amount of the project in the project goal master 106b by 100, for each project and year, based on the delivery status data of all properties in the project, and registers the data in a data file 106c or displays it on the monitor 114.

(4) Based on the delivery status data for all properties of the project created in (3), project-specific transition data is created to manage on a project-by-project basis. In this case, a project goal master 106b is prepared in which a target amount is set for each project, making it possible to check the achievement rate. The achievement rate is calculated by: cumulative sales amount / target amount of the project in the project goal master 106b x 100.

Figure 7 (A) shows an example of contract information data, with examples of project numbers "P002, P003" also added. Figure 7 (B) shows an example of property room information master 106a. Figure 7 (C) shows an example of project goal master 106b.

Figure 7 (D) shows an example of progress data by project. In the example shown in Figure 7 (D), for project number "P001", in October 2020, the number of delivered units is "2", the cumulative sales amount is "70,000,000", the delivery rate is "25%", and the achievement rate is "35%". In November 2020, the number of delivered units is "3", the cumulative sales amount is "120,000,000", the delivery rate is "38%", and the achievement rate is "60%". In December 2020, the number of delivered units is "3", the cumulative sales amount is "120,000,000", the delivery rate is "38%", and the achievement rate is "60%".

For project number "P002", in October 2020, the number of delivered units is "1", the cumulative sales amount is "30,000,000", the delivery rate is "33%", and the achievement rate is "50%". In November 2020, the number of delivered units is "1", the cumulative sales amount is "30,000,000", the delivery rate is "33%", and the achievement rate is "50%". In December 2020, the number of delivered units is "1", the cumulative sales amount is "30,000,000", the delivery rate is "33%", and the achievement rate is "50%".

For project number "P003", in October 2020, the number of delivered units is "2", the cumulative sales amount is "80,000,000", the delivery rate is "50%", and the achievement rate is "50%". In November 2020, the number of delivered units is "3", the cumulative sales amount is "120,000,000", the delivery rate is "75%", and the achievement rate is "75%". In December 2020, the number of delivered units is "4", the cumulative sales amount is "160,000,000", the delivery rate is "100%", and the achievement rate is "100%".

More specific information can be provided by comprehensively checking and comparing the above-mentioned (2) delivery status data for each property in the project, (3) delivery status data for all properties in the project, and (4) trends in project-specific trend data.

For example, for project number "P002", there is no increase in the number of deliveries within the project. (2) The delivery status data for each property in project number "P002" and (3) the transition of the delivery status data for all properties in project "P002" make it possible to confirm the progress of each property, which can be used as information for policy decisions such as holding, renting, or selling. It is also possible to automatically pick up properties whose delivery rate has not reached 100%.

For project number "P003," both the number of deliveries and cumulative sales amount are increasing within the project. Comparing project information and progress can provide useful information for planning the next project.

As described above, according to this embodiment, the property room information master 106a registers the sales price of each dwelling unit number for each property, the contract processing unit 102a registers contract information data including the contract number, project, property name, dwelling unit number, application date, contract date, and scheduled delivery date, and the delivery status processing unit 102b aggregates the contract information data by year and month for each property in the project, and creates and outputs delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered at the time of the year and month, dwelling units that have already been delivered, dwelling units that have not been delivered, and vacant dwelling units that are not yet contracted at the time of the year and month, and the sales amount calculated by aggregating the sales prices of the dwelling units by referring to the property room information master 106a. Therefore, in the case of dwelling unit sales, a sales forecast (for example, based on the number of units and amount) linked to the scheduled delivery can be created, and the status and trends of sales of dwelling units, reservation contract status, and monthly sales progress can be grasped and analyzed from the start of the contract.

[4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

5. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

In addition, with regard to the residence sales management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the dwelling unit sales management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the dwelling unit sales management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the residence sales management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The residence sales management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The residence sales management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

REFERENCE SIGNS LIST 100 Residence unit sales management device 102 Control unit 102a Contract processing unit 102b Delivery status processing unit 102c Project-specific transition processing unit 102d Master maintenance unit 102e Screen display control unit 104 Communication interface unit 106 Storage unit 106a Property room information master 106b Project goal master 106c Data file 108 Input/output interface unit 112 Input device 114 Output device 300 Network

Claims (6)

A residence sales management device having a control unit,
The control unit is
The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered,
A contract processing means for registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date;
a delivery status data processing means for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount obtained by aggregating the sales prices of the dwelling units to be delivered by referring to the first master;
A residence sales management device comprising: The dwelling unit sales management device according to claim 1, characterized in that the delivery status data processing means creates and outputs delivery status data for all properties of the project, including the number of delivered dwelling units, sales amount, cumulative sales amount which is the accumulated amount of sales amount up to the specified year and month, and delivery rate calculated by total delivered dwelling units / total number of dwelling units x 100, by aggregating all properties of the project by year and month based on the delivery status data. The control unit is
The second master in which the target amount for each project is registered is accessible.
The dwelling unit sales management device as described in claim 2, characterized in that it is characterized by having a project-specific transition processing means for creating and outputting project-specific transition data including the number of delivered dwelling units, cumulative sales amount, delivery rate, and achievement rate calculated by cumulative sales amount / target amount of the project in the second master x 100, by project and by year and month, based on the delivery status data of all properties in the project. The dwelling unit sales management device according to any one of claims 1 to 3, characterized in that the dwelling unit includes an apartment or a detached house. A method for managing sales of a residence executed by an information processing device having a control unit,
The control unit is
The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered,
Executed in the control unit,
a contract processing step of registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date;
a delivery status data processing step for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount calculated by aggregating the sales prices of the dwelling units to be delivered by referring to the first master;
A method for managing the sale of a residence, comprising: A residence sales management program to be executed by an information processing device having a control unit,
The control unit is
The system is configured to be able to access a first master in which the sales price of each dwelling unit number for each property is registered,
In the control unit,
a contract processing step of registering contract information data including a contract number, a project, a property name, a dwelling unit number, an application date, a contract date, and a scheduled delivery date;
a delivery status data processing step for creating and outputting delivery status data including the number of dwelling units to be delivered that are scheduled to be delivered as of that year and month, dwelling units that have already been delivered, dwelling units that have not yet been delivered, and vacant dwelling units that are not under contract as of that year and month, and the sales amount calculated by aggregating the sales prices of the dwelling units to be delivered by referring to the first master;
A residential sales management program to implement the above.

Images