Information processing apparatus, information processing method, and program

Abstract

To provide an information processor, an information processing method and a program for specifying a blending plan document suitable for a predetermined condition from among a large number of blending plan documents.SOLUTION: In a management system that manages at least a part of exchanges between a client company and a plurality of client companies of ready-mixed concrete, a client device A11, which is an information processor, includes a control unit A36 that associates an S-value relating to placement of ready-mixed concrete and an application period with a blending plan document generated by reading a blending plan document of the ready-mixed concrete by an OCR, and a storage unit A34 that stores association information for associating the S-value with the blending plan document.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] A trading company or a general construction company (general contractor) acts as the client and requests the shipment of ready-mix concrete to a factory.

[0003] For example, Patent Document 1 describes a ready-mixed concrete reservation system that executes a process of registering a ready-mixed concrete order reservation based on ready-mixed concrete order information acquired upon receiving a ready-mixed concrete order from an orderer (see Patent Document 1). The reservation system executes a mix determination process at the time of reservation acceptance, which determines whether to apply standard mix information indicating a standard mix used when ready-mixed concrete is to be delivered within a standard period or modified mix information indicating a modified mix used when ready-mixed concrete is to be delivered within a modified period that differs from the standard period, based on the order information. After this determination is made, the reservation system registers order information with the reservation completed. Here, the order information includes desired delivery schedule information indicating a desired delivery schedule for the ready-mixed concrete. The reservation system determines to apply the standard mix information as the mix information if the date corresponding to the desired delivery schedule indicated by the desired delivery schedule information falls within the standard period, and determines to apply the modified mix information as the mix information if the date corresponding to the desired delivery schedule falls within the modified period. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7470952 Summary of the Invention [Problem to be solved by the invention]

[0005] However, there is still room for development in the prior art. For example, in the past, there were cases where a large number of mix plans for ready-mixed concrete were created, and it was sometimes difficult to identify a mix plan that met predetermined conditions from among the many mix plans.

[0006] The present disclosure has been made in consideration of these circumstances, and aims to provide an information processing device, information processing method, and program that can identify a formulation plan that meets specified conditions from among a large number of formulation plans. [Means for solving the problem]

[0007] One aspect of the present disclosure is an information processing device that includes a control unit that links S-value data including an S-value and application period related to the pouring of ready-mixed concrete with mix plan data generated by reading the mix plan for the ready-mixed concrete using OCR, and a memory unit that stores linking information that links the S-value data with the mix plan data.

[0008] One aspect of the present disclosure is an information processing method in which an information processing device links S-value data, including an S-value and application period related to the pouring of ready-mixed concrete, to mix plan data generated by reading the mix plan for the ready-mixed concrete using OCR, and stores linking information linking the S-value data to the mix plan data in a memory unit. One aspect of the present disclosure is a program for enabling a computer to implement the following functions: linking S-value data, including the S-value and application period related to the pouring of ready-mixed concrete, to mix plan data generated by reading the mix plan for the ready-mixed concrete using OCR; and storing linking information linking the S-value data to the mix plan data in a memory unit. [Effects of the Invention]

[0009] According to the present disclosure, an information processing device, an information processing method, and a program can identify a blending plan that meets specified conditions from among a large number of blending plans. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration example of a management system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating a schematic configuration example of a request sending device according to the embodiment. [Figure 3A] A diagram showing an example of the procedure for creating a request for formulation plan creation at a requesting company in an embodiment. [Figure 3B] A diagram showing an example of the procedure for creating a blending plan at a client company in accordance with an embodiment. [Figure 4] A diagram showing an example of the procedure for linking formulation plans at a requesting company in an embodiment. [Figure 5] FIG. 10 is a diagram showing an example of a procedure for creating a construction plan at a client company according to an embodiment. [Figure 6A] FIG. 10 is a diagram showing an example of a procedure for creating a concrete pouring request form at a requesting contractor according to an embodiment. [Figure 6B] A figure showing an example of the procedure for creating a concrete pouring request response at a requested contractor in the embodiment. [Figure 7] FIG. 10 is a diagram showing an example of a procedure for determining a concrete pouring factory at a client company according to an embodiment. [Figure 8] FIG. 10 is a diagram showing an example of a procedure for creating a day-before confirmation document at a requesting trader according to the embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of a contractor data editing screen according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a site data editing screen according to the embodiment. [Figure 11] A figure showing an example of a pouring location data editing screen related to the embodiment. [Figure 12] FIG. 10 is a diagram showing an example of an S value data editing screen according to the embodiment. [Figure 13]This figure shows an example of a pouring location data selection screen when creating a request for creation of a mix plan according to an embodiment. [Figure 14] A figure showing an example of a request for preparation of a blending plan for an embodiment. [Figure 15A] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 15B] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 15C] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 15D] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 15E] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 15F] FIG. 1 is a diagram showing a schematic example of a blending plan according to an embodiment. [Figure 16A] This figure shows an example of a pouring location data editing screen for the embodiment and an example of linking with a mix plan. [Figure 16B] A diagram schematically showing an example of metadata included in the linking data of a formulation plan related to an embodiment. [Figure 16C] A diagram schematically showing an example of metadata included in the linking data of a formulation plan related to an embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of a contractor and site data selection screen according to the embodiment. [Figure 18] FIG. 10 is a diagram showing an example of a playing plan data editing screen according to the embodiment. [Figure 19] FIG. 10 is a diagram showing an example of a playing plan data selection screen according to the embodiment. [Figure 20] FIG. 2 is a diagram showing an example of a hitting plan according to an embodiment. [Figure 21] FIG. 10 is a diagram showing an example of a playing plan data selection screen according to the embodiment. [Figure 22] A figure showing an example of a casting request factory selection screen related to the embodiment. [Figure 23] FIG. 10 is a diagram showing an example of a concrete pouring request form according to an embodiment. [Figure 24] FIG. 10 is a diagram showing an example of a playing plan data selection screen according to the embodiment. [Figure 25] FIG. 10 is a diagram showing an example of a day-before confirmation according to the embodiment. [Figure 26] A figure showing an example of a table that associates pouring locations (ranges) with pouring locations (specific locations) in accordance with an embodiment. [Figure 27] 1 is a diagram showing an example of the relationship between the structural strength correction value (S value) according to the embodiment, the seasonal mix of a factory, and the required mix plan. FIG. [Figure 28] FIG. 2 is a diagram illustrating an example of a data structure of management data according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0012] [Management system] FIG. 1 is a diagram showing a schematic configuration example of a management system 1 according to an embodiment. In this embodiment, the management system 1 manages at least a part of the exchange between a requester and a requestee of ready-mix concrete. The name "management system 1" is used for convenience of explanation, and any name may be used.

[0013] <Requesting company> The management system 1 includes a requesting company 11 and requested companies 21 to 23. The client company 11 is, for example, a trading company or a general construction company. In this embodiment, for the sake of simplicity, it is assumed that the requesting company 11 is a single company, but the requesting company 11 may be made up of multiple companies. In addition, in this embodiment, for the sake of simplicity, only one requesting company 11 is shown, but, for example, there may be a plurality of requesting companies.

[0014] The requesting company 11 includes a requesting device A11 and a printing device A12. In this embodiment, the printing device A12 also has a facsimile function. The request source device A11 is configured using, for example, a computer. In this embodiment, the requesting device A11 and the printing device A12 are separate devices, but the requesting device A11 may also include the functions of the printing device A12. Furthermore, in this embodiment, for the sake of simplicity, a single request source device A11 is shown, but the functions of the request source device A11 may be distributed among a plurality of devices. Furthermore, in this embodiment, for the sake of simplicity, a single printing device A12 is shown, but for example, a plurality of printing devices may be provided and any desired printing device may be used as appropriate.

[0015] The requesting company 11 has a requesting user A1. The requesting user A1 is, for example, an employee of the requesting company 11. In this embodiment, the requesting user A1 performs tasks such as operating the requesting device A11 and the printing device A12. In this embodiment, to simplify the explanation, one requesting user A1 is shown, but as another example, there may be two or more requesting users who share and carry out the work as appropriate.

[0016] <Contractor> Client companies 21 to 23 are each ready-mix concrete factories. Here, in this embodiment, for the sake of explanation, three requested contractors 21 to 23 are shown, but as another example, it may be applied when there are two requested contractors, or when there are four or more requested contractors. This embodiment is also applicable to a case where there is only one requested trader.

[0017] In this embodiment, for the sake of convenience, a detailed description will be given using one requested company 21 as a representative. The other requested companies 22 and 23 are similar to the requested company 21, and detailed explanations thereof will be omitted.

[0018] The requested company 21 includes a requested device B11 and a printing device B12. In this embodiment, the printing device B12 also has a facsimile function. The request receiving device B11 is configured using, for example, a computer. In this embodiment, the request receiving device B11 and the printing device B12 are separate devices, but the request receiving device B11 may also include the functions of the printing device B12. Furthermore, in this embodiment, for the sake of simplicity, a single request receiving device B11 is shown, but the functions of the request receiving device B11 may be distributed among a plurality of devices. Furthermore, in this embodiment, for the sake of simplicity, a single printing device B12 is shown, but for example, a plurality of printing devices may be provided and any desired printing device may be used as appropriate.

[0019] The requested company 21 has a requested user B1. The requested user B1 is, for example, an employee of the requested company 21. In this embodiment, the request destination user B1 performs tasks such as operating the request destination device B11 and the printing device B12. In this embodiment, to simplify the explanation, one requested user B1 is shown, but as another example, there may be two or more requested users who share and complete the work as appropriate.

[0020] <Communication between the requesting company and the requested company> In this embodiment, a case is shown in which paper documents are exchanged between the requesting company 11 and each of the requested companies 21 to 23. This exchange may also be by facsimile.

[0021] <Requesting device> FIG. 2 is a diagram illustrating an example of a schematic configuration of the request source device A11 according to the embodiment. The example configuration of the request sending device A11 shown in FIG. 2 is a schematic diagram for the purpose of explanation, and other configurations may be used.

[0022] The requesting device A11 includes an input unit A31 for inputting information, an output unit A32 for outputting information, a communication unit A33 for communicating information, a memory unit A34 for storing information, an OCR data acquisition unit A35 for acquiring data resulting from optical character recognition (OCR: Optical Character Reader or Optical Character Recognition), and a control unit A36 for performing various controls. The control unit A36 includes a pouring location conversion control unit A111 and a data linking control unit A112.

[0023] The OCR data acquisition unit A35 has an OCR function, and performs optical character recognition processing on image data in which characters are written using the OCR function, and acquires data of the recognized characters (OCR data). Here, in this embodiment, a case is shown in which the requesting device A11 is equipped with an OCR function, but as another example, the OCR function may be equipped external to the requesting device A11, and in this case, the OCR data acquisition unit A35 acquires data (OCR data) that is the result of optical character recognition processing performed by the external OCR function. For example, the external OCR function may be an OCR function provided by a cloud service. As a specific example, the requesting device A11 may transmit data for which OCR is desired to be performed to a predetermined server in the cloud, the server may receive the data and perform optical character recognition processing on the data using an OCR function, the server may transmit data resulting from the processing (OCR data) to the requesting device A11, and the requesting device A11 may acquire the data (OCR data). In this embodiment, for convenience of explanation, the expressions "characters" or "character strings" are used, but these may include symbols and codes, or may be composed of symbols or codes only.

[0024] The pouring location conversion control unit A111 performs control relating to conversion between pouring locations (range) and pouring locations (specific locations), thereby performing processing to convert these. Here, in this embodiment, the pouring location (range) indicates a pouring location expressed using a range, and the pouring location (specific location) indicates a pouring location expressed using a specific location. In addition, in this embodiment, when the pouring location (specific location) is used for searching, it is also referred to as the pouring location (for search).

[0025] The data linking control unit A112 controls data linking, thereby performing processing such as linking predetermined data together. In this embodiment, the data linking control unit A112 performs control relating to the linking of data relating to, for example, a blending plan.

[0026] In this embodiment, for the sake of convenience of explanation, the control functions possessed by the control unit A36 are shown as the pouring location conversion control unit A111 and the data linking control unit A112, but the control unit A36 may have various control functions. Furthermore, names such as the pouring location conversion control unit A111 and the data linking control unit A112 are used for the convenience of explanation, and may be called by any name.

[0027] <Example of matching between pouring location (range) and pouring location (specific location)> FIG. 26 is a diagram showing an example of a table T1 that associates pouring locations (ranges) with pouring locations (specific locations) according to the embodiment. Table T1 shows five specific examples of associations with "No." 1 to 5. Note that "No." is added for the purpose of explanation and does not limit the technical content. In this correspondence, "pouring location (range)" and "pouring location (specific location)" are associated with each other. For ease of explanation, table T1 includes an explanation of the association in the "explanation" column.

[0028] "No. 1" specifies that the pouring location (range) of "1st floor to 5th floor" corresponds to the pouring locations (specific locations) of "1st floor, 2nd floor, 3rd floor, 4th floor, 5th floor." Here, these are specific examples for the purpose of explanation, and generally, it is specified that a pouring location (range) of "floor i to floor j" corresponds to a pouring location (specific location) of "floor i, and if there are other floors between floor i and floor j, each floor of all those floors, floor j" where i and j are natural numbers and j is greater than i. In this way, when the pouring location (range) is a numerical range of floor numbers, the pouring location (specific location) is a division of each floor included in the numerical range.

[0029] "No. 2" specifies that the pouring location (range) of "basement 1st floor to 2nd floor" should be associated with the pouring locations (specific locations) of "basement 1st floor, 1st floor, 2nd floor." Here, these are specific examples for the purpose of explanation, and generally, it is specified that i and j are natural numbers, and a pouring location (range) of "basement floor i to j" corresponds to a pouring location (specific location) of "basement floor i, and if there are other floors between basement floor i and j, each of those floors excluding floor 0, and floor j." In this way, when the casting location (range) is a numerical range of floor numbers and the numerical range spans from underground to above ground, the 0th floor is excluded from the casting location (specific location). Incidentally, the existence of a basement floor and the absence of a zero floor, as in this example, is unique to the field of buildings.

[0030] "No. 3" specifies that the pouring location (range) of "1st floor to mezzanine floor" should be associated with the pouring location (specific location) of "1st floor, mezzanine floor." Here, these are specific examples for the purpose of explanation, and generally, when j is a natural number and the upper limit of the pouring location (range) is the "middle jth floor," a correspondence is defined in which the pouring location (specific location) includes the "middle jth floor" but does not include the "jth floor." In this way, if the upper limit of the pouring location (range) is the "middle jth floor," at the pouring location (specific location), the "middle jth floor" is considered to exist between the "(j-1)th floor" and the "jth floor," and the "jth floor" is not included. Incidentally, the existence of a mezzanine floor, as in this example, is unique to the field of buildings.

[0031] Here, another example of "No. 3" will be shown. That is, it may be specified that the pouring locations (range) of "mezzanine floor to third floor" correspond to the pouring locations (specific locations) of "mezzanine floor, second floor, third floor." Here, these are specific examples for the purpose of explanation, and generally, when i is a natural number and the lower limit of the pouring location (range) is the "middle i-th floor," a correspondence is defined in which the pouring location (specific location) includes the "middle i-th floor" but does not include the "(i-1)th floor." In this way, if the lower limit of the pouring location (range) is the "middle i floor," at the pouring location (specific location), the "middle i floor" is considered to be between the "(i-1) floor" and the "i floor," and the "(i-1) floor" is not included. Incidentally, the existence of a mezzanine floor, as in this example, is unique to the field of buildings.

[0032] "No. 4" specifies that the concrete pouring location (range) "5F~RF" is associated with the concrete pouring location (specific location) of the floor above the "5th floor." Here, these are specific examples for the purpose of explanation, and generally, it is specified that i is a natural number and a pouring location (range) of "iF~RF" corresponds to a pouring location (specific location) of "i floor, and if there are other floors between i floor and RF (rooftop), each floor of all those floors, and the rooftop." In other words, it can be determined that this pouring location (specific location) is "i floor" or higher. In this way, when the upper limit of the pouring location (range) is "RF", floors above the lower limit floor of the pouring location (range) are considered to be included in the pouring location (specific location). In this example, "F" represents "floor," and either representation is equivalent. Incidentally, the presence of RF (rooftop) as in this example is unique to the field of buildings.

[0033] "No. 5" specifies that the pouring location (range) of "1st floor columns and walls to 3rd floor beams and floor" should be matched with the pouring locations (specific locations) of "1st floor columns, 1st floor walls, 2nd floor beams, 2nd floor floor, 2nd floor columns, 2nd floor walls, 3rd floor beams, 3rd floor floor." Here, these are specific examples for the purpose of explanation, and generally, it is specified that the pouring location (range) corresponds to the pouring location (specific location) based on the order of columns, walls, beams, and floors. In this way, the concrete pouring locations (areas) are divided and concrete pouring locations (specific locations) are determined, assuming that concrete will be poured in the order of columns, walls, beams, and floors. Incidentally, the presence of columns, walls, beams, and floors, as in this example, is unique to the field of buildings.

[0034] In addition, there are no particular limitations on the content of the correspondence between the pouring location (range) and the pouring location (specific location), and it is not limited to the content exemplified in table T1 of this embodiment, and any correspondence content may be used.

[0035] As an example, the pouring location conversion control unit A111 may determine whether the character string stored in the pouring location (range) contains the mark "~", and if it determines that the mark is included, determine whether the character string is included in the correspondence information for converting from the pouring location (range) to the pouring location (specific location), and if it determines that the character string is included in the correspondence information, perform the conversion. As another example, the pouring location conversion control unit A111 may determine, for all strings stored in the pouring location (range), whether the string is included in the correspondence information for conversion from the pouring location (range) to the pouring location (specific location), and perform the conversion if it determines that the string is included in the correspondence information.

[0036] Here, the correspondence information shown in table T1 may be stored in, for example, the storage unit A34. However, in the example of FIG. 26, for the sake of convenience, specific examples of correspondence information are described in table T1, but for example, table T1 may be provided that holds correspondence information having generalized content. As an example, table T1 does not need to include information in the "Description" column. As another example, only the information in the "explanation" column may be specified in table T1, and the correspondence between the pouring location (range) and the pouring location (specific location) may be determined based on the content of the "explanation."

[0037] In this embodiment, the pouring location conversion control unit A111 is capable of converting from a pouring location (range) to a pouring location (specific location) and from a pouring location (specific location) to a pouring location (range) based on correspondence information between the pouring location (range) and the pouring location (specific location). As a specific example, the pouring location conversion control unit A111 can convert a pouring location (range) such as "1st floor to 5th floor" into multiple specific locations (individual locations) within that range, such as "1st floor," "2nd floor," "3rd floor," "4th floor," and "5th floor" (specific locations). As a specific example, the pouring location conversion control unit A111 can convert a pouring location (specific location) such as "1st floor" into a pouring location (range) such as "1st floor to 5th floor," which is a range that includes that specific location (individual location). In this conversion, for example, a process may be performed in which a character string representing a pouring location (range) is newly displayed as a character string representing a pouring location (specific location) corresponding to that range, or a process may be performed in which, using the character string representing the pouring location (specific location) as a key, a character string for a pouring location (range) having a range that includes that pouring location (specific location) is identified from among the character strings representing multiple existing pouring locations (ranges).For example, a process may be performed in which it is determined whether or not information on an already existing pouring location (range) matches (matches) the information on the pouring location (range) to be converted from the information on the key pouring location (specific location).

[0038] Here, in this embodiment, when the requesting device A11 converts the pouring location (range) into a pouring location (specific location), the pouring location (specific location) may be displayed on the screen as a pouring location (for search), which is a pouring location for search purposes. As another example, when the requesting device A11 converts a pouring location (range) into a pouring location (specific location), the pouring location (specific location) may be used for internal processing in the requesting device A11, but may not be displayed on the screen. As yet another example, when the requesting device A11 converts a pouring location (range) into a pouring location (specific location), the pouring location (specific location) is not displayed on the screen spontaneously, but when, for example, a specified operation is performed by the requesting user A1, the pouring location (specific location) may be displayed on the screen as a pouring location (for search), which is a pouring location for search purposes.

[0039] <Example of the relationship between the structural strength correction value (hereinafter referred to simply as "S value"), the factory's seasonal mix, and the required mix plan> FIG. 27 is a diagram showing an example of the relationship between the structural strength correction value (S value), the seasonal mix of a factory, and the required mix plan according to the embodiment. Note that the example in FIG. 27 is an example for the purpose of explanation, and the start and end dates of each period may be any other dates.

[0040] Figure 27 shows January to December. In the example of FIG. 27, the structural strength correction value (S value) is 6 for the period "11 / 11 to 2 / 20", 3 for the period "2 / 21 to 7 / 10", 6 for the period "7 / 11 to 9 / 10", and 3 for the period "9 / 11 to 11 / 20". In the example of Figure 27, the seasonal mix for the factory is as follows: "Winter" mix for the period "12 / 11 to 3 / 10", "Standard" mix for the period "3 / 11 to 6 / 10", "Summer" mix for the period "6 / 11 to 9 / 20", and "Standard" mix for the period "9 / 21 to 12 / 10". Note that these periods are examples for explaining the periods of the structural strength correction value (S value) and the periods of seasonal blending in factories, and are not necessarily limited to the example of FIG.

[0041] The combination patterns of the structural strength correction value (S value) and the seasonal mix of the factory are (Pattern 1) to (Pattern 6) as follows. (Pattern 1) is a pattern in which the S value is 6 and the factory's seasonal mix is ​​"winter." (Pattern 2) is a pattern in which the S value is 3 and the factory's seasonal mix is ​​"winter." (Pattern 3) is a pattern in which the S value is 3 and the factory's seasonal mix is ​​the "standard period." (Pattern 4) is a pattern in which the S value is 3 and the factory's seasonal mix is ​​"summer." (Pattern 5) is a pattern in which the S value is 6 and the seasonal mix of the factory is "summer." (Pattern 6) is a pattern in which the S value is 6 and the factory's seasonal mix is ​​the "standard period."

[0042] In the example of FIG. 27, (Pattern 1) to (Pattern 6) are simply shown as (1) to (6). 27, the pattern for early January and the pattern for late December overlap, but they represent the same pattern. In other words, December of one year and January of the next year are treated as consecutive.

[0043] Here, the structural strength correction value (S value) differs for each region (which may also be called a district) and for each type of cement. Additionally, the seasonal mix of ingredients varies from factory to factory. The required mix plan includes, at most, all possible combinations of the structural strength correction value (S value) period and the factory's seasonal mix period, resulting in six patterns, (Pattern 1) to (Pattern 6), as shown in Figure 27.

[0044] <Example of management data structure> FIG. 28 is a diagram illustrating an example of a data structure of management data according to the embodiment. In this embodiment, the request source device A11 manages the management data. The management data may be stored and managed in the storage unit A34 of the request source device A11, for example.

[0045] In this embodiment, the management data has a tree-like data structure. In the data structure of the management data, the contractor data is at the top level, and one or more site data are placed under it. Under each site data, there is one or more pouring location data. Under each pouring location data, there are two S-value data. Under each S value data, there are six blending plan data. Here, in this embodiment, the blending plan data is data resulting from reading the written blending plan using OCR.

[0046] In addition, in this embodiment, predetermined metadata (attribute data) may be linked to the blending plan data. In this embodiment, for the sake of convenience, the blending plan data and the metadata associated with it are described as separate data, but for example, the blending plan data may be considered to include the metadata in addition to the data resulting from the OCR reading.

[0047] The data structure of this embodiment has a hierarchical structure in the order of contractor data, site data, pouring location data, S-value data, and mix plan data, from top to bottom, and one parent data (data at a higher level) can have multiple child data (data at a lower level). The builder data includes the "builder name." The site data includes the "site name." The pouring location data includes the name of the "pouring location," the "design strength" (also known as Fc), the "slump," the "bone size," and the "cement type."

[0048] Here, Fc is set for each casting location. A structural strength correction value (S value) according to the period must be added to Fc. Normally, as shown in the example in Figure 27, the S value is 3 in the standard period, and 6 in the summer and winter periods, and these two types are required. In this embodiment, the S value data includes the S value and such a period (also referred to as an application period in this embodiment). Here, the S value data may include multiple periods. Depending on the pouring location, the S value may not be required. Additionally, the S value may vary from factory to factory depending on the pouring location.

[0049] Furthermore, for S-value data, in addition to the above, it is necessary to take into account the type of material and value adjustments (seasonal mix) according to the period determined for each factory. For this reason, as in the example of Figure 27, for the same S-value, three different periods (seasonal mix) are usually required: standard, summer, and winter. For example, since there are two combinations of S values ​​and three seasonal mixes, up to six mix plans are required for one pouring location.

[0050] Before the ready-mix concrete is shipped, the contractor 21 prepares and submits a mix plan. The request to create a mix plan covers multiple pouring locations at a single site. The JIS requires that a mix plan be submitted before the ready-mix concrete is shipped. For this reason, in the event that the factory that was scheduled to ship the concrete is unable to do so for some reason, the requesting contractor 11 typically requests the creation of mix plans from multiple factories (multiple requested contractors 21 to 23 in the example of Figure 1) so that the concrete can be shipped from another factory that has submitted a mix plan.

[0051] In this embodiment, the data linking control unit A112 is capable of linking the S value data with the blending plan data, and is also capable of linking the blending plan data with predetermined metadata. In addition, the data linking control unit A112 may, for example, perform a process of identifying the linked blending plan data from the S value data for S value data and blending plan data that are already linked, or a process of identifying the linked S value data from the blending plan data. Furthermore, the data linking control unit A112 may perform a predetermined search process using, for example, information included in the metadata as a key.

[0052] [Example of overall processing flow] In this embodiment, processing is performed in the order of the processing flow shown in Figure 3A, the processing flow shown in Figure 3B, the processing flow shown in Figure 4, the processing flow shown in Figure 5, the processing flow shown in Figure 6A, the processing flow shown in Figure 6B, the processing flow shown in Figure 7, and the processing flow shown in Figure 8. It should be noted that this overall processing flow is merely an example, and is not necessarily limited to the processing flow according to this embodiment.

[0053] In this embodiment, the following processing flow is performed by, for example, one piece of software (application), but as another example, it may be performed by a combination of two or more pieces of software (applications). Each screen in the following processing flow is displayed by, for example, a user (in this embodiment, requesting user A1) performing a predetermined operation. Such operations include, for example, an operation to call up a new task screen when starting a new task, and an operation to transition from one task screen to the next screen (for example, a higher-level screen or a lower-level screen). The operation for calling up each screen, the content displayed on each screen, the layout of information on each screen, and the like are not necessarily limited to those in this embodiment, and various modes may be used.

[0054] In the following processing flow, the control of various processes in the request source device A11 is performed by the control unit A36. For example, in the request source device A11, control regarding conversion between a pouring location (range) and a pouring location (specific location) is performed by a pouring location conversion control unit A111. For example, in the request source device A11, control regarding linking of data in the blending plan is performed by a data linking control unit A112. It should be noted that such division of the functions of the control unit is for the convenience of explanation and is not limited to this.

[0055] FIG. 3A is a diagram showing an example of a procedure for creating a blending plan creation request at a requesting trader according to an embodiment. FIG. 3B is a diagram showing an example of a procedure for creating a blending plan at a client company according to an embodiment. FIG. 4 is a diagram showing an example of a procedure for linking blending plans at a client company according to an embodiment. FIG. 5 is a diagram illustrating an example of a procedure for creating a construction plan at a client company according to the embodiment. FIG. 6A is a diagram showing an example of a procedure for creating a concrete pouring request form at a client company according to the embodiment. FIG. 6B is a diagram showing an example of a procedure for creating a concrete pouring request reply at the requested contractor according to the embodiment. FIG. 7 is a diagram showing an example of a procedure for determining a concrete pouring plant at a client company according to the embodiment. FIG. 8 is a diagram showing an example of a procedure for creating a day-before confirmation document at a requesting trader according to the embodiment.

[0056] Each processing flow will be explained below.

[0057] <Creation of a request for blending plan creation by the client> The processing flow shown in FIG. 3A will be described.

[0058] (Step S11) The request source device A11 inputs the builder data. The contractor data is input, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S12.

[0059] <Example of the contractor data editing screen> FIG. 9 is a diagram illustrating an example of a contractor data editing screen according to the embodiment. A screen E1 shown in FIG. 9 is an example of a contractor data editing screen. On screen E1, "Edit Contractor Data" is displayed at the top. In this embodiment, when a requesting user A1 performs a predetermined operation on the requesting device A11, a screen E1 is displayed.

[0060] As the builder data, for example, the "builder name" can be input. In addition, for example, the "site name" can be input as site data under the contractor data. In the example of FIG. 9, the name "XX Construction Co., Ltd." is entered and displayed as the "Constructor Name." In the example of FIG. 9, the names "XX Building New Construction Project" and "YY Tower New Construction Project" are entered and displayed as "site names."

[0061] In the example of Figure 9, screen E1 displays buttons that can be clicked, such as a button F11 for confirming the screen contents (OK), a button F12 for canceling the screen contents, a button F13 for adding an input item, a button F14 for editing an input item, and a button F15 for deleting an item that has already been entered.

[0062] (Step S12) The request source device A11 inputs the site data. The site data is input, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S13.

[0063] <Example of the site data editing screen> FIG. 10 is a diagram illustrating an example of a site data editing screen according to the embodiment. A screen E2 shown in FIG. 10 is an example of a site data editing screen. On screen E2, "Field Data Editing" is displayed at the top.

[0064] In this embodiment, the screen E1 shown in FIG. 9 and the screen E2 shown in FIG. 10 are in a higher-order and lower-order relationship. Specifically, when the requesting user A1 selects a site name (in this example, "XX Building New Construction Work") on screen E1 and presses the "Edit" button F14, the requesting device A11 controls the screen to transition to screen E2 of Figure 10. Furthermore, when the "add" button F13 is pressed on the screen E1, the request source device A11 performs control to transition to a screen E2 for inputting new site data (site name).

[0065] For example, the "Name of the installer" is automatically displayed. Note that, for content that has already been entered, that content may be displayed automatically, for example. As site data, for example, the "site name" and "site address" can be input. In addition, for example, "pouring location" can be input as pouring location data under the site data. In the example of FIG. 10, the names "1st floor to 5th floor," "exterior ditch," and "foundation, 2nd basement floor to 1st basement floor" are entered and displayed as "pouring locations." In the example of Figure 10, "Fc" and "S value" are displayed for each "casting location."

[0066] In the example of Figure 10, screen E2 displays buttons that can be clicked, such as a button F21 for confirming the screen contents (OK), a button F22 for canceling the screen contents, a button F23 for adding an input item, a button F24 for editing an input item, and a button F25 for deleting an item that has already been entered. When the button F21 or F22 is pressed, the request source device A11 performs control to return to the screen E1.

[0067] (Step S13) The request source device A11 inputs data on the pouring location (range). The input of the pouring location (range) data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S14.

[0068] <Example of the casting location data editing screen> FIG. 11 is a diagram showing an example of a pouring location data editing screen according to the embodiment. A screen E3 shown in FIG. 11 is an example of a pouring location data editing screen. On screen E3, the message "Edit pouring location data" is displayed at the top.

[0069] In this embodiment, the screen E2 shown in FIG. 10 and the screen E3 shown in FIG. 11 are in a higher-order and lower-order relationship. Specifically, when the requesting user A1 selects one pouring location (in this example, "1st floor to 5th floor") on screen E2 and presses the "Edit" button F24, the requesting device A11 controls the screen to transition to screen E3 of Figure 11. Furthermore, when the "Add" button F23 is pressed on the screen E2, the request source device A11 performs control so that the screen transitions to a screen E3 for inputting a new pouring location.

[0070] For example, the "Constructor Name" and the "Site Name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. As pouring location data, for example, "Pouring location," "Pouring location (for search)," "Fc (design standard strength)," "Structural strength correction value," "Slump, flow," "Bone size," and "Cement type" can be input. In the example of FIG. 11, "1st floor to 5th floor" is input and displayed as "Pouring location". In the example of Figure 11, "Pouring location (for search)," "Fc (design standard strength)," "Structural strength correction value," "Slump, flow," "Bone size," and "Cement type" are entered and displayed as "1st floor, 2nd floor, 3rd floor, 4th floor, 5th floor," "24," "S value 3.6," "15," "20," and "N."

[0071] In this embodiment, the "structure strength correction value" can be selected from three options: "S value 3,6," "no S value," and "each company's S value."

[0072] In the example of FIG. 11, a button F33 for "Automatically Obtain S Value Period" is displayed on the screen E3. When the requesting user A1 selects the button F33, the requesting device A11 automatically acquires the S value period and displays the acquired S value period on the screen E3. In the example of FIG. 11, it is displayed that "Period 1" where the "S value" is "3" is "2 / 23 to 7 / 6" and "Period 2" is "9 / 8 to 11 / 25". In the example of FIG. 11, it is displayed that "Period 1" where the "S value" is "6" is "7 / 7 to 9 / 7" and "Period 2" is "11 / 26 to 2 / 22". Note that these periods are merely examples for the purpose of explanation and may vary depending on, for example, the region.

[0073] In this embodiment, the S value period is registered in advance in the request source device A11 according to a combination of region and cement type. Then, based on such registered information, the request source device A11 uses the "site address" of the site data and the "cement type" of the pouring location data as keys to obtain the S value period corresponding to the keys. In the example of FIG. 11, buttons F34 to F35 for editing the S-value period are displayed on screen E3, and by clicking on buttons F34 to F35 or the like, the S-value period can be edited manually (operated) by the requesting user A1.

[0074] In the example of FIG. 11, on screen E3, buttons F31 for finalizing (OK) the screen content and button F32 for canceling the screen content are displayed as buttons that can be accepted by clicking or the like. In the requesting device A11, when button F31 or button F32 is pressed, control is performed to return to screen E2.

[0075] (Step S14) In the requesting device A11, automatically, the placement location (range) entered in the "Placement Location" field is divided into placement locations for search and saved as "Placement Location (for Search)". In the example of FIG. 11, an arrow X1 that schematically represents such an automatic conversion is shown, but arrow X1 may not be displayed. Then, the process proceeds to step S15.

[0076] Here, in the present embodiment, in the requesting device A11, when the requesting user A1 inputs information on the placement location (range) in the "Placement Location", automatically, the content is divided into placement locations for search and saved as information on "Placement Location (for Search)". In the example of FIG. 11, on screen E3, "Placement Location (for Search)" can also be edited manually (operated) by the requesting user A1.

[0077] (Step S15) In the requesting device A11, S-value data is input. The input of the S-value data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S16.

[0078] <Example of S-value data editing screen> FIG. 12 is a diagram showing an example of an S value data editing screen according to the embodiment. A screen E4 shown in FIG. 12 is an example of an S-value data editing screen. On screen E4, "S value data editing" is displayed at the top.

[0079] In this embodiment, the screen E3 shown in FIG. 11 and the screen E4 shown in FIG. 12 are in a higher-order and lower-order relationship. Specifically, when the requesting user A1 presses the "Edit" button (button F34 in the example of Figure 11) corresponding to one S value (in this example, "3") on screen E3, the requesting device A11 controls the screen to transition to screen E4 of Figure 12.

[0080] For example, "Constructor name," "Site name," "Pouring location," and "S value" are automatically displayed. Note that, for information that has already been entered, the information may be displayed automatically. As the S-value data, in addition to the "S-value", for example, "period 1" and "period 2" can be input (for example, input for rewriting is possible).

[0081] In the example of FIG. 12, screen E4 displays, as buttons that can be clicked or the like, a button F41 for confirming the screen contents (OK) and a button F42 for canceling the screen contents. When the button F41 or F42 is pressed, the request sending device A11 performs control to return to the screen E3.

[0082] (Step S16) The request source device A11 selects multiple pouring location data to be output to the mix plan creation request form. The selection of the pouring location data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S17. In this embodiment, the period for the S value is determined for each region and is assumed to be known by the requested contractors 21 to 23 (factories), so it is assumed that it will not be written in the request for preparation of the blending plan, but other configurations may be used.

[0083] <Example of concrete placement data selection screen> FIG. 13 is a diagram showing an example of a pouring location data selection screen E5 when creating a mix plan creation request according to the embodiment. A screen E5 shown in FIG. 13 is an example of a pouring location data selection screen. On screen E5, the message "Select pouring location data" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, screen E5 is displayed. Screen E5 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0084] For example, "Constructor name" and "Site name" are automatically displayed. Also, for example, a combination of "Pouring location", "Fc", and "S value" is automatically displayed. Note that for content that has already been entered, that content may be displayed automatically, for example. On the screen E5, check boxes F53a, F53b, and F53c are displayed for each pouring location data, which can be selected or not by clicking, etc. On the requesting device A11, the requesting user A1 can operate to set whether or not to check each of the check boxes F53a, F53b, and F53c (whether or not to select).

[0085] In the example of FIG. 13, screen E5 displays, as buttons that can be clicked or the like, a button F51 for confirming the screen contents (OK) and a button F52 for canceling the screen contents.

[0086] (Step S17) The request source device A11 starts the process of creating a blending plan creation request. The blending plan creation request is created, for example, by a requesting user A1 operating a requesting device A11. Then, the process proceeds to step S18.

[0087] (Step S18) The request source device A11 completes the blending plan creation request. Then, the processing of this flow ends.

[0088] <Example of a request for a blending plan> FIG. 14 is a diagram showing an example of a blending plan creation request E6 according to the embodiment. Here, the request for formulation plan creation E6 is the result of being electronically created by the requesting device A11 and then printed on paper by the printing device A12, and is a printed matter, but it does not necessarily have to be printed. The blending plan creation request form E6 is an example of a form. In this embodiment, the blending plan creation request E6 is sent from the requesting company 11 to the requested company 21 by facsimile, email, mail, or hand delivery, for example. The contents of the blending plan creation request E6 shown in FIG. 14 are an example for the purpose of explanation, and are not limited to this example.

[0089] <Creating a mix plan at the client> The processing flow shown in FIG. 3B will be described.

[0090] (Step S21) The requested user B1 receives the blending plan creation request E6 from the requesting company 11. Then, the process proceeds to step S22.

[0091] (Step S22) The requested user B1 creates a blending plan based on the received blending plan creation request E6. Here, the request destination user B1 performs the task of creating a blending plan by operating the request destination device B11, for example. Then, the process proceeds to step S23.

[0092] (Step S23) The blending plan is completed through the work of the requested user B1. Then, the processing of this flow ends.

[0093] <Example of a summary of a blending plan> 15A to 15F are diagrams showing schematic examples of blending plans E7a to E7f according to the embodiment, respectively. Here, the blending plans E7a to E7f are each the result of being electronically created by the requested device B11 and then printed on paper by the printing device B12, and are printed materials, but they do not necessarily have to be printed. The blending plans E7a to E7f are examples of forms. In this embodiment, a maximum of six mixture plans E7a to E7f are created by the requested user B1 at the requested contractor 21. For example, when the construction period is long, the requested contractor 21 may create six mixture plans E7a to E7f. In this embodiment, a case where six mixture plans E7a to E7f are created is shown. In this embodiment, the blending plans E7a to E7f are sent from the requested contractor 21 to the requesting contractor 11 by facsimile, email, mail, or hand delivery, for example.

[0094] In this embodiment, for ease of explanation, the examples of FIGS. 15A to 15F only show a portion of the blending plans E7a to E7f, and the other portions are omitted. In the mix plan E7a shown in FIG. 15A, the title "Ready-mixed concrete mix plan" is displayed at the top. In the top right corner of the blending plan E7a, the serial number "No. 0000000001", the date "April 1, 2024", the creating company "XX Co., Ltd." which corresponds to the requested contractor 21, the creating company's address "Tokyo...", and the name of the blending planner "XX ××" are displayed. In the mix plan E7a, the addressee for the contractor to whom it was submitted, "To: XX Construction Co., Ltd.", is displayed in the upper left corner.

[0095] Furthermore, the mix plan E7a displays the "Project name" (which includes the site name) as "XX Building New Construction Project," the "Location" as "△△1-2-3, XX-ku, Tokyo," the "Scheduled delivery date" as "April 1, 2024 to March 31, 2025," the "Applicable period of this mix" as "March 8 to June 15, September 24 to November 25 (standard mix)," and the "Concrete pouring location" (which includes the pouring location (range)) as "1st floor to 5th floor."

[0096] Furthermore, in the mix plan E7a, the names of the "mix design conditions" are listed as "normal," which is the "symbol for the type of concrete," "27," which is the "nominal strength," "15," which is the "slump or slump flow cm," "20," which is the "maximum dimension of coarse aggregate mm," and "N," which is the "symbol for the type of cement."

[0097] Here, the contents of the blending plan E7a continue further downwards, but in this embodiment, illustrations and detailed explanations of the contents thereafter will be omitted. Further, the following content may be displayed, for example, "materials used," "recipes," "remarks," and the like. For example, in a "mixing table," the mix may vary for each period (here, for each period of the mix plan) depending on the seasonal mix at each factory.

[0098] The blending plan E7b shown in FIG. 15B has some different content from the blending plan E7a. The mix plan E7b shown in Figure 15B displays the serial number "No. 0000000002," the "application period of this mix" of "June 16th to July 6th, September 8th to September 23rd (modified standard mix)," and the "nominal strength" of "27" under the "mix design conditions."

[0099] The blending plan E7c shown in FIG. 15C has some different contents compared to the blending plan E7a. The mix plan E7c shown in Figure 15C displays the serial number "No. 0000000003," the "application period of this mix" of "February 3rd to March 7th (modified standard mix)," and the "nominal strength" of the "mix design conditions" of "27."

[0100] The blending plan E7d shown in FIG. 15D has some different content from the blending plan E7a. The mix plan E7d shown in Figure 15D displays the serial number "No. 0000000004," the "application period of this mix" of "November 26th to December 10th (standard mix)," and the "nominal strength" of "30" under the mix design conditions.

[0101] The blending plan E7e shown in FIG. 15E has some different contents compared to the blending plan E7a. The mix plan E7e shown in Figure 15E displays the serial number "No. 0000000005," the "application period of this mix" of "July 7th to September 7th (modified standard mix)," and the "nominal strength" of "30" under the mix design conditions.

[0102] The blending plan E7f shown in FIG. 15F has some different content from the blending plan E7a. The mix plan E7f shown in Figure 15F displays the serial number "No. 0000000006," the "application period of this mix" of "December 11th to February 22nd (modified standard mix)," and the "nominal strength" of "30" under the mix design conditions.

[0103] Here, the blending plan E7a corresponds to an S value of 3 and a standard period. In addition, the mix plan E7b corresponds to S value = 3 and summer. In addition, the mix plan E7c corresponds to S value = 3 and winter season. In addition, the blending plan E7d corresponds to an S value of 6 and the standard period. In addition, the mix plan E7e corresponds to S value = 6 and summer. In addition, the mix plan E7f corresponds to S value = 6 and winter season. It is possible to identify when the S value is 3 and when the S value is 6 because the "call strength" value is different. The dates for each period are merely examples for the purpose of explanation, and are not limited to these examples, and various other forms may be used.

[0104] <Linking of the requester's blending plan> The processing flow shown in FIG. 4 will be described.

[0105] (Step S31) The requesting user A1 receives the blending plans E7a to E7f from the requested trader 21. Then, the process proceeds to step S32.

[0106] (Step S32) The requesting device A11 performs a process of reading each of the received blending plans E7a to E7f using OCR. Then, the process proceeds to step S33. Here, the reading process using OCR is performed, for example, by the requesting user A1 operating the requesting device A11 to have the blending plan E7a to E7f (e.g., paper documents or image data) read by the OCR of the OCR data acquisition unit A35 of the requesting device A11.

[0107] Here, in this embodiment, among the items read by OCR, the items that are used when linking to the pouring location but are not saved include the contractor, site name, pouring location, and nominal strength (in this embodiment, at least only pouring locations with an S value of 3 or 6 are required), but as another example, one or more of these may be saved. Furthermore, in this embodiment, among the items read by OCR, the items that are linked to the mix plan data and saved include the company name of the requested contractor 21 (in this embodiment, the factory name) and the read application period. In this embodiment, these items are used, for example, in searches by the requesting device A11. For example, when checking the day before, in order to send a mix plan to be poured to the factory the next day, it is possible to specify the factory and pouring date, and have the requesting device A11 identify a mix plan whose pouring date is within the application period and whose factory matches.

[0108] In general, the format for writing a mix plan is specified by JIS. In this embodiment, the requesting device A11 may, for example, store information about the description format of the blending plan in advance, and identify the content of the information of each area in the OCR data based on the description format.As another example, the requesting device A11 may, for example, analyze the meaning from the characters in the OCR data, and identify the content of the information of each area in the OCR data. The OCR data may be, for example, data in PDF format.

[0109] (Step S33) The requesting device A11 identifies the builder data corresponding to the builder name read by OCR. The request source device A11 identifies the site data corresponding to the read site name from under the identified builder data. The request source device A11 identifies data of a pouring location (range) corresponding to the read pouring location (range) from under the identified site data. Then, the process proceeds to step S34.

[0110] (Step S34) The requesting device A11 identifies, from the data of the identified pouring location (range), the S value data corresponding to the value obtained by subtracting Fc from the read nominal strength, or identifies the S value data corresponding to period 1 or period 2 in the read applicable period. Thereafter, the request source device A11 links the identified S value data with the blending plan data (in this embodiment, the OCR data of the blending plan). Then, the process proceeds to step S35.

[0111] (Step S35) The requesting device A11 stores the read company name (factory name in this embodiment) of the requested contractor 21 and the read application period as metadata for search purposes, linking them to the OCR data of the corresponding formulation plan. Then, the processing of this flow ends.

[0112] <Pouring location data editing screen> FIG. 16A is a diagram showing an example of a pouring location data editing screen according to the embodiment and an example of linking with a mix planning document. A screen E8 shown in FIG. 16A is an example of a pouring location data editing screen. On screen E8, the message "Edit pouring location data" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, a screen E8 is displayed. The screen E8 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0113] For example, "Constructor name" and "Site name" are automatically displayed. Also, for example, "Pouring location," "Pouring location (for search)," "Fc (design standard strength)," and "Structural strength correction value" are automatically displayed. Also, for example, "Period 1" and "Period 2" where the "S value" is "3," "Period 1" and "Period 2" where the "S value" is "6," "Slump, flow," "Bone size," and "Cement type" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. Here, in the example of Fig. 16A, the contents of these items are the same as, for example, the contents of screen E3 in the example of Fig. 11. In the example of Fig. 16A, the information entered on screen E3 in the example of Fig. 11 is displayed.

[0114] In the example of FIG. 16A, buttons F84 to F85 for editing the S value period are displayed on screen E8, and the S value period can also be edited manually (by operation) by requesting user A1. In the example of FIG. 16A, screen E8 displays, as buttons that can be clicked or the like, a button F81 for confirming the screen contents (OK) and a button F82 for canceling the screen contents.

[0115] Figure 16A shows a schematic diagram in which the OCR data of six blending plans G1 to G6 is linked to a state in which the "S value" is "3" (corresponding S value data), and the OCR data of six blending plans G11 to G16 is linked to a state in which the "S value" is "6" (corresponding S value data).

[0116] FIG. 16B is a diagram schematically illustrating an example of metadata included in the linked data of the blending plans G1 to G6 according to the embodiment. In the example of FIG. 16B, examples of metadata linked to the OCR data of each of the blending plans G1 to G6 are shown in the respective columns of numbers 1 to 6. Note that numbers 1 to 6 are for the convenience of explanation and are not limited to these. As an example, the OCR data for mix plan G1 is linked with the following metadata: "nominal strength" is "27 (S value = 3)", "period 1" is the applicable period "3 / 8 - 6 / 15", "period 2" is the applicable period "9 / 24 - 11 / 25", and "factory" is "Factory A". As another example, the OCR data for Mixing Plan G5 is associated with the following metadata: "Nominal Strength" is "27 (S value = 3)", "Period 1" is the applicable period, which is "6 / 16~7 / 6", "Period 2" is the applicable period, which is "9 / 8~9 / 23", and "Factory" is "Factory B".

[0117] Here, the other blending plans (blending plans G2, G3, G4, G6) are also as shown in Figure 16B. In this embodiment, the three mixture plans G1 to G3 all relate to "Factory A," and relate to the "standard season," "summer," and "winter season," respectively. In this embodiment, the other three blending plans G4 to G6 all relate to "Factory B," and relate to the "standard season," "summer," and "winter," respectively.

[0118] FIG. 16C is a diagram schematically illustrating an example of metadata included in the linked data of the blending plans G11 to G16 according to the embodiment. In the example of FIG. 16C, examples of metadata linked to the OCR data of each of the blending plans G11 to G16 are shown in the respective columns of numbers 11 to 16. Note that numbers 11 to 16 are for the convenience of explanation and are not limited to these. As an example, the OCR data for Mixing Plan G11 is associated with the following metadata: "Nominal Strength" is "30 (S value = 6)", "Period 1" is the applicable period, "11 / 26 - 12 / 10", "Period 2" is not applicable, and "Factory" is "Factory A". As another example, the OCR data for Mixing Plan G16 is linked with the following metadata: "Nominal Strength" is "30 (S value = 6)", "Period 1" is "12 / 11~2 / 22", "Period 2" is not applicable, and "Factory" is "Factory B".

[0119] Here, the other blending plans (blending plans G12, G13, G14, G15) are also as shown in Figure 16C. In this embodiment, the three mixture plans G11 to G13 all relate to "Factory A," and relate to the "standard season," "summer," and "winter season," respectively. In this embodiment, the other three mixture plans G14 to G16 all relate to "Factory B," and relate to the "standard season," "summer," and "winter," respectively.

[0120] <Creation of a construction plan by the client> The processing flow shown in FIG. 5 will be described.

[0121] (Step S51) The request source device A11 selects the builder data and the site data. The selection of the contractor data and the site data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S52.

[0122] <Example of the contractor and site data selection screen> FIG. 17 is a diagram showing an example of a contractor and site data selection screen according to the embodiment. A screen E9 shown in FIG. 17 is an example of a contractor and site data selection screen. On screen E9, the message "Constructor and site data selection" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, screen E9 is displayed. Screen E9 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0123] For example, "Constructor name" and "Site name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. In the example of FIG. 17, "XX Construction Co., Ltd.", "□□ Construction Co., Ltd.", and "△△ Group Co., Ltd." are displayed as "Contractor Names." In the example of Figure 17, "XX Building Construction" and "△△ Tower Construction" are displayed as the "site names" of "XX Construction Co., Ltd." In the example of Figure 17, "XX Building Construction" is selected.

[0124] In the example of FIG. 17, the screen E9 displays, as buttons that can be clicked or the like, a button F91 for confirming the screen contents (OK) and a button F92 for canceling the screen contents. When the button F91 is pressed, the request source device A11 performs control to transition to a screen E10 shown in FIG.

[0125] (Step S52) The request source device A11 inputs the playing plan data. The playing plan data is input, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S53.

[0126] <Example of construction plan data editing screen> FIG. 18 is a diagram showing an example of a playing plan data editing screen according to the embodiment. A screen E10 shown in FIG. 18 is an example of a playing plan data editing screen. On screen E10, the words "Editing playing plan data" are displayed at the top.

[0127] In this embodiment, the screen E9 shown in FIG. 17 and the screen E10 shown in FIG. 18 are in a higher-order and lower-order relationship. Specifically, when the requesting user A1 selects a set of "contractor name" and "site name" (in this example, "XX Construction Co., Ltd." and "XX Building New Construction Project") on screen E9 and presses the "OK" button F91, the requesting device A11 controls the screen to transition to screen E10 in Figure 18.

[0128] For example, "Constructor name" and "Site name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. In the example of FIG. 18, "XX Construction Co., Ltd." is displayed as the "Constructor Name." In the example of FIG. 18, "XX Building New Construction" is displayed as the "site name."

[0129] Furthermore, the screen E10 has columns for "Pouring location," "Pouring date," "Time," "Quantity," "Pouring location (range)," and "Name."

[0130] In the example of FIG. 18, screen E10 displays, as buttons that can be clicked or the like, a button F101 for confirming the screen contents (OK) and a button F102 for canceling the screen contents.

[0131] (Step S53) The request source device A11 identifies data of a pouring location (range) having a search pouring location that corresponds to the input pouring location (specific location) from the site data of the selected "site name". In the example of FIG. 18, an arrow X12 is shown to schematically represent such automatic conversion, but the arrow X12 does not necessarily have to be displayed. Then, the process proceeds to step S54.

[0132] Here, in this embodiment, when the requesting user A1 inputs data of a pouring location (specific location) into "Pouring location", the requesting device A11 automatically saves data of "Pouring location (range)" that has a search pouring location that matches the content. Here, we have shown a case where a pouring location (specific location) is converted into a pouring location (range) via a search pouring location, but in this embodiment, the pouring location (specific location) and the pouring location (range) may be directly linked.

[0133] (Step S54) The requesting device A11 identifies the S value for the applicable period corresponding to the input "pouring date" from the data for the identified pouring location (range), and identifies the mix by setting the nominal strength as (Fc + S value). In this example, Fc=24, which may be stored in advance in the request source device A11, for example. In the example of FIG. 18, an arrow X11 is shown to schematically represent such automatic conversion, but the arrow X11 does not necessarily have to be displayed. Then, the process proceeds to step S55.

[0134] Here, in this embodiment, when the requesting user A1 inputs pouring date data in the "Pouring Date", the requesting device A11 automatically saves the nominal strength according to the content as the "Nominal Type".

[0135] (Step S55) The requesting device A11 creates a casting plan. Then, the process proceeds to step S56.

[0136] <Example of construction plan data selection screen> FIG. 19 is a diagram showing an example of a playing plan data selection screen according to the embodiment. A screen E11 shown in FIG. 19 is an example of a playing plan data selection screen. On screen E11, the message "Select playing plan data" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, a screen E11 is displayed. The screen E11 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0137] For example, "Constructor name" and "Site name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. In the example of FIG. 19, "XX Construction Co., Ltd." is displayed as the "Constructor Name." In the example of FIG. 19, "XX Building New Construction" is displayed as the "site name."

[0138] In addition, screen E11 has multiple columns corresponding to "Pouring date," "Time," "Pouring location," "Quantity," "Name," "Requesting factory," and "Shipping factory." In the example of Fig. 19, check boxes F113a to F113d are displayed that allow the user to specify whether or not to select each of the plurality of columns of construction plan data by clicking, etc. The requesting user A1 can operate the requesting device A1 to set whether or not to check each of the check boxes F113a to F113d (whether or not to select).

[0139] In the example of FIG. 19, the screen E11 displays, as buttons that can be clicked or the like, a button F111 for confirming the screen contents (OK) and a button F112 for canceling the screen contents. When the button F111 is pressed, the request sending device A11 performs control to create a layout plan corresponding to each of the one or more fields selected by the check boxes F113a to F113d.

[0140] (Step S56) The requesting device A11 completes the casting plan. Then, the processing of this flow ends.

[0141] <Example of a pitching plan> FIG. 20 is a diagram showing an example of a hitting plan E12 according to the embodiment. Here, the laying plan E12 is the result of being electronically created by the requesting device A11 and then printed on paper by the printing device A12, and is a printed matter, but it does not necessarily have to be printed. The construction plan E12 is an example of a form.

[0142] <Creating a concrete pouring request form at the requesting party> The processing flow shown in FIG. 6A will be described.

[0143] (Step S71) The requesting device A11 selects the playing plan data. The selection of the playing plan data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S72.

[0144] <Example of construction plan data selection screen> FIG. 21 is a diagram showing an example of a playing plan data selection screen according to the embodiment. A screen E13 shown in FIG. 21 is an example of a playing plan data selection screen. On screen E13, the message "Select playing plan data" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, the screen E13 is displayed. The screen E13 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0145] For example, "Constructor name" and "Site name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. In addition, screen E13 has multiple columns corresponding to "Pouring date," "Time," "Pouring location," "Quantity," "Name," "Requesting factory," and "Shipping factory." On the screen E13, it is possible to specify whether or not to select the playing plan data for each of these multiple fields.

[0146] In the example of FIG. 21, the screen E13 displays, as buttons that can be clicked or the like, a button F131 for confirming the screen contents (OK) and a button F132 for canceling the screen contents. When the button F131 is pressed, the request source device A11 performs control to create a concrete pouring request corresponding to each of the one or more selected fields.

[0147] (Step S72) When creating a pouring request, the requesting device A11 searches for factories that have created mix plans for the applicable period corresponding to the pouring date for which the pouring request is made, based on metadata, from among the mix plans linked to the S-value data under the pouring location data (here, data on the pouring location (range)), which is the parent data of the selected pouring plan data, and displays factories that can be requested as selectable factories. Then, the process proceeds to step S73. The request source device A11 may select a plurality of factories from among the displayed factories to which concrete pouring is to be requested. In addition, the pouring date when planning the pouring plan may differ from the pouring date when requesting the pouring.

[0148] <Example of the casting request factory selection screen> FIG. 22 is a diagram showing an example of a casting request factory selection screen according to the embodiment. A screen E14 shown in FIG. 22 is an example of a casting request factory selection screen. On screen E14, the top displays "Select a factory to request pouring."

[0149] In this embodiment, the screen E13 shown in FIG. 21 and the screen E14 shown in FIG. 22 are in a higher-order and lower-order relationship. Specifically, when the requesting user A1 selects one column (in this example, the top column) on screen E13 and presses the "OK" button F131, the requesting device A11 controls the screen to transition to screen E14 of Figure 22.

[0150] For example, one or more selectable "factory names" are automatically displayed. In the example of FIG. 22, "Factory A," "Factory B," "Factory C," and "Factory D" are displayed as selectable "Factory Names." Furthermore, the screen E14 displays check boxes F143a to F143d that can be used to select or not select each factory name by clicking, etc. The requesting user A1 can operate the requesting device A11 to set whether or not to check each of the check boxes F143a to F143d (whether or not to select).

[0151] On the screen E14, a button F144 for referring to the blending plan is displayed. When the button F144 is pressed, the requesting device A11 displays the contents of the blending plan created by one or more factories selected by the check boxes F143a to F143d, allowing the requesting user A1 to check the contents of the blending plan displayed.

[0152] In the example of FIG. 22, the screen E14 displays, as buttons that can be clicked or the like, a button F141 for confirming the screen contents (OK) and a button F142 for canceling the screen contents. When the button F141 is pressed, the request source device A11 performs control to create a concrete pouring request corresponding to each of the one or more fields selected by the check boxes F143a to F143d.

[0153] At this stage, blending plans have been obtained from each relevant factory. In the example of Figure 22, a blending plan is linked to each factory.

[0154] (Step S73) The request source device A11 creates a concrete pouring request. The concrete pouring request is created, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S74.

[0155] (Step S74) The request source device A11 completes the concrete pouring request. Then, the processing of this flow ends.

[0156] <Example of concrete pouring request> FIG. 23 is a diagram showing an example of a concrete pouring request E15 according to the embodiment. Here, the concrete pouring request E15 is the result of being electronically created by the requesting device A11 and then printed on paper by the printing device A12, and is a printed matter, but it does not necessarily have to be printed. Concrete pouring request form E15 is an example of a form. In this embodiment, the concrete pouring request E15 is sent from the requesting contractor 11 to the requested contractor 21 by facsimile, e-mail, mail, or hand delivery, for example.

[0157] Normally, the concrete pouring request form E15 is submitted to multiple contractors (three contractors 21 to 23 in the example of Figure 1). The reason for this is that if only one contractor is requested, there is a possibility that that contractor may not be able to ship the work. If two or more requested contractors are able to ship the work, the work is shipped by one arbitrarily selected contractor.

[0158] <Creating a concrete pouring request response at the client> The processing flow shown in FIG. 6B will be described.

[0159] (Step S81) The requested user B1 receives the concrete pouring request E15 from the requesting contractor 11. Then, the process proceeds to step S82.

[0160] (Step S82) The requested user B1 creates a concrete pouring request response as a response to the received concrete pouring request E15. Here, the request destination user B1 performs the task of creating a pouring request response by operating the request destination device B11, for example. Then, the process proceeds to step S83.

[0161] (Step S83) The concrete pouring request response is completed through the work of the requested user B1. Then, the processing of this flow ends.

[0162] <Response to concrete pouring request> Here, the pouring request response is the result of being electronically created by the request receiving device B11 and then printed on paper by the printing device B12, and is a printed matter, but it does not necessarily have to be printed. In this embodiment, the concrete pouring request response is sent, for example, from the requested contractor 21 to the requesting contractor 11 by facsimile, e-mail, mail, or hand delivery.

[0163] <Decision of the pouring plant by the client> The processing flow shown in FIG. 7 will be described.

[0164] (Step S91) The request source device A11 receives the pouring request response. Then, the process proceeds to step S92.

[0165] (Step S92) Based on the concrete pouring request response, the request source device A11 inputs the name of the factory to which the request is actually made as the concrete pouring factory (in this example, "shipping factory") in the concrete pouring plan data. Then, this flow ends.

[0166] <Preparation of confirmation documents from the requesting party the day before> The processing flow shown in FIG. 8 will be described.

[0167] (Step S111) The requesting device A11 selects the playing plan data. The selection of the playing plan data is performed, for example, by the requesting user A1 operating the requesting device A11. Then, the process proceeds to step S112.

[0168] <Example of construction plan data selection screen> FIG. 24 is a diagram showing an example of a playing plan data selection screen according to the embodiment. A screen E16 shown in FIG. 24 is an example of a playing plan data selection screen. On screen E16, the message "Select playing plan data" is displayed at the top. In this embodiment, when a predetermined operation is performed by the requesting user A1 on the requesting device A11, the screen E16 is displayed. The screen E16 may be transitioned from any of the screens shown in this embodiment, or may be newly displayed.

[0169] For example, "Constructor name" and "Site name" are automatically displayed. Note that, for content that has already been entered, the content may be displayed automatically, for example. In addition, screen E16 has multiple columns corresponding to "Pouring date," "Time," "Pouring location," "Quantity," "Name," "Requesting factory," and "Shipping factory." Here, the "request factory" may include multiple factories, but the "shipping factory" includes only one factory if it is determined. On the screen E16, it is possible to specify whether or not to select the playing plan data for each of these multiple fields.

[0170] In the example of FIG. 24, the screen E16 displays, as buttons that can be clicked or the like, a button F161 for confirming the screen contents (OK) and a button F162 for canceling the screen contents. When the button F161 is pressed, the requesting device A11 performs control to create a day-before confirmation document corresponding to each of the one or more selected fields.

[0171] (Step S112) The requesting device A11 identifies one mix plan by searching from the metadata for a mix plan (here, mix plan data) that was created by the "shipping factory", which is the pouring factory, and has an applicable period that corresponds to the "pouring date" of the pouring plan data, from among the mix plans (here, mix plan data) that are linked to the S value data under the pouring location data (here, pouring location (range) data), which is the parent data of the selected pouring plan data. Then, the process proceeds to step S113.

[0172] (Step S113) In the requesting device A11, the previous day confirmation document is completed and one blending plan is identified. Then, the processing of this flow ends.

[0173] <Example of documents to confirm the day before> FIG. 25 is a diagram showing an example of the previous day confirmation E17 according to the embodiment. Here, the previous day's confirmation E17 is the result of being electronically created by the requesting device A11 and then printed on paper by the printing device A12, and is a printed matter, but it does not necessarily have to be printed. The previous day confirmation form E17 is an example of a form. In this embodiment, the previous day confirmation E17 and the identified blending plan are sent, for example, by fax, email, mail, or hand delivery from the requesting company 11 to the requested company 21.

[0174] As described above, the management system 1 according to this embodiment can perform all the processes related to requests for ready-mix concrete.

[0175] <Conversion between pouring location (range) and pouring location (specific location)> In the background art, when creating a pouring plan (the factory has not yet been decided at this stage), it is desirable to identify the Fc corresponding to the pouring location and the S value corresponding to the pouring date, and then determine the nominal strength as (Fc + S value). However, in the background art, for example, if the name of the pouring location in the pouring location data is a string indicating the range of the pouring location (e.g., "1st floor to 5th floor"), and the pouring location when creating the pouring plan is part of that range (e.g., "3rd floor"), it is not possible to identify such a pouring location (here, a specific location). Conversely, if the pouring location (here, a specific location) can be identified, it is possible to identify an S value whose pouring date falls within the period of the S value data subordinate to the pouring location data. In the past, it was customary for designers to describe pouring locations as ranges (for example, "1st floor to 5th floor"). For example, in the past, pouring locations for ready-mixed concrete were sometimes described as ranges, making it difficult to clearly identify individual locations within the range.

[0176] Therefore, in the request source device A11 according to this embodiment, when the name of the concrete pouring location in the concrete pouring location data indicates a range, the character string included in the range is divided according to a predetermined rule (association), and the division result is registered as the concrete pouring location (specific location). Also, in this embodiment, such a concrete pouring location (specific location) is registered and used as a key (search keyword).

[0177] Here, a predetermined rule (association) for performing such division may be registered (stored) in advance in the request source device A11, for example. As another example, the requesting device A11 may be controlled to add a rule (association) manually input by the requesting user A1 as a predetermined rule (association) for such division. In other words, the requesting device A11 may store the rule (association) manually input by the requesting user A1, and if there is a character string of a pouring location (range) that fits the rule (association), the divided character string may be converted into a pouring location (specific location) according to the rule (association).

[0178] In addition, the process of adding a rule (association) manually input by the operation of the requesting user A1 may be performed, for example, when a new rule is input by the operation of the requesting user A1, or when the content once displayed by the requesting device A11 is corrected (changed) by the operation of the requesting user A1, or it may be performed in both of these cases. As a specific example, when the requesting device A11 displays an error message regarding the conversion between the pouring location (range) and the pouring location (specific location) (or when no such error message is displayed), if the requesting user A1 inputs corrected information (association information), the requesting device A1 may store the corrected information and use it from the next time onwards. In addition, the input of information by the requesting user A1 may be performed, for example, by the requesting device A11 displaying a list of multiple pieces of selectable information, and the requesting user A1 selecting one piece of information from the list.

[0179] Such a rule (association) associates, for example, the name of the original pouring location before division (e.g., a string representing a range) with a combination of strings after division (e.g., strings representing multiple specific locations). In addition, the requesting device A11 may convert from a pouring location (range) to a pouring location (specific location), or from a pouring location (specific location) to a pouring location (range), or may perform both of these conversions.

[0180] Therefore, the request source device A11 according to this embodiment can clearly identify individual locations included in a range from the pouring locations represented by the range. In the request source device A11 of this embodiment, for example, when creating a pouring plan, Fc can be determined by identifying the pouring location (range) to which the specified pouring location (specific location) corresponds, and the nominal strength can be determined as (Fc + S value) by identifying S value data including the specified pouring date. In addition, the pouring location (range) and the pouring location (specific location) may be associated with each other, for example, via a search keyword for the pouring location data.

[0181] <About reading blending plans using OCR> In the background art, it was desirable that the day before pouring (at this stage the factory was determined) the factory that would be shipping the concrete should send a mix plan that corresponds to the mix that would actually be shipped from the mix plans that the factory had already submitted as a confirmation document for the day before. However, there are cases where there are hundreds of mix plans associated with a single site, and it can be time-consuming to identify the mix plan that corresponds to the actual pouring location, pouring date, and factory.In addition, when identifying the mix plan in question, there is a possibility that the wrong mix plan may be selected by mistake. In the past, it was customary to exchange mix plans, etc., by facsimile, etc. For example, in the past, there were cases where many mix plans for ready-mixed concrete were created, and it was sometimes difficult to identify one that met the specified conditions from among the many mix plans.

[0182] Therefore, the requesting device A11 in this embodiment reads the mix plan using OCR, and identifies the hierarchy of contractor data, site data, and pouring location data from the contractor name, site name, and pouring location, from top to bottom. In addition, the requesting device A11 subtracts the Fc of the pouring location data from the nominal strength read by OCR to determine the S value, and links the corresponding mix plan data (e.g., a PDF file) to the S value data. Here, since the pouring location described in the mix plan is a range rather than a specific location, when identifying the pouring location data in the system from the pouring location in the mix plan, no conversion is performed between the pouring location (range) and the pouring location (specific location), but rather the pouring location data that matches the pouring location in the mix plan is searched for and identified. Note that there may be multiple mix plans (e.g., standard season, summer season, winter season) for the same factory, the same pouring location, and the same nominal strength (same S value). The requesting device A11 registers metadata using the factory name and application period read by OCR as keys (search keywords) linked to the corresponding formulation plan data (e.g., PDF file).

[0183] In the requesting device A11 of this embodiment, when identifying the mix plan that corresponds to the mix that will actually be shipped from the mix plans that the factory has already submitted as a confirmation document for the day before pouring to the factory that will be shipping, the requesting user A1 selects the contractor data and site data from top to bottom, and specifies the pouring location, pouring date, and shipping factory. In the request source device A11, the pouring location data and the S value data are identified by utilizing the conversion between the pouring location (range) and the pouring location (specific location) described above.

[0184] Therefore, the request source device A11 according to this embodiment can identify a blending plan that meets predetermined conditions from among a large number of blending plans. In the request source device A11 according to this embodiment, for example, it is possible to identify one mix plan in which the specified factory name corresponds to the factory name linked to the mix plan data (e.g., PDF file) and the specified pouring date falls within the applicable period linked to the mix plan data (e.g., PDF file). In this way, in this embodiment, it is possible to identify one mix plan using the shipping factory and pouring date as keys.

[0185] In the requesting device A11 according to this embodiment, for example, a blending plan is linked to the S-value data, and the blending plan is linked to the factory name (for example, as metadata), so that, for example, the requesting user A1 or the requesting device A11 can refer to this linking information to ascertain the names of factories that have submitted blending plans and the names of factories that have not yet submitted blending plans. This allows the requesting user A1 or the requesting device A11 to, for example, prompt factories that have not yet submitted blending plans to submit them.

[0186] In addition, when a technology is applied that reads the mix plan using OCR and stores the mix plan data (and in this embodiment, metadata), it is not necessarily necessary to apply a technology that converts between pouring location (range) and pouring location (specific location). However, when the mix plan is read using OCR and the mix plan data (and in this embodiment, metadata) is saved, and the overall processing flow as in this embodiment is performed, conversion between pouring location (range) and pouring location (specific location) is also used.

[0187] In this way, by applying both the technology for converting between pouring locations (range) and pouring locations (specific locations) and the technology for reading the mix plan using OCR, it is possible to efficiently carry out the overall processing flow as in this embodiment.

[0188] <Other configuration examples> As another example of configuration, when technology is applied to convert between pouring locations (range) and pouring locations (specific locations), it is also possible to configure the system without applying technology to read the mix plan using OCR. In such a configuration, for example, the requesting device A11 and the requested device B11 may communicate via a network to exchange (transmit and receive) electronic information about various documents including blending plans. In this case, for example, the functions of the printing device A12 of the requesting company 11, the OCR function of the requesting device A11, and the printing device B12 of the requested company 21 may not be provided.

[0189] [Regarding the above embodiment] A program for implementing the functions of any of the components of any of the above-described devices may be recorded on a computer-readable recording medium and loaded into a computer system for execution. The term "computer system" as used herein includes hardware such as an operating system or peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and compact discs (CDs) or read-only memories (ROMs), as well as storage devices such as hard disks built into computer systems. The term "computer-readable recording medium" also includes devices that retain a program for a certain period of time, such as volatile memory within a computer system that acts as a server or client when a program is transmitted over a network such as the Internet or a communication line such as a telephone line. Such volatile memory may be, for example, random access memory (RAM). The recording medium may also be, for example, a non-transitory recording medium.

[0190] The above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network such as the Internet or a communication line such as a telephone line. The above program may also be one that realizes part of the above-mentioned functions. Furthermore, the above program may be a so-called differential file that can realize the above-mentioned functions in combination with a program already recorded in a computer system. A differential file may also be called a differential program.

[0191] Furthermore, the functions of any of the components in any of the above-described devices may be implemented by a processor. For example, each process in the embodiments may be implemented by a processor operating based on information such as a program and a computer-readable recording medium storing information such as the program. Here, the functions of each unit of the processor may be implemented by, for example, individual hardware, or may be implemented by integrated hardware. For example, the processor may include hardware, and the hardware may include at least one of a circuit for processing digital signals and a circuit for processing analog signals. For example, the processor may be configured using one or more circuit devices mounted on a circuit board, or one or both of one or more circuit elements. An integrated circuit (IC) or the like may be used as the circuit device, and a resistor or a capacitor may be used as the circuit element.

[0192] Here, the processor may be, for example, a CPU. However, the processor is not limited to a CPU, and various types of processors such as a GPU (Graphics Processing Unit) or a DSP (Digital Signal Processor) may be used. The processor may also be, for example, a hardware circuit such as an ASIC (Application Specific Integrated Circuit). The processor may also be, for example, composed of multiple CPUs, or may be, for example, composed of a hardware circuit such as a multiple ASIC. The processor may also be, for example, composed of a combination of multiple CPUs and a hardware circuit such as a multiple ASIC. The processor may also include, for example, one or more of an amplifier circuit or a filter circuit that processes analog signals.

[0193] The embodiments of this disclosure have been described in detail above with reference to the drawings, but the specific configuration is not limited to this embodiment, and includes designs within the scope that do not deviate from the gist of this disclosure.

[0194] [First Note] (Configuration example 1-1) to (Configuration example 1-7) are shown.

[0195] (Configuration Example 1-1) A storage unit that stores association information that associates pouring location range information that represents the pouring location of fresh concrete as a range with pouring location individual location information that represents the pouring location as an individual location; A control unit that converts the pouring location range information into the pouring location individual location information based on the association information; An information processing device comprising:

[0196] Therefore, the information processing device can clearly identify individual locations included in a range from the casting locations represented by the range. In this embodiment, the request source device A11 is an example of an information processing device. In addition, in this embodiment, information on the pouring location (range) is an example of pouring location range information, and information on the pouring location (specific location) is an example of pouring location individual location information. In this embodiment, the control unit A36 is an example of a control unit, and the storage unit A34 is an example of a storage unit.

[0197] (Configuration example 1-2) The control unit identifies the pouring location range information having a range including the pouring location individual location information, The information processing device according to (Configuration Example 1-1).

[0198] Therefore, in an information processing device, by identifying pouring location range information from individual pouring location information, it is possible to identify, for example, pouring location range information corresponding to individual pouring location information from multiple pouring location range information.

[0199] (Configuration Example 1-3) an input unit for inputting information relating to the association information in response to an operation performed by a user; the control unit updates the association information based on the information input by the input unit. The information processing device according to (Configuration Example 1-1) or (Configuration Example 1-2).

[0200] Therefore, in the information processing device, for example, not only can the predetermined association information be used, but the association information can also be updated with the content modified by the user. In this embodiment, the requesting user A1 is an example of a user. In this embodiment, the input unit A31 is an example of an input unit.

[0201] (Configuration Example 1-4) The control unit converts the pouring location range information into the pouring location individual location information, and then controls to display the converted pouring location individual location information. The information processing device according to any one of (Configuration Example 1-1) to (Configuration Example 1-3).

[0202] Therefore, by displaying individual pouring location information converted from pouring location range information in an information processing device, the user can grasp the individual pouring locations, and this information can also be used as a search key, etc.

[0203] (Configuration Example 1-5) A storage unit is provided for storing association information that associates pouring location range information, which represents a pouring location of fresh concrete as a range, with pouring location individual location information, which represents the pouring location as an individual location. Information processing device.

[0204] Therefore, the information processing device can utilize such correspondence information, and for example, from a pouring location represented by a range, it can clearly identify individual locations included in the range.

[0205] It is also possible to provide a method of processing performed by an information processing device. (Configuration Example 1-6) The information processing device Pouring location range information representing the pouring location of fresh concrete as a range and individual pouring location information representing the pouring location as an individual location are stored in a storage unit that stores correspondence information that associates the pouring location range information with the individual pouring location information. Based on the correspondence information, the pouring location range information is converted into the individual pouring location information. Information processing methods.

[0206] Therefore, the information processing method makes it possible to clearly identify individual locations included in a range from the casting locations represented by the range.

[0207] It is also possible to provide a program that is executed by a computer (computer program). (Configuration Example 1-7) On the computer, A program for realizing the function of converting pouring location range information, which represents the pouring location of fresh concrete as a range, into pouring location individual location information, based on correspondence information stored in a memory unit that stores correspondence information that corresponds between pouring location range information, which represents the pouring location of fresh concrete as a range, and pouring location individual location information, which represents the pouring location as an individual location.

[0208] Therefore, the program can clearly identify individual locations included in a range of pouring locations represented by the range.

[0209] [Second Note] (Configuration example 2-1) to (Configuration example 2-6) are shown.

[0210] (Configuration Example 2-1) A control unit that links S-value data including an S-value and an application period related to pouring of ready-mixed concrete with mix plan data generated by reading the mix plan of the ready-mixed concrete by OCR; A storage unit that stores linking information that links the S value data and the blending plan data; An information processing device comprising:

[0211] Therefore, the information processing device can identify a blending plan that meets predetermined conditions from among a large number of blending plans. In this embodiment, the control unit A36 is an example of a control unit, and the storage unit A34 is an example of a storage unit.

[0212] (Configuration Example 2-2) The mix plan includes the name of the contractor, the name of the site, the pouring location, and the nominal strength. The control unit performs at least one of the following processes: a process of identifying Fc based on the contractor name, the site name, and the casting location among the S-value data corresponding to the contractor name, the site name, and the casting location, and identifying the S-value data corresponding to the value obtained by subtracting Fc from the nominal strength; or a process of identifying the S-value data corresponding to the applicable period among the S-value data corresponding to the contractor name, the site name, and the casting location. The information processing device according to (Configuration Example 2-1).

[0213] Therefore, the information processing device can identify the S value data that links to the data in the blending plan. Here, the contractor name, site name, pouring location, and nominal strength in the mix plan may each be written using their original names, or may be written using other names as long as they are identifiable.

[0214] (Configuration Example 2-3) The blending plan includes the name of the factory, The control unit links the blending plan data with attribute data including the factory name and the application period, The linking information includes a link between the blending plan data and the attribute data, The information processing device according to (Configuration Example 2-2).

[0215] Therefore, by providing attribute data in an information processing device, it is possible to perform searches and the like using the attribute data. Here, the factory name in the blending plan may be written using the name as is, or may be written using another name as long as it is identifiable.

[0216] (Configuration Example 2-4) An input unit for inputting information for selecting the playing plan data, The control unit identifies the S-value data corresponding to the selected pouring plan data based on the linking information, and identifies one of the mixture plan data that is linked to the identified S-value data, has the same factory name included in the pouring plan data, and has a pouring date included in the pouring plan data that falls within the applicable period. The information processing device according to (Configuration Example 2-3).

[0217] Therefore, in an information processing device, for example, when there are multiple blending plans, it is possible to identify one blending plan that corresponds to the pouring plan data from among these multiple blending plans. In this embodiment, the input unit A31 is an example of an input unit.

[0218] It is also possible to provide a method of processing performed by an information processing device. (Configuration Example 2-5) The information processing device S-value data including the S-value and application period related to the pouring of ready-mixed concrete is linked to mix plan data generated by reading the mix plan of the ready-mixed concrete using OCR, Linking information linking the S value data and the blending plan data is stored in a storage unit. Information processing methods.

[0219] It is also possible to provide a program that is executed by a computer (computer program).

[0220] Therefore, the information processing method can identify a blending plan that meets specified conditions from among a large number of blending plans. (Configuration Example 2-6) On the computer, A function for linking S-value data including the S-value and application period related to pouring of ready-mixed concrete with mix plan data generated by reading the mix plan of the ready-mixed concrete by OCR; A function of storing linking information linking the S value data and the blending plan data in a storage unit; A program to achieve this.

[0221] Therefore, the program can identify a blending plan that meets specified conditions from among a large number of blending plans. [Explanation of symbols]

[0222] 1...Management system, 11...Requesting contractor, 21-23...Requested contractor, A1...Requesting user, A11...Requesting device, A12, B12...Printing device, A31...Input unit, A32...Output unit, A33...Communication unit, A34...Memory unit, A35...OCR data acquisition unit, A36...Control unit, A111...Pouring location conversion control unit, A112...Data linking control unit, B1...Requested user, B11...Requested device, E1-E5, E8-E11, E13-E14, E16...Screen, E6...Request for mixture plan creation, E7a-E7f, G1 ~G6, G11~G16...mixing plan, E12...pouring plan, E15...pouring request, E17...confirmation form the day before, F11~F15, F21~F25, F31~F35, F41~F42, F51~F52, F81~F82, F84~F85, F91~F92, F101~F102, F111~F112, F131~F132, F141~F142, F144, F161~F162...buttons, F53a~F53c, F113a~F113d, F143a~F143d...checkboxes, T1...table

Claims

1. A control unit that links S-value data including an S-value and an application period related to pouring of ready-mixed concrete with mix plan data generated by reading the mix plan of the ready-mixed concrete by OCR; A storage unit that stores linking information that links the S value data and the blending plan data; An information processing device comprising:

2. The mix plan includes the name of the contractor, the name of the site, the pouring location, and the nominal strength. The control unit performs at least one of the following processes: a process of identifying Fc based on the contractor name, the site name, and the casting location among the S-value data corresponding to the contractor name, the site name, and the casting location, and identifying the S-value data corresponding to the value obtained by subtracting Fc from the nominal strength; or a process of identifying the S-value data corresponding to the applicable period among the S-value data corresponding to the contractor name, the site name, and the casting location. The information processing device according to claim 1 .

3. The blending plan includes the name of the factory, The control unit links the blending plan data with attribute data including the factory name and the application period, The linking information includes a link between the blending plan data and the attribute data, The information processing device according to claim 2 .

4. An input unit for inputting information for selecting the playing plan data, The control unit identifies the S-value data corresponding to the selected pouring plan data based on the linking information, and identifies one of the mixture plan data that is linked to the identified S-value data, has the same factory name included in the pouring plan data, and has a pouring date included in the pouring plan data that falls within the applicable period. The information processing device according to claim 3 .

5. The information processing device S-value data including the S-value and application period related to pouring of ready-mixed concrete is linked to mix plan data generated by reading the mix plan of the ready-mixed concrete by OCR, Linking information linking the S value data and the blending plan data is stored in a storage unit. Information processing methods.

6. On the computer, A function of linking S-value data including the S-value and application period related to pouring of ready-mixed concrete with mix plan data generated by reading the mix plan of the ready-mixed concrete by OCR; A function of storing linking information linking the S value data and the blending plan data in a storage unit; A program to achieve this.

Images