Computer programs, information processing devices, information processing systems, and information processing methods

Abstract

To provide a computer program, information processing device, information processing system, and information processing method that can reduce the workload of building designers. [Solution] The computer program obtains data including the address and use of the building to be designed, and extracts multiple ordinances related to the building's architectural design from an ordinance database that records ordinances, including multiple tag items that identify the content of the ordinances, classified into two categories: a parent category and child categories belonging to the parent category, based on the acquired data. The computer then performs a process to classify the extracted ordinances according to their importance in each of the two categories.

Description

Technical Field

[0001] The present invention relates to a computer program, an information processing apparatus, an information processing system, and an information processing method.

Background Art

[0002] BIM (Building Information Modeling) provides a workflow for utilizing a database of buildings in which attribute information such as cost, finish, and management information is added to a three-dimensional digital model of a building created on a computer in various processes from architectural design to construction and maintenance management.

[0003] Patent Document 1 discloses a system for efficiently managing information on members related to construction generated by BIM.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In order to utilize BIM, it is necessary to handle a large amount of geometric shape information. On the other hand, in carrying out the design and construction of a building, it is necessary to confirm which regulations apply from among many regulations related to the building. In addition, since various information is described in the regulations, there are many things that the building designer should confirm, and the content of the regulations also varies depending on the use and location of the building. Therefore, it is desired to reduce the workload of the building designer.

[0006] The present invention has been made in view of such circumstances, and an object thereof is to provide a computer program, an information processing apparatus, an information processing system, and an information processing method capable of reducing the workload of a building designer. [Means for solving the problem]

[0007] The present invention includes several means for solving the above-mentioned problems, but to give one example, the computer program acquires data including the address and use of the building to be designed, and from an ordinance database that records ordinances, which include multiple tag items that identify the content of the ordinance, classified into two categories: a parent category and child categories belonging to the parent category, it extracts multiple ordinances related to the architectural design of the building based on the acquired data, and the computer executes a process to classify the extracted multiple ordinances according to the importance of each of the two categories. [Effects of the Invention]

[0008] According to this invention, the workload of building designers can be reduced. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the configuration of the information processing device according to this embodiment. [Figure 2] This diagram shows an example of the structure of a regulations database. [Figure 3] This is a diagram showing an example of a database of ordinances. [Figure 4] This figure shows an example of the importance levels of parent and child categories. [Figure 5] This figure shows an example of the classification results of the ordinance. [Figure 6] This figure shows an example of the display order of information included in the deadline tag when urgency is selected. [Figure 7] This diagram shows an example of how the ordinance is displayed when urgency is selected. [Figure 8] This figure shows an example of how to enter a deadline in addition to the urgency level. [Figure 9] This diagram shows an example of how the ordinance is displayed when urgency and deadline are selected. [Figure 10] This figure shows an example of the process that is executed when the number of accesses is selected. [Figure 11] This is a diagram showing an example of the display of regulations when the number of accesses is selected. [Figure 12] This is a diagram showing an example of the process when the total points are selected. [Figure 13] This is a diagram showing an example of the display of regulations when the number of points is selected. [Figure 14] This is a diagram showing an example of the load level. [Figure 15] This is a diagram showing an example of the display when the load level is selected. [Figure 16] This is a diagram showing an example of the extraction items. [Figure 17] This is a diagram showing the process when filtering by "application conditions". [Figure 18] An example of the display when filtering by "application conditions" is shown. [Figure 19] This is a diagram showing the process when filtering by "designer's task". [Figure 20] An example of the display when filtering by "designer's task" is shown. [Figure 21] This is a diagram showing the process when filtering by "deadline". [Figure 22] An example of the display when filtering by "deadline" is shown. [Figure 23] This is a diagram showing an example of the input information for generating a process table. [Figure 24] This is a diagram showing an example of a process table. [Figure 25] This is a diagram showing an example of the condition setting when generating a birdcage diagram. [Figure 26] This is a diagram showing an example of a parent category database. [Figure 27] This is a diagram showing an example of a child category database. [Figure 28] This is a diagram showing an example of the steps for generating a regulation DB. [Figure 29] This is a diagram showing an example of the configuration of the information processing system of this embodiment. [Figure 30] This is a diagram showing an example of the configuration of the server. [Figure 31] This is a diagram showing an example of the configuration of a terminal device. [Figure 32] This figure shows an example of parameter information. [Figure 33] This figure shows an example of determining compliance with an ordinance using parameter information. [Figure 34] This figure shows an example of the processing procedure for classifying and displaying ordinances using an information processing device. [Figure 35] This figure shows an example of the procedure for generating a database of ordinances using an information processing device. [Modes for carrying out the invention]

[0010] Embodiments of the present invention will be described below with reference to the drawings. Figure 1 is a diagram showing an example of the configuration of the information processing device 50 of this embodiment. The information processing device 50 comprises a control unit 51 that controls the entire device, a communication unit 52, a memory 53, a display unit 54, an operation unit 55, a storage unit 56, and an interface unit 58. The information processing device 50 can be configured as, for example, a computer such as a server.

[0011] The control unit 51 may be configured by incorporating a required number of CPUs (Central Processing Units), MPUs (Micro-Processing Units), GPUs (Graphics Processing Units), etc. Alternatively, the control unit 51 may be configured by combining DSPs (Digital Signal Processors), FPGAs (Field-Programmable Gate Arrays), etc.

[0012] The communication unit 52 is equipped with a communication module and can communicate with external devices.

[0013] The display unit 54 can be made of a liquid crystal panel or an organic EL (Electro-Luminescence) display, etc. An external display device may be provided instead of the display unit 54.

[0014] The operation unit 55 consists of a touch panel or the like, and allows for the operation of icons displayed on the display unit 54, cursor movement and manipulation, and input of text, etc. The operation unit 55 may also be a mouse or keyboard.

[0015] The storage unit 56 can be made up of semiconductor memory or a hard disk, and stores a computer program 57 (program product) and necessary information.

[0016] The computer program 57 can be read by a recording medium (e.g., an optically readable disc storage medium such as a CD-ROM) M using a recording medium reading unit (not shown) and stored in a storage unit 56. The computer program 57 may also be read by a recording medium such as a storage device (semiconductor memory such as an SSD (Solid State Drive)) connected by a standard for connecting to a computer (e.g., USB (Universal Serial Bus) or other standards) and stored in a storage unit 56. Alternatively, the computer program 57 may be downloaded from an external device via a communication unit 52 and stored in a storage unit 56.

[0017] The memory 53 can be composed of semiconductor memory such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), or flash memory. The computer program 57 is loaded into the memory 53, and the control unit 51 can execute the computer program 57. The control unit 51 can execute the processing defined in the computer program 57. In other words, the processing performed by the control unit 51 is also the processing performed by the computer program 57.

[0018] The interface unit 58 provides an interface function to the ordinance database 60. The control unit 51 can access the ordinance database 60 via the interface unit 58 and can write information to and read information from the ordinance database 60.

[0019] The information processing device 50 can provide functions such as classifying and displaying the contents of ordinances that designers want to check according to their importance, classifying and displaying the contents of ordinances according to their urgency, classifying and displaying ordinances according to the number of accesses, total points, load (workload of designers), etc., extracting items required by designers, creating schedules, and generating birdcage diagrams. Details of each function will be described later.

[0020] Figure 2 shows an example of the structure of the Ordinance DB60. The Ordinance DB60 classifies and records ordinances, which include multiple tag items that identify the content of the ordinance, into two categories: a parent category and child categories belonging to the parent category. As shown in Figure 2, the parent categories are A, B, C, ... The child categories belonging to parent category A are a1, a2, a3, a4, and the child categories belonging to parent category B are b1, b2. Other parent categories also have corresponding child categories.

[0021] An ordinance whose parent category is A and whose child category corresponds to a1 is represented as Aa1. The tag items w1, w2, w3, w4, w5, w6, ... of ordinance Aa1 are represented as aw11, aw12, aw13, aw14, aw15, aw16, ... respectively. Tag items include, for example, "Name of the ordinance," "Applicable conditions," "Designer's tasks," "Deadline," and "References."

[0022] An ordinance whose parent category is A and whose child category corresponds to a2 will be represented as Aa2. The tag items w1, w2, w3, w4, w5, w6, ... of ordinance Aa2 will be represented as aw21, aw22, aw23, aw24, aw25, aw26, ... respectively. The same applies to other child categories of parent category A.

[0023] An ordinance whose parent category is B and whose child category corresponds to b1 is denoted as Bb1. The tag items w1, w2, w3, w4, w5, w6, ... of ordinance Bb1 are denoted as bw11, bw12, bw13, bw14, bw15, bw16, ... respectively. The same applies to other child categories of parent category B.

[0024] Figure 3 shows an example of the ordinance DB60. In Figure 3, parent category A is "Use, Scale, and Planning," and the subcategories belonging to parent category A are "Ordinances by Use," "Ordinances by Use," "Parking, Bicycle Parking, and Motorcycle Parking," "Parking, Bicycle Parking, and Motorcycle Parking," and "Ordinances for Sloping Land." Parent category B is "Ordinance Procedures," and the subcategories belonging to parent category B are "Mid-to-High-Rise Buildings," "Mid-to-High-Rise Buildings," "Greening," "Landscape," "Waste Management," "Public Safety (Police Consultation)," "Embankment Regulation Law," and "Buried Cultural Properties." Note that the parent and subcategories are not limited to the example in Figure 3 and may include other types.

[0025] The name of an ordinance whose parent category is "Purpose, Scale, and Plan" and whose child category is "Ordinances by Purpose" is, for example, "Arakawa Ward Ordinance Concerning the Improvement of the Living Environment Related to the Construction of Housing, etc." and the tag items "Applicable Conditions," "Designer's Tasks," "Deadline," and "References" contain their respective contents. Note that while Ordinance DB60 shown in Figure 3 illustrates ordinances related to Arakawa Ward, Ordinance DB60 is not limited to Arakawa Ward and could be an ordinance database of other wards or cities. If it is an ordinance database of another ward or city, then the ordinances of that ward or city will be included.

[0026] Next, we will explain how to classify the regulations required by designers based on Regulation DB60.

[0027] Figure 4 shows an example of the importance levels of parent and child categories. The importance levels of parent and child categories can be pre-set considering factors such as the readability of the classified regulations. For example, the importance level may also be related to the order in which the pre-set parent or child categories are displayed. In other words, the importance level may simply be based on the order in which they are displayed. In the example in Figure 4, the importance levels of the parent categories are such that "Building Standards" is the most important, followed by "Urban Development," "District Designation," "Use, Scale, and Planning," "Regulations and Procedures," and "Infrastructure Procedures," in decreasing order.

[0028] Among the subcategories belonging to the parent category "Building Standards," the importance of "Specific Administrative Agency" is highest, followed by "Building Standards Ordinance," "Building Standards Ordinance Regulations," and "Handling," in that order.

[0029] Furthermore, among the subcategories belonging to the parent category "Urban Development," the importance of "Certification under Articles 29 and 60 of the Design Act, and Outline Consultation" is the highest, followed by "Urban Facilities" and then "Land Readjustment Projects," in descending order. The same applies to other categories. Note that the content and importance of the categories are examples only and are not limited to the example in Figure 4. For example, importance may be related to the size in which a pre-set parent or child category is displayed. In this case, information with high importance among the subcategories belonging to the parent category may be displayed larger, and information with low importance may be displayed smaller.

[0030] The control unit 51 acquires data including the address and use of the building to be designed. By acquiring data including the building's address and use, the control unit 51 can narrow down the regulations related to the building to be designed. Based on the acquired data, the control unit 51 extracts multiple regulations related to the building's architectural design from the regulations DB 60, which records regulations that include multiple tag items that identify the content of the regulations, classified into two categories: a parent category and child categories belonging to the parent category. The control unit 51 can classify the extracted multiple regulations according to the importance of each of the two categories: the parent category and the child categories belonging to the parent category.

[0031] Ordinances contain a variety of information, and what designers want to check varies depending on the situation. For example, from a process perspective, there are submission deadlines, and from a building shape perspective, there are things that affect the building's exterior shape and room sizes, all of which are combined in a complex way. For this reason, a single-axis classification is insufficient for designers; a two-axis classification system with parent categories and child categories belonging to those parent categories allows for a multifaceted review of the ordinances. For example, it becomes possible to identify items that need to be submitted urgently and that may have a significant impact on the direction of the plan. Furthermore, by setting importance levels based on experience and data, it becomes possible to organize information in a way that is more relevant to practical design work. By classifying and structuring the necessary information using the importance levels of two categories, design efficiency can be improved and the workload of building designers can be reduced.

[0032] Figure 5 shows an example of the classification results of the ordinance. As shown in Figure 5, the control unit 51 arranges the parent categories in order of importance, and for each arranged parent category, the child categories belonging to that parent category are arranged in order of importance. For example, as shown in Figure 5, the parent categories are arranged in the order of importance 1, 2, and 3, with parent categories I1, I2, and I3. The child categories belonging to parent category I1 are arranged in the order of importance 1, 2, and 3, with child categories i1, i2, and i3, and the child categories belonging to parent category I2 are arranged in the order of importance 1, 2, and i4, i5.

[0033] The control unit 51 can classify and display ordinances in association with each of the placed subcategories. For example, as shown in Figure 5, ordinances are classified and displayed in association with subcategories i1, i2, i3, i4, and i5.

[0034] This allows for the classification and display of necessary regulations based on their importance in two categories, thereby improving design efficiency and reducing the workload of building designers.

[0035] In the example in Figure 5, one ordinance is shown corresponding to one subcategory, but this is not limited to this. For example, one subcategory may correspond to multiple ordinances. For instance, if three ordinances correspond to subcategory i1, in Figure 5, subcategory i1 can be displayed across three rows, with one ordinance corresponding to each subcategory i1, thus allowing multiple ordinances to be associated with one subcategory.

[0036] The "Ordinance Classification Results" screen in Figure 5 displays the following icons: "Urgency" icon 101, "Number of Accesses" icon 102, "Total Points" icon 103, "Load Level" icon 104, "Extraction Items" icon 105, "Project Schedule" icon 106, and "Birdcage Diagram" icon 107. The following describes the process when each icon is operated.

[0037] First, let's explain the "Urgency" icon 101. By manipulating the "Urgency" icon 101, you can change the classification and display method of ordinances according to their urgency, thereby increasing the number of display options when classifying and displaying ordinances. Urgency is information related to the order and size in which ordinances are displayed, which are set based on information such as the deadline and timing of procedures.

[0038] Figure 6 shows an example of the display order of information included in deadline tags when urgency is selected. As shown in Figure 6, the information included in the "deadline tags" of the ordinance is pre-configured to be displayed in order from the most urgent to the most urgent. In the example in Figure 6, among the information included in the deadline tags, "Multiple Steps" has the highest urgency and is displayed at the top. Following that, the urgency decreases in the following order: "XX days before sign installation," "XX days before confirmation application acceptance," "before confirmation application," "30 days before commencement of construction," "before commencement of construction," "after commencement of construction," and "requires confirmation." Note that the order of urgency is not limited to the example in Figure 6.

[0039] Figure 7 shows an example of how regulations are displayed when urgency is selected. As shown in Figure 7, the control unit 51 can arrange laws and regulations that do not have a deadline in the following order of importance: "Multiple steps required", "XX days before sign installation", "XX days before confirmation application acceptance", "Before confirmation application", "30 days before commencement of construction", "Before commencement of construction", "After commencement of construction", and "Requires confirmation".

[0040] As described above, when the control unit 51 receives an instruction to classify ordinances according to their urgency, it can classify and display the ordinances in order of the urgency of the multiple pieces of information (application procedure deadline information) included in the deadline tag (application procedure deadline item) among the multiple tag items.

[0041] In this way, if "urgency" is selected and no deadline is entered, ordinances and regulations can be sorted and displayed according to the pre-set urgency level. Alternatively, when displaying ordinances and regulations, they can be displayed in order of importance for each piece of information included in the deadline tag.

[0042] Figure 8 shows an example of entering a deadline in addition to the urgency level. In the example in Figure 8, the designer selects the "urgency level" and enters the deadline for the procedure. Examples of deadlines include the date the application for confirmation was received, the date construction began, and the date the sign was installed.

[0043] Figure 9 shows an example of how ordinances are displayed when urgency and deadlines are selected. As shown in Figure 9, when a deadline is entered, the display items "Deadline Determined" and "Deadline Completed" are displayed outside the display frame exemplified in Figure 7, from highest to lowest. The "Deadline Determined" column displays the laws and regulations / ordinances for which deadlines have been entered. In this case, the display order of ordinances, etc., can be set to the earliest deadline (or the one with the closest deadline). If there are multiple ordinances with the same deadline, these multiple ordinances may be displayed in order of importance by category. The "Deadline Completed" column displays laws and regulations / ordinances whose deadlines have passed.

[0044] As described above, when the control unit 51 receives input for a deadline (application procedure deadline item) from among multiple tag items, it can classify and display ordinances that are before the deadline (before the application procedure deadline) in order of the remaining days until the application procedure deadline, and can also classify and display ordinances that have passed their deadline (after the application procedure deadline).

[0045] This allows designers to easily check which ordinances are due soon and which have already expired, simply by entering the deadline. They don't need to check each ordinance individually, but can check both upcoming and expired ordinances at once, reducing the workload for designers.

[0046] Next, we will explain what happens when you manipulate the "Access Count" icon 102.

[0047] Figure 10 shows an example of processing when the number of accesses is selected. The control unit 51 pre-calculates the number of accesses for each ordinance over a predetermined period. The predetermined period can be determined as appropriate, for example, one week, one month, three months, six months, etc. The number of accesses can be the number of accesses to the "reference source" tag among the tag items of each ordinance. When a designer investigates matters related to an ordinance, they can refer to the reference source information to deepen their understanding of the ordinance's content. In other words, it can be assumed that the more accesses there are, the higher the likelihood that the designer will be able to access useful information.

[0048] In the example in Figure 10, ordinances can be divided into those with exceptionally high access, i.e., ordinances where the number of accesses over a specified period exceeds a predetermined first threshold, and ordinances with no access, i.e., ordinances where the number of accesses over a specified period does not exceed a predetermined second threshold (<first threshold).

[0049] Figure 11 shows an example of how ordinances are displayed when the number of accesses is selected. As shown in Figure 11, the top of the display column shows the laws and regulations that are frequently accessed. In other words, the top column lists ordinances whose referral source access count exceeds the first threshold. Also, the bottom of the display column shows laws and regulations that have not been accessed for more than a week, for example. In other words, the bottom column lists ordinances whose referral source access count does not exceed the second threshold.

[0050] In the display area between the top-level and bottom-level fields, for example, parent categories could be arranged in order of importance, and the ordinances included in each parent category could be displayed in order of the number of accesses from the referring source. Although not shown in the diagram, child categories belonging to parent categories could also be arranged in order of importance, and the ordinances included in each child category could be displayed in order of the number of accesses from the referring source.

[0051] Regarding the number of accesses to the referring source, they may be displayed in order of access count by ordinance, as shown in the example in the top column, or they may be displayed in order of access count by parent category or child category.

[0052] As described above, the control unit 51 can classify and display ordinances based on the aggregated number of accesses. This allows designers to easily access useful ordinances from among many.

[0053] The control unit 51 may classify and display the ordinances included in each parent category by the number of accesses. Alternatively, the control unit 51 may classify and display the ordinances included in each child category by the number of accesses. This allows designers to access appropriate ordinances, taking into account both the importance of the category and the number of accesses.

[0054] Next, we will explain what happens when you operate the "Total Points" icon 103.

[0055] Figure 12 shows an example of the process when selecting the overall point system. As shown in Figure 12, the overall point system is calculated by assigning points to the number of accesses to the referral source, the percentage of projects with short deadlines (urgent percentage), and the percentage of projects that are considered mandatory (mandatory percentage). For example, if N is the number of accesses to past projects for each subcategory, E is the urgent percentage, and A is the mandatory percentage, then the overall point system G can be calculated using the formula G = α1 × N + α2 × E + α3 × A. α1, α2, and α3 are weighting coefficients that can be set in advance. The overall point system can be calculated for each subcategory.

[0056] In the example in Figure 12, overall points are calculated for each subcategory, such as "Usage-Specific Ordinances," "Parking / Bicycle Parking," "Mid-to-High-Rise Buildings," and "Port Areas." In the example in Figure 12, it is possible to distinguish between ordinances with high overall point scores and those with low overall point scores.

[0057] Figure 13 shows an example of how ordinances are displayed when a point system is selected. As shown in Figure 13, the top of the display column shows laws and regulations that are likely to be of high importance based on past history. In other words, the top column is filled with ordinances with high total points. Conversely, the bottom of the display column shows laws and regulations that are likely to be of low importance based on past history. In other words, the bottom column is filled with ordinances with low total points.

[0058] In the display area between the top-level and bottom-level sections, for example, parent categories may be arranged in order of importance, and the ordinances included in each parent category may be displayed in order of total points. Alternatively, although not shown in the diagram, child categories belonging to parent categories may be arranged in order of importance, and the ordinances included in each child category may be displayed in order of total points.

[0059] As described above, the control unit 51 calculates points for each subcategory by multiplying a weight coefficient by the percentage of tag items for which the application of the application condition item is mandatory (mandatory application percentage), the percentage of tag items for which the application procedure deadline is set to a short period (urgent percentage), and the number of accesses of the referencing item among the tag items. The control unit 51 can then display the ordinances included in the subcategory classified according to the calculated points.

[0060] This allows for the display of ordinances of high and low importance based on past history, enabling designers to identify important ordinances from among many.

[0061] Next, we will explain what happens when you manipulate the "Load Level" icon 104.

[0062] Figure 14 shows an example of workload. The workload is information related to the order and size in which pre-set regulations are displayed, and is an indicator of how much effort is required in the designer's work. For example, the higher the workload, the more effort is required. As shown in Figure 14, among the tasks defined as designer tasks, the one with the highest workload is "permission," followed by "neighborhood explanation," "sign installation," "notification," "prior consultation procedure," "necessity determination," "certification," and "confirmation," in decreasing order of workload. Note that the order of workload and the examples of tasks are not limited to the example in Figure 14.

[0063] Figure 15 shows an example of the display when load level is selected. As shown in Figure 15, the parent categories are arranged in order of importance, and the ordinances included in each parent category are displayed in order of highest load level. In this case, ordinances that are "required" for application are included.

[0064] As described above, the designer's workload is defined for each of the multiple tasks included in the designer's task item among the multiple tag items. The control unit 51 can then identify the workload for each of the multiple regulations included in the parent category according to the tasks included in the task item, and classify and display the regulations according to the identified workload.

[0065] This allows designers to easily identify the time-consuming tasks within the design process.

[0066] Next, we will explain what happens when you operate the "Extract Items" icon 105.

[0067] Figure 16 shows an example of extraction items. The extraction items include items of interest to the designer from ordinances narrowed down by the building's address and purpose. The control unit 51 provides a filtering function for extracting items of interest. As shown in Figure 16, the extraction items include, for example, "applicable conditions," "designer's tasks," and "deadlines." "Applicable conditions" includes display items such as "purpose," "building size," "site size," "construction location," "plan," and "requires confirmation," and multiple display items can be set. "Designer's tasks" includes display items such as "notification," "permission," "certification," "necessity determination," "sign installation," "neighbor explanation," "prior consultation procedure," and "requires confirmation," and multiple display items can be set. "Deadlines" includes display items such as "30 days before commencement of construction," "before commencement of construction," "before confirmation application," "XX days before confirmation application acceptance," "XX days before sign installation," "after commencement of construction," "multiple steps," and "requires confirmation," and one display item can be set.

[0068] Figure 17 shows the process when filtering by "Applicable Conditions," and Figure 18 shows an example of the display when filtering by "Applicable Conditions." As shown in Figure 17, the designer can input or select "Applicable Conditions" to extract the items recorded in the "Applicable Conditions" tag of each ordinance ("Usage," "Building Size," "Site Size," "Construction Location," "Plan," or "Confirmation Required").

[0069] As shown in Figure 18, when the items recorded under the "Applicable Conditions" tag of each ordinance are extracted, the necessary information recorded in relation to each display item, such as "Site Size," "Construction Location," "Usage," "Building Size," "Plan," and "Confirmation Required," can be extracted. For example, for "Site Size" and "Construction Location," the applicability is determined by the site size and construction location of the planned building, and essential items for designers to understand the site's potential in volume analysis can be extracted. This makes it possible to generate accurate birdcage diagrams.

[0070] Furthermore, the applicability of "purpose," "building size," and "planning" is determined based on the purpose, size, and plan of the planned building, allowing designers to identify considerations when planning the building. This clarifies key points at the planning stage and enables early identification of necessary design conditions and constraints.

[0071] Figure 19 shows the process when filtering by "Designer's Tasks," and Figure 20 shows an example of the display when filtering by "Designer's Tasks." As shown in Figure 19, by inputting or selecting "Designer's Tasks," designers can extract items recorded in the "Designer's Tasks" tag of each ordinance ("Notification," "Permission," "Certification," "Necessity Determination," "Sign Installation," "Neighbor Explanation," "Prior Consultation Procedure," or "Confirmation Required").

[0072] As shown in Figure 20, when the items recorded under the "Designer's Tasks" tag for each ordinance are extracted, the necessary information recorded in association with each display item, such as "Notification," "Permit," "Certification," "Necessity Determination," "Sign Installation," "Neighbor Explanation," "Prior Consultation Procedure," and "Confirmation Required," can be extracted. For example, for each display item, such as "Neighbor Explanation," "Sign Installation," "Prior Consultation Procedure," "Notification," and "Permit," the designer's mandatory tasks can be displayed. Furthermore, for "Confirmation Required," tasks that may become mandatory after confirmation can be displayed, and for "Certification," tasks that may become tasks of businesses other than the designer (for example, the client) can be displayed.

[0073] Figure 21 shows the process when filtering by "deadline," and Figure 22 shows an example of the display when filtering by "deadline." As shown in Figure 21, the designer can input or select a "deadline" to extract the items recorded in the "deadline" tag of each ordinance ("30 days before commencement of construction," "before commencement of construction," "before application for confirmation," "XX days before application for confirmation was received," "XX days before sign installation," "after commencement of construction," "multiple steps," or "requires confirmation").

[0074] As shown in Figure 22, when the items recorded under the "deadline" tag of each ordinance are extracted, the necessary information recorded in association with each display item, such as "before confirmation application," "XX days before confirmation application acceptance," "30 days before commencement of construction," "before commencement of construction," "after commencement of construction," "XX days before sign installation," "multiple steps," and "requires confirmation," can be extracted. For example, for the display items "before confirmation application" and "XX days before confirmation application acceptance," it is possible to extract and display legal regulations and ordinances for which deadlines are set based on the confirmation application acceptance date. This makes it possible to use it as a database for a function that automatically generates a construction schedule by setting the confirmation application acceptance date.

[0075] Furthermore, the display items for "30 days before construction," "before construction," and "after construction begins" can extract and display legal regulations and ordinances that have deadlines based on the construction start date. This allows it to be used as a database for a function that automatically generates a construction schedule by setting the construction start date.

[0076] Furthermore, for the display items "XX days before sign installation" and "multiple steps," it is possible to extract and display legal regulations and ordinances that have multiple steps for the sign installation date or deadline. This clarifies the tasks that designers need to pay attention to.

[0077] As described above, extraction items corresponding to the required items among multiple tag items are predetermined. When the control unit 51 receives input for the required items, it can display information including regulations related to the extraction items corresponding to the received required items. The information including regulations includes, for example, information such as required items, considerations, and tasks. In addition, the required items may include at least one of the following: application conditions, designer's tasks, and deadlines (application procedure deadlines).

[0078] In the display examples illustrated in Figure 18 or Figure 20, when displaying required items, considerations, or tasks, they may be displayed in order of deadline based on the deadlines associated with those required items, considerations, or tasks. Also, in the display example illustrated in Figure 22, when displaying laws and regulations, the man-hours required for those laws and regulations may be identified and displayed, for example, in order of the amount of man-hours required.

[0079] As illustrated in Figures 17, 19, and 21, for each narrowed-down ordinance, a database can be created in advance that associates each ordinance with the information for "Application Conditions," "Designer's Tasks," and "Deadline." Specifically, the information for "Application Conditions," "Designer's Tasks," and "Deadline" can be recorded in association with the identifier (ID) of each ordinance.

[0080] Next, we will explain what happens when you operate the "Project Schedule" icon 106.

[0081] Figure 23 shows an example of input information for generating a construction schedule. As shown in Figure 23, the input screen displays fields for entering or selecting the planned date for receiving the confirmation application and the planned start date of construction as reference dates. The designer can set reference dates for deadlines for regulations narrowed down by the building's address and use. The planned date for installing signs may also be included in the reference date setting.

[0082] The control unit 51 accepts input for setting the reference date for the application procedure deadline and can generate a schedule that displays the designer's task schedule in a time chart for each of the pre-selected ordinances relative to the accepted reference date.

[0083] Furthermore, the control unit 51 may identify a reference date for the application procedure deadline for each ordinance classified based on the building's address and use, and accept input for setting the identified reference date. This allows the information processing device 50 to request the designer to input the setting of the reference date determined according to the ordinance. In other words, the reference date may be identified in accordance with the ordinance, and the designer may be asked to set the identified reference date. This eliminates the need for the designer to determine which scheduled date needs to be entered for setting the reference date, and the designer only needs to input the reference date requested by the information processing device 50 for each ordinance.

[0084] Figure 24 shows an example of a project schedule. As shown in Figure 24, the project schedule is a time chart with a time axis on the horizontal axis, and the reference dates entered by the designer (for example, the scheduled date for receiving the confirmation application and the scheduled date for starting construction) are set as points on the time chart. Then, for each applicable regulation, the deadline for the designer's tasks is set as a point on the time chart. In the example in Figure 24, the designer's tasks 1, 2, and 3 are displayed for regulations 1, 2, and 3.

[0085] If, for example, the confirmation application submission date is 30 days prior to the scheduled date, the designer's task will be displayed on the time chart as being 30 days prior to the scheduled confirmation application submission date. This makes it easy to see by when each procedure related to the relevant regulations must be completed in relation to the deadline reference date.

[0086] Suppose, after the construction schedule has been generated, a meeting is held with relevant parties, including the designer, and it is decided, for example, to postpone the start date of construction. The control unit 51 may obtain the minutes of the meeting, perform language processing on the obtained minutes to identify the change in the construction start date, and update the construction schedule based on the identified construction start date.

[0087] Next, we will explain what happens when you operate the "birdcage diagram" icon 107.

[0088] A birdcage diagram is a three-dimensional representation of the area that a building must not exceed. Conditions for generating a birdcage diagram include, for example, regulations concerning setback lines, reverse shadows, reverse sky ratio, and setback distances. Setback lines are stipulated in the Building Standards Act and limit the height of each part of a building according to the distance from the road boundary or adjacent property boundary, thereby ensuring sunlight and ventilation for roads and adjacent properties and reducing the feeling of oppression. Reverse shadows are stipulated in the Building Standards Act and are regulations to prevent shadows from being cast on adjacent blocks for a certain period of time or longer. Reverse sky ratio is stipulated in the Building Standards Act and regulates the ratio of the area of ​​the sky to the total sky when viewing a building from a certain position, based on the ratio of the building to the sky. Setback distances are stipulated by municipal ordinances and regulate the distance from the adjacent property boundary to each part of a building.

[0089] To generate a birdcage diagram, software for constructing 3D building data can be used, such as a BIM CAD system.

[0090] As described above, the control unit 51 can generate a birdcage diagram based on at least one of the setback regulations, inverse shadow and inverse sky ratio, as well as regulations on setback distances based on ordinances classified on the building's address and use.

[0091] Figure 25 shows an example of the conditions for generating a birdcage diagram. As shown in Figure 25, further conditions for generating a birdcage diagram include regulations concerning Category 2 roads and self-managed sidewalks. Roads under the Building Standards Act are, in principle, required to be at least 4 meters wide. Category 2 roads are roads less than 4 meters wide that have been given relief measures through designation by a specific administrative agency.

[0092] When constructing a building on a site facing a road under Article 2 of the Land Use Act, a birdcage diagram can be generated after confirming with the local government office whether to adopt one of two methods: reducing the size of the site to secure a width of 4m (a pattern where the site becomes smaller) or narrowing the land on the opposite side of the road from the site (a pattern that does not affect the site).

[0093] The regulation regarding self-managed sidewalks states that if there is no sidewalk of 2.0m or more in width on the road adjacent to the project site, a sidewalk of 2.0m or more in width must be secured. If a specific ordinance contains regulations regarding self-managed sidewalks, a birdcage diagram can be generated taking those regulations into consideration.

[0094] When generating a birdcage diagram based on multiple regulations, the birdcage diagram based on the narrowest 3D shape among those based on each regulation can be used.

[0095] As described above, the control unit 51 can generate a birdcage diagram based on regulations concerning Category 2 roads or self-managed sidewalks based on ordinances. This allows the birdcage diagram to be generated while reflecting the regulations based on ordinances, thereby improving the accuracy of the birdcage diagram.

[0096] Next, we will explain how to generate the ordinance DB60.

[0097] Ordinance DB60 records ordinances that include multiple tag items that identify the content of the ordinance, classifying them into two categories: a parent category and child categories belonging to the parent category. Therefore, in order to generate Ordinance DB60, a parent category database is prepared to identify the ordinances included in the parent category, and a child category database is prepared to identify the ordinances included in the child category.

[0098] Figure 26 shows an example of a parent category database. The parent category database records words associated with each parent category, as well as vectors of those words. For example, as shown in Figure 26, parent category P1 has the words wp11, wp12, wp13, ... associated with it, as well as the vectors vp11, vp12, vp13, ... associated with the words wp11, wp12, wp13, ....

[0099] Furthermore, the parent category P2 has associated words such as wp21, wp22, wp23, ..., as well as associated vectors vp21, vp22, vp23, ... for the associated words wp21, wp22, wp23, ....

[0100] Figure 27 shows an example of a subcategory database. The subcategory database records each subcategory, associating it with words related to that subcategory and vectors of those related words. For example, as shown in Figure 27, subcategory C1 has the words wc11, wc12, wc13, ... associated with it, as well as the vectors vc11, vc12, vc13, ... associated with the related words wc11, wc12, wc13, ....

[0101] Furthermore, subcategory C2 has associated words such as wc21, wc22, wc23, ..., as well as associated vectors vc21, vc22, vc23, ... for the related words wc21, wc22, wc23, ....

[0102] Figure 28 shows an example of the steps for generating the ordinance database 60. The control unit 51 obtains the ordinance document. The ordinance document includes the name of the ordinance and the text of the ordinance. When a user (person in charge) creates the ordinance database 60, they enter a URL on the web, and the control unit 51 obtains the entered URL and sends the URL to an external website, allowing the ordinance document to be obtained from the external website.

[0103] The control unit 51 performs morphological analysis on the acquired ordinance document to extract words from the ordinance document. The words may include words related to multiple tag items that identify the content of the ordinance.

[0104] The control unit 51 performs vectorization processing on the extracted words and calculates a vector for each extracted word.

[0105] The control unit 51 calculates the similarity between the vector values ​​of each word extracted from the ordinance document and the vector values ​​of the words recorded in the parent category database and the child category database, respectively. For calculating the similarity, for example, cosine similarity can be used.

[0106] The control unit 51 calculates the probability of a parent category and the probability of a child category based on the calculated similarity, and identifies the category with the highest probability as the parent category and the child category. For example, let the vectors of words extracted from the ordinance document be x1, x2, x3, x4, ... and the probability that the ordinance document is a parent category P1, P2, P3, ... is R1, R2, R3, ... based on the similarity between the vector values ​​of the words and the vector values ​​of the words recorded in the parent category database. If the highest probability among the probabilities R1, R2, R3, ... is R2, then the parent category corresponding to the ordinance document can be identified as P2. Similarly, let the vectors of words extracted from the ordinance document be x1, x2, x3, x4, ... and the probability that the ordinance document is a child category C1, C2, C3, ... is r1, r2, r3, ... based on the similarity between the vector values ​​of the words and the vector values ​​of the words recorded in the child category database. If we assume that r3 is the highest degree of certainty among the degrees r1, r2, r3, ..., then we can identify that the subcategory corresponding to the ordinance document is C3.

[0107] The control unit 51 can classify and record ordinances into two categories: a parent category and a child category belonging to that parent category, by saving the ordinance text in association with its parent category and child category.

[0108] As described above, vector information of words related to each parent category and child category is stored in related information (parent category database and child category database) associated with the parent category and child category. The control unit 51 retrieves ordinance documents from an external website, generates vector information (vector values) of words contained in the retrieved ordinance documents, and identifies the parent category and child category corresponding to the ordinance document based on the similarity between the generated vector information and the vector information stored in the related information. The control unit 51 can generate an ordinance database in which ordinance documents are classified and recorded in the two categories of the identified parent category and child category.

[0109] Furthermore, the control unit 51 repeatedly retrieves ordinance documents from an external website at required intervals (e.g., every one or two months), determines whether there are any differences between the retrieved ordinance document and the most recently retrieved ordinance document, and if there are differences, generates vector information of the words contained in the retrieved ordinance document, and identifies the parent category and child category corresponding to the ordinance document based on the similarity between the generated vector information and the vector information stored in the related information. The control unit 51 can update the ordinance database, which records ordinance documents classified into the two categories of the identified parent category and child category.

[0110] If the ordinance document is not registered on an external website or similar platform and cannot be obtained as data, it can be obtained by manually entering the information.

[0111] In the example described above, a parent category database and a child category database were prepared in advance, words were extracted from the ordinance document by morphological analysis, and the parent category and child category were identified based on the similarity of the word vectors. However, the method for identifying parent and child categories is not limited to this. For example, a machine learning model may be used to identify parent categories and child categories belonging to those parent categories. For example, a neural network model can be used as the learning model. In this case, the control unit 51 can acquire an ordinance document, and when an ordinance document is input, it can input the acquired ordinance document into a learning model that identifies the parent category and child categories belonging to that parent category corresponding to the ordinance document, thereby identifying the parent category and child category.

[0112] Next, we will explain the BIM (Building Information Modeling) used in this embodiment.

[0113] Figure 29 shows an example of the configuration of the information processing system according to this embodiment. The information processing system comprises a server 100 and a plurality of terminal devices 200. The server 100 and each terminal device 200 are connected via a communication network 1. In the example of Figure 29, there are two terminal devices 200, but the number of terminal devices 200 is not limited to two and may be three or more. The information processing system can provide BIM, and users such as designers can perform BIM modeling on a browser using the terminal devices 200. That is, information necessary for BIM modeling (for example, parameter information described later) can be shared among the terminal devices 200 via the server 100.

[0114] Figure 30 shows an example of the configuration of server 100. Server 100 includes a control unit 101 that controls the entire server 100, a communication unit 102, a geometric engine 103, a storage unit 104, and a parameter DB 107.

[0115] The control unit 101 may be configured by incorporating the required number of CPUs (Central Processing Units), MPUs (Micro-Processing Units), GPUs (Graphics Processing Units), etc. Alternatively, the control unit 101 may be configured by combining DSPs (Digital Signal Processors), FPGAs (Field-Programmable Gate Arrays), etc.

[0116] The communication unit 102 is equipped with a communication module and can communicate with the terminal device 200 and external devices (not shown) via the communication network 1.

[0117] The geometric engine 103 can generate three-dimensional geometric shape information of building members from parameter information relating to those members. The three-dimensional geometric shape information includes three-dimensional coordinate data such as lines, faces, and vertices, as well as data identifying the faces of the members, in order to identify the three-dimensional shape of the member. Parameter information is data used to identify the three-dimensional shape of the member, and it is less data-intensive than the geometric shape information. The geometric engine 103 has a function to convert the parameter information into 3D, and can perform 3D and 2D representations of building members. Details of the parameter information will be described later.

[0118] The storage unit 104 can be composed of semiconductor memory or a hard disk, and stores the BIM model 105, BIM data 106, and necessary information. The BIM model 105 is a model for constructing building components, and the BIM data 106 is data used in the BIM model 105.

[0119] Parameter DB107 is a database that records parameter information.

[0120] The server 100 can provide (export) the BIM model 105 and BIM data 106 to external systems and software via the communication unit 102.

[0121] Figure 31 shows an example of the configuration of the terminal device 200. The terminal device 200 comprises a control unit 201 that controls the entire terminal device 200, a communication unit 202, a geometric engine 203, a display unit 204, an operation unit 205, a parameter database 206, and a storage unit 207. The terminal device 200 can be configured as, for example, a personal computer.

[0122] The control unit 201 may be configured by incorporating the required number of CPUs (Central Processing Units), MPUs (Micro-Processing Units), GPUs (Graphics Processing Units), etc. Alternatively, the control unit 101 may be configured by combining DSPs (Digital Signal Processors), FPGAs (Field-Programmable Gate Arrays), etc.

[0123] The communication unit 202 is equipped with a communication module and can communicate with the server 100 via the communication network 1.

[0124] The geometric engine 203 is the same as the geometric engine 103 provided by server 100, so its explanation will be omitted.

[0125] The display unit 204 is composed of a liquid crystal display or an organic EL display, and provides a user interface (UI) to the user by displaying the necessary information. Alternatively, an external display device may be used instead of the display unit 204.

[0126] The operation unit 205 is, for example, configured as a touch panel and can perform operations such as manipulating icons displayed on the display unit 204, moving and manipulating the cursor, and inputting text. The operation unit 205 may be configured with buttons and switches, or with a keyboard and mouse. The operation unit 205 provides a user interface (UI) to the user by accepting user input. Alternatively, an external terminal device for operation may be provided instead of the operation unit 205.

[0127] Parameter DB206 is a database that records parameter information.

[0128] The storage unit 207 can be composed of semiconductor memory or a hard disk, and stores the BIM model 208, BIM data 209, and necessary information. The BIM model 208 is a model for constructing building components, similar to the BIM model 105, and the BIM data 209 is data used in the BIM model 208, similar to the BIM data 106.

[0129] The information processing system of this embodiment comprises a server 100 and a plurality of terminal devices 200. Each of the server 100 and the plurality of terminal devices 200 is equipped with a geometricization engine 103, 203 that generates geometric shape information of building members based on parameter information relating to those members. One terminal device 200 transmits the parameter information used to generate the geometric shape information to the server 100. The server 100 receives and stores the parameter information and transmits the received parameter information to the plurality of terminal devices 200, excluding the one terminal device 200. This allows the plurality of terminal devices 200 to share the parameter information.

[0130] In other words, when designer A designs a component using parameter information instead of geometric shape information in a terminal device 200A, the geometricization engine 203 can convert the parameter information into 3D geometric shape information. In the terminal device 200A, designer A can use the geometricization engine 203 to display the designed component in 3D (and 2D). The parameter information used by the designer is recorded in the parameter DB 206.

[0131] When new parameter information is generated or updated, or at the instruction of designer A, terminal device 200A transmits the parameter information to server 100. Server 100 receives the parameter information, records it in parameter DB 107, and transmits the parameter information to other terminal devices 200B. Other terminal devices 200B receive the parameter information and record it in parameter DB 206. On other terminal devices 200B, other designers B can use the geometric engine 203 to perform a 3D (and 2D) display of the component designed by designer A based on the parameter information. In this way, by sharing parameter information among terminal devices 200, other designers B can perform a 3D display of a component designed by one designer A, and design information can be shared among designers.

[0132] Furthermore, from a designer's perspective, instead of dealing with a large amount of geometric shape information, it allows for the handling of parameter information with a smaller data volume, thus reducing the workload of building designers.

[0133] Furthermore, from the perspective of an information processing system, it is not necessary to exchange large amounts of geometric shape information between terminal devices 200, and it is possible to exchange parameter information with a small amount of data, thus reducing the processing load on the information processing system.

[0134] Figure 32 shows an example of parameter information. As shown in Figure 32, parameter information includes, for example, member information (e.g., floor, wall, ceiling, etc.), geometric information (e.g., height, width, thickness, level (building floor), etc.), material information (information that identifies or distinguishes the material of the member), cost information (unit price of the member, etc.), and finish information (information that identifies or distinguishes the surface treatment of the member, etc.).

[0135] For example, if the component is a wall, the geometric information of the wall, such as height (e.g., 1000 mm) and width (e.g., 300 mm), can be input into the geometry engine 203 to generate 3D geometric shape information of the wall. Similarly, if the component is a floor, the geometric information of the floor, such as length, width, thickness, and level (floor), can be input into the geometry engine 203 to generate 3D geometric shape information of the floor on the corresponding floor.

[0136] Figure 33 shows an example of determining compliance with regulations using parameter information. As shown in Figure 33, the criteria for determining compliance with regulations may include, for example, wall height restrictions, wall material restrictions, and wall finish restrictions. To determine whether or not a wall meets the height restrictions, the geometric information (height) from the parameter information can be used to make an immediate confirmation. If 3D geometric shape information were used, it would be necessary to display the wall in 3D and calculate the wall height. However, by using parameter information, the determination can be made directly, reducing the workload of the designer.

[0137] Furthermore, whether or not a wall material complies with material restrictions can be immediately confirmed by using the material information from the parameter data. Similarly, whether or not a wall finish complies with finish restrictions can be immediately confirmed by using the finish information from the parameter data. This reduces the workload of the designer.

[0138] As described above, the parameter information includes geometric information and material information relating to the component, and the terminal device 200 can determine whether or not the dimensions (height) or material of the component are subject to regulations based on the parameter information.

[0139] Furthermore, in designs using multiple types of components, the total cost of the components can be immediately confirmed using cost information for each component (unit price x quantity), thereby reducing the workload of the designer.

[0140] Figure 34 shows an example of the processing procedure for classifying and displaying ordinances by the information processing device 50. The control unit 51 acquires data including the building's address and purpose (S11), and extracts ordinances related to the building's architectural design from the ordinance database 60 based on the acquired data (S12). The control unit 51 classifies and displays the extracted ordinances in order of importance of the parent category and the importance of the child categories belonging to the parent category (S13), and then terminates the processing. This allows obtaining the ordinance classification results illustrated in Figure 5.

[0141] Figure 35 shows an example of the process for generating the ordinance database 60 by the information processing device 50. The control unit 51 acquires the ordinance document (S21) and performs morphological analysis on the acquired ordinance document (S22). The control unit 51 calculates the word vectors obtained from the morphological analysis (S23).

[0142] The control unit 51 calculates the similarity between the calculated vector and the word vectors in a pre-prepared parent category database (exemplified in Figure 27) (S24), and identifies the parent category with the greatest similarity (S25).

[0143] The control unit 51 calculates the similarity between the calculated vector and the word vectors in a pre-prepared child category database (exemplified in Figure 28) (S26), and identifies the child category with the greatest similarity (S27). The control unit 51 generates the ordinance database 60 by associating the ordinances with the identified parent and child categories and saving them (S28), and then terminates the process.

[0144] As described above, this embodiment can reduce the workload of building designers.

[0145] (Note 1) The computer program obtains data including the address and use of the building to be designed, and extracts multiple ordinances related to the architectural design of the building from an ordinance database that records ordinances, including multiple tag items that identify the content of the ordinances, classified into two categories: a parent category and child categories belonging to the parent category, based on the obtained data. The computer then performs the following processing: classify the extracted ordinances according to the importance of each of the two categories.

[0146] (Note 2) The computer program instructs the computer to perform the following processing as described in Note 1: arranging the parent categories in order of importance, arranging the child categories belonging to each of the arranged parent categories in order of importance, and classifying and displaying the ordinances in association with each of the arranged child categories.

[0147] (Note 3) When the computer program receives an instruction in Note 1 or Note 2 to classify ordinances according to their urgency, it will cause the computer to execute a process that classifies and displays the ordinances in order of the urgency of the multiple application procedure deadline information included in the application procedure deadline item among the multiple tag items.

[0148] (Note 4) In addition to Note 3, if the computer program receives input for the application procedure deadline item among the multiple tag items, it will cause the computer to execute a process that classifies and displays ordinances that have not yet reached their application procedure deadline in order of remaining days until the application procedure deadline, and also classifies and displays ordinances that have reached their application procedure deadline.

[0149] (Note 5) In any one of Notes 1 to 4, the computer program will perform the following process: aggregate the number of accesses of the referencing item among the multiple tag items over a predetermined period, and classify and display the ordinances based on the aggregated number of accesses.

[0150] (Note 6) The computer program instructs the computer to perform the process described in Note 5, which classifies and displays the ordinances included in each parent category by the number of accesses.

[0151] (Note 7) The computer program instructs the computer to perform the process described in Note 5, which classifies and displays the ordinances included in each of the subcategories by the number of accesses.

[0152] (Note 8) In any one of Notes 1 to 7, the computer program calculates points for each of the following subcategories by multiplying the percentage of the multiple tag items for which the application of the application condition item is mandatory, the percentage of the tag items for which the application procedure deadline is set to a short period, and the number of accesses to the referencing item among the tag items by a weighting coefficient, and then displays the ordinances included in the subdivided subcategories according to the calculated points.

[0153] (Note 9) The computer program defines the workload of the designer for each of the multiple tasks included in the designer's task item among the multiple tag items in any one of Notes 1 to 8, identifies the workload for each of the multiple regulations included in the parent category according to the tasks included in the task item, and then has the computer execute the process of classifying and displaying the regulations according to the identified workload.

[0154] (Note 10) The computer program pre-determines, in any one of Notes 1 to 9, the extraction items corresponding to the required items among the multiple tag items, and when it receives input of the required items, it causes the computer to execute a process that displays the regulations related to the extraction items corresponding to the received required items.

[0155] (Note 11) The computer program, as specified in Note 10, includes at least one of the following required items: application conditions, the designer's tasks, and the application deadline.

[0156] (Note 12) The computer program causes the computer to perform the following processes in any one of Notes 1 to 11: storing vector information of words related to the parent category and the child category, related information associated with the parent category and the child category; obtaining ordinance documents from an external website; generating vector information of words contained in the obtained ordinance documents; identifying the parent category and the child category corresponding to the ordinance documents based on the similarity between the generated vector information and the vector information stored in the related information; and generating an ordinance database in which the ordinance documents are classified and recorded in the two categories of the identified parent category and child category.

[0157] (Note 13) In Note 12, the computer program includes words related to multiple tag items that identify the content of the ordinance.

[0158] (Note 14) The computer program, as described in Note 12 or Note 13, repeatedly retrieves ordinance documents from the external website at the required intervals, determines whether there are any differences between the retrieved ordinance documents and the most recently retrieved ordinance documents, generates vector information of the words contained in the retrieved ordinance documents, identifies the parent category and child category corresponding to the ordinance documents based on the similarity between the generated vector information and the vector information stored in the related information, and updates the ordinance database, which records the ordinance documents classified into the two categories of the identified parent category and child category.

[0159] (Note 15) The computer program accepts input for setting the reference date for the application procedure deadline in any one of Notes 1 to 14, and for each ordinance, it executes a process to generate a schedule that displays the designer's task schedule in a time chart relative to the accepted reference date.

[0160] (Note 16) The computer program, as specified in Note 15, identifies a reference date for the application procedure deadline for each ordinance classified based on the address and use of the building, and instructs the computer to perform the process of accepting input for setting the identified reference date.

[0161] (Note 17) The computer program causes the computer to perform a process in any one of Notes 1 to 16 to generate a birdcage diagram based on at least one of the setback regulations, inverse shadow and inverse sky ratio, and regulations on setback distances based on ordinances classified according to the address and use of the building.

[0162] (Note 18) In Note 17, the computer program further causes the computer to perform a process to generate a birdcage diagram based on the regulations concerning roads under paragraph 2 or self-managed sidewalks under the aforementioned ordinance.

[0163] (Note 19) The information processing device includes a control unit, which acquires data including the address and use of the building to be designed, and from an ordinance database that records ordinances, including multiple tag items that identify the content of the ordinance, classified into two categories: a parent category and child categories belonging to the parent category, extracts multiple ordinances related to the architectural design of the building based on the acquired data, and classifies the extracted multiple ordinances according to the importance of each of the two categories.

[0164] (Note 20) The information processing method involves acquiring data including the address and use of the building to be designed, and from an ordinance database that records ordinances, including multiple tag items that identify the content of the ordinance, classified into two categories: a parent category and child categories belonging to the parent category, extracting multiple ordinances related to the architectural design of the building based on the acquired data, and classifying the extracted multiple ordinances according to the importance of each of the two categories.

[0165] (Note 21) The information processing system comprises a server and a plurality of terminal devices, each of the server and the plurality of terminal devices being equipped with a geometric engine that generates geometric shape information of building members based on parameter information relating to the members, one terminal device transmits the parameter information used to generate the geometric shape information to the server, the server receives and stores the parameter information and transmits the received parameter information to the plurality of terminal devices excluding the one terminal device, and the plurality of terminal devices including the one terminal device share the parameter information.

[0166] (Note 22) In Note 21, the information processing system includes geometric information and material information relating to the member, and the plurality of terminal devices determine whether the member satisfies the regulations of the ordinance relating to the dimensions or material based on the parameter information.

[0167] (Note 23) The information processing method involves the server and each of the multiple terminal devices inputting parameter information relating to building components into a geometric engine to generate geometric shape information of the components; one terminal device transmitting the parameter information used to generate the geometric shape information to the server; the server receiving and storing the parameter information, and transmitting the received parameter information to the multiple terminal devices excluding the one terminal device; and sharing the parameter information among the multiple terminal devices, including the one terminal device.

[0168] The matters described in each embodiment can be combined with each other. Furthermore, the independent and dependent claims described in the claims can be combined with each other in any combination, regardless of the form of reference. In addition, the claims use a form in which claims referencing two or more other claims (multi-claim form), but are not limited to this. A form in which multi-claims referencing at least one multi-claim (multi-multi-claim) may also be used. [Explanation of symbols]

[0169] 1. Communication Network 50 Information Processing Devices 51 Control Unit 52 Communications Department 53 memory 54 Display section 55 Operation section 56 Memory section 57 Computer Programs 58 Interface section 60 Ordinance DB 100 servers 101 Control Unit 102 Communications Department 103 Geometric Engine 104 Storage section 105 BIM Models 106 BIM data 107 Parameter DB 200 terminal devices 201 Control Unit 202 Communications Department 203 Geometric Engine 204 Display section 205 Operation section 206 Parameter DB 207 Memory section 208 BIM models 209 BIM data

Claims

1. We obtain data including the address and use of the building to be designed. From an ordinance database that classifies and records ordinances containing multiple tag items that identify the content of the ordinance into two categories: a parent category and child categories belonging to the parent category, multiple ordinances related to the architectural design of the building are extracted based on the acquired data. The extracted ordinances are classified according to their importance in each of the two categories mentioned above. A computer program that instructs a computer to perform a process.

2. The aforementioned parent categories are arranged in order of importance. For each parent category, the child categories belonging to that parent category are arranged in order of importance. The regulations are classified and displayed according to the subcategory in which they are placed. A computer program according to claim 1 that causes a computer to perform a process.

3. When an instruction is received to classify ordinances according to their urgency, the ordinances will be classified and displayed in order of urgency of the multiple application procedure deadline information included in the application procedure deadline item among the multiple tag items. A computer program according to claim 1 that causes a computer to perform a process.

4. Furthermore, when input is received for the application procedure deadline item among the multiple tag items mentioned above, ordinances whose application procedure deadline has not yet passed will be classified and displayed in order of remaining days until the application procedure deadline, and ordinances whose application procedure deadline has passed will also be classified and displayed. A computer program according to claim 3 that causes a computer to perform a process.

5. The number of accesses to the referencing item among the aforementioned multiple tag items is aggregated over a predetermined period. The regulations are categorized and displayed based on the aggregated number of accesses. A computer program according to claim 1 that causes a computer to perform a process.

6. For each parent category, the ordinances included in that parent category are classified and displayed according to the number of accesses. A computer program according to claim 5 that causes a computer to perform a process.

7. For each of the aforementioned subcategories, the ordinances included in that subcategory are classified and displayed according to the number of accesses. A computer program according to claim 5 that causes a computer to perform a process.

8. For each of the aforementioned subcategories, the percentage of the multiple tag items for which the application of the application condition item is mandatory, the percentage of the tag items for which the application procedure deadline is set to a short application procedure deadline, and the number of accesses to the referencing item among the tag items are each multiplied by a weighting coefficient to calculate the number of points. The ordinances included in the aforementioned subcategories, classified according to the calculated points, are displayed. A computer program according to claim 1 that causes a computer to perform a process.

9. The workload for each of the multiple tasks included in the designer's task item among the aforementioned multiple tag items is defined, For each of the multiple ordinances included in the aforementioned parent category, the workload is identified according to the tasks included in the task items. The regulations are classified and displayed according to the identified load level. A computer program according to claim 1 that causes a computer to perform a process.

10. The extraction items corresponding to the required items among the aforementioned multiple tag items are predetermined, When the required items are entered as described above, the system will display the regulations related to the extracted items corresponding to the entered required items. A computer program according to any one of claims 1 to 9, which causes a computer to perform a process.

11. The aforementioned required items include at least one of the application conditions, the designer's tasks, and the application deadline. The computer program according to claim 10.

12. The vector information of words associated with the parent category and the child category, respectively, is stored as related information associated with the parent category and the child category. Obtain the ordinance document from an external website, Generate vector information of words contained in the acquired ordinance document, Based on the similarity between the generated vector information and the vector information stored in the related information, the parent category and child category corresponding to the ordinance document are identified. The aforementioned ordinance documents are classified and recorded into two categories: a parent category and a child category, to generate an ordinance database. A computer program according to any one of claims 1 to 9, which causes a computer to perform a process.

13. The aforementioned words include words related to multiple tag items that identify the content of the ordinance, The computer program according to claim 12.

14. The ordinance document is repeatedly obtained from the aforementioned external website at the required time, Determine whether there are any differences between the acquired ordinance document and the most recently acquired ordinance document. If there are differences, generate vector information of the words contained in the acquired ordinance document. Based on the similarity between the generated vector information and the vector information stored in the related information, the parent category and child category corresponding to the ordinance document are identified. The ordinance database, which records the aforementioned ordinance documents classified into two categories—a parent category and a child category—will be updated. A computer program according to claim 12 that causes a computer to perform a process.

15. We accept input for setting the reference date for the application procedure deadline. For each regulation, a schedule is generated that displays the designer's task schedule in a time chart relative to the accepted reference date. A computer program according to any one of claims 1 to 9, which causes a computer to perform a process.

16. Based on the address and use of the aforementioned building, a reference date for the application procedure deadline is specified for each ordinance classified accordingly. The system accepts input for setting a specified reference date. A computer program according to claim 15 that causes a computer to perform a process.

17. A birdcage diagram is generated based on at least one of the following: setback regulations, inverse shadow and inverse sky ratio, and regulations concerning setback distances based on ordinances classified according to the address and use of the said building. A computer program according to any one of claims 1 to 9, which causes a computer to perform a process.

18. Furthermore, a birdcage diagram is generated based on the regulations concerning roads under Article 2 or self-managed sidewalks based on the aforementioned ordinance. A computer program according to claim 17 that causes a computer to perform a process.

19. Equipped with a control unit, The control unit, We obtain data including the address and use of the building to be designed. From an ordinance database that classifies and records ordinances containing multiple tag items that identify the content of the ordinance into two categories: a parent category and child categories belonging to the parent category, multiple ordinances related to the architectural design of the building are extracted based on the acquired data. The extracted ordinances are classified according to their importance in each of the two categories mentioned above. Information processing device.

20. We obtain data including the address and use of the building to be designed. From an ordinance database that classifies and records ordinances containing multiple tag items that identify the content of the ordinance into two categories: a parent category and child categories belonging to the parent category, multiple ordinances related to the architectural design of the building are extracted based on the acquired data. The extracted ordinances are classified according to their importance in each of the two categories mentioned above. Information processing methods.

21. The system includes a server and multiple terminal devices. Each of the aforementioned server and the plurality of terminal devices is: It includes a geometry engine that generates geometric shape information of building members based on parameter information relating to those members, One terminal device transmits the parameter information used to generate geometric shape information to the server. The server receives and stores the parameter information, and transmits the received parameter information to the multiple terminal devices, excluding the first terminal device. The parameter information is shared among the plurality of terminal devices, including the one terminal device. Information processing system.

22. The aforementioned parameter information is This includes geometric information and material information relating to the aforementioned member, The aforementioned multiple terminal devices are, Based on the parameter information, it is determined whether or not the regulations concerning the dimensions or materials of the member are satisfied. The information processing system according to claim 21.

23. Each of the server and multiple terminal devices, Parameter information regarding building components is input into a geometric engine to generate geometric shape information of the components. One terminal device transmits the parameter information used to generate geometric shape information to the server. The server receives and stores the parameter information, and transmits the received parameter information to the multiple terminal devices, excluding the first terminal device. The parameter information is shared among the plurality of terminal devices, including the one terminal device. Information processing methods.

Images