Material management system and material management method

Abstract

To improve the efficiency of quality control and to improve productivity.SOLUTION: A construction management system includes a plan data input unit that receives input of construction plan data of a construction material, a test data input unit that receives input of test data of the construction material, an execution data input unit that receives input of construction execution data of the construction material, and a data management unit that manages the construction plan data, the test data, and the construction execution data in association with each other.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a material management system and a material management method. [Background technology]

[0002] During concrete construction work, various documents related to concrete (construction materials) (such as pouring plans, pouring reports, and various test results) are generally prepared on paper and stored separately at each site or construction office. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-77740 Summary of the Invention [Problem to be solved by the invention]

[0004] As mentioned above, because various documents related to concrete are stored separately at the site and in the office, it is difficult to check and use various data on concrete work. In addition, it is time-consuming and laborious to check test results related to concrete work.

[0005] The present invention has been made in view of the above problems, and an object of the present invention is to improve the efficiency of quality control of construction materials and to improve productivity. [Means for solving the problem]

[0006] The main invention for achieving the above object is a material management system characterized by having a planning data input unit that accepts input of construction material construction planning data, a test data input unit that accepts input of test data for the construction materials, an implementation data input unit that accepts input of construction implementation data for the construction materials, and a data management unit that manages the construction planning data, the test data, and the construction implementation data in correspondence with each other.

[0007] Other features of the present invention will become apparent from the following description and drawings. [Effects of the Invention]

[0008] According to the present invention, it is possible to improve the efficiency of quality control and productivity. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a schematic explanatory diagram of a concrete control system 1 according to the present embodiment. [Figure 2] FIG. 2 is a block diagram showing the configuration of a concrete control device 40. [Figure 3] FIG. 10 is a diagram showing a screen displayed on the examiner terminal 30 during the acceptance approval process. [Figure 4] FIG. 10 is a diagram showing a photograph of an acceptance test situation. [Figure 5] FIG. 10 is a diagram showing a home screen of the pouring management process. [Figure 6] FIG. 10 is a diagram showing an input table for a concrete construction pouring plan. [Figure 7] FIG. 10 is a diagram showing an input table for a concrete construction pouring report. [Figure 8] FIG. 10 is a diagram showing the functions of the pouring management process. [Figure 9] FIG. 2 is a diagram showing a user interface of the concrete control system 1. DETAILED DESCRIPTION OF THE INVENTION

[0010] At least the following points will become clear from the description and drawings to be described later.

[0011] (Aspect 1) A material management system comprising: a planning data input unit that accepts input of construction material construction plan data; a test data input unit that accepts input of test data for the construction material; an implementation data input unit that accepts input of construction implementation data for the construction material; and a data management unit that manages the construction planning data, the test data, and the construction implementation data in association with each other.

[0012] According to the material management system of aspect 1, various data relating to construction materials are consolidated and managed (unified management), thereby improving the efficiency of quality control and productivity.

[0013] (Aspect 2) It is desirable that the material management system described in aspect 1 has an output unit that displays a screen, and that the screen can selectively display the construction plan data, the test data, and the construction implementation data.

[0014] According to the material management system of aspect 2, desired data regarding the application of construction materials can be displayed on the screen, thereby further improving the efficiency of quality control.

[0015] (Aspect 3) In a material management system according to aspect 1 or aspect 2, it is desirable that the construction execution data is a copy of the same data as the corresponding construction plan data, and that the construction execution data is input when the data is rewritten.

[0016] According to the material management system of aspect 3, it is possible to save the effort of inputting construction execution data.

[0017] (Aspect 4) In the material management system according to any one of the first to third aspects, it is preferable that the test data input unit is provided in a portable terminal.

[0018] According to the material management system of aspect 4, it is possible to improve the workability in concrete testing (acceptance inspection) of construction materials.

[0019] (Aspect 5) In the material management system according to any one of the first to fourth aspects, it is preferable that the execution items of the construction execution data include plan items of the construction plan data and test items of the test data.

[0020] According to the material management system of the fifth aspect, the implementation results of the plan items in the construction plan data and the implementation results of the test items in the test data can be combined (integrated) into one.

[0021] (Aspect 6) In a material management system described in any one of aspects 1 to 5, it is desirable that the construction execution data include implementation results of the planned items of the construction plan data and implementation results of the test items of the test data.

[0022] According to the material management system of the sixth aspect, the implementation results of the plan items in the construction plan data and the implementation results of the test items in the test data can be combined (integrated) into one.

[0023] (Aspect 7) In a material management system according to any one of aspects 1 to 6, it is desirable that the test data input unit further inputs progress test data of the construction material after the input of the test data, and that the data management unit manages the construction plan data, the test data, the progress test data, and the construction implementation data in correspondence with each other.

[0024] According to the material management system of the seventh aspect, it is possible to manage (unifiedly manage) the test results including those of the progress test (for example, 7-day strength, 28-day strength, etc.).

[0025] (Aspect 8) It is desirable that the material management system described in aspect 7 has an output unit that displays a screen, and that the screen can selectively display the construction plan data, the test data, the progress test data, and the construction implementation data.

[0026] According to the material management system of aspect 8, the efficiency of quality control can be further improved.

[0027] (Aspect 9) In a material management system according to aspect 7 or aspect 8, it is desirable that the implementation items of the construction implementation data include planning items of the construction plan data, test items of the test data, and progress test items of the progress test data.

[0028] According to the material management system of aspect 9, the implementation results of the plan items in the construction plan data, the implementation results of the test items in the test data, and the implementation results of the progress test items in the progress test data can be combined (integrated) into one.

[0029] (Aspect 10) In a material management system described in any of aspects 7 to 9, it is desirable that the construction implementation data include implementation results of the planned items of the construction plan data, implementation results of the test items of the test data, and implementation results of the progress test items of the progress test data.

[0030] According to the material management system of the tenth aspect, the implementation results of the plan items in the construction plan data, the implementation results of the test items in the test data, and the implementation results of the progress test items in the progress test data can be combined into one.

[0031] (Aspect 11) A material management method comprising: a planning data input step for accepting input of construction material construction plan data; a test data input step for accepting input of test data for the construction material; an implementation data input step for accepting input of construction implementation data for the construction material; and a data management step for managing the construction planning data, the test data, and the construction implementation data in correspondence with each other.

[0032] According to the material management method of aspect 11, various data related to construction materials are consolidated and managed (unified management), thereby improving the efficiency of quality control and productivity.

[0033] Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. The same or equivalent components, members, etc. shown in each drawing are designated by the same reference numerals, and redundant explanations will be omitted where appropriate.

[0034] ===This embodiment=== <System Overview> In the material management system of this embodiment, the materials to be managed are construction materials. Examples of such construction materials include materials that use cement, such as concrete, mortar, paste, and bricks. In the following explanation, we will explain the case where the material is concrete.

[0035] FIG. 1 is a schematic explanatory diagram of a concrete control system 1 according to the present embodiment.

[0036] The Concrete Management System 1 (corresponding to a Materials Management System) is a system that shares information about the concrete used in construction. By sharing information, it also enables people in charge of planning construction work, on-site personnel such as workers working on construction sites, and construction material suppliers to obtain the information they need from this information. This aims to improve the efficiency of quality control and productivity (details will be provided later).

[0037] As shown in FIG. 1, the concrete control system 1 includes an office terminal 10, a field terminal 20, a tester terminal 30, and a concrete control device 40.

[0038] The office terminal 10, the on-site terminal 20, the tester terminal 30, and the concrete control device 40 are connected to each other via a communication network 2 so as to be able to send and receive data to and from each other. User terminals (e.g., terminals of suppliers, etc.) (not shown) are also connected to the communication network 2.

[0039] The communication network 2 is a wireless or wired communication means, such as the Internet, a wide area network (WAN), a local area network (LAN), a public communication network, or a dedicated line.

[0040] The office terminal 10 is an information processing device that is placed in a concrete construction office (here, an office where pouring plans are prepared) and is operated by office staff, etc. The office terminal 10 is, for example, a smartphone, tablet, mobile phone, personal computer, etc. The office terminal 10 is equipped with hardware such as a CPU, memory, storage device, communication module, display device (e.g., liquid crystal display), input device (e.g., keyboard, mouse, touch panel), etc. (not shown).

[0041] The storage device of the office terminal 10 stores a program for executing the pouring management process described below. By executing the program for the pouring management process, the office terminal 10 can, for example, accept input of concrete pouring plan data (equivalent to construction plan data). In other words, the office terminal 10 (specifically, the input device of the office terminal 10) corresponds to a plan data input unit. Furthermore, by executing the pouring management process, the office terminal 10 can create documents such as concrete pouring plans and share information about concrete with other terminals.

[0042] The field terminal 20 is an information processing device that is placed at a concrete pouring site and is operated by a site manager, a worker, or the like. In this embodiment, as shown in Fig. 1, there are multiple concrete pouring sites, and a field terminal 20 is placed at each of the concrete pouring sites. In other words, multiple field terminals 20 are provided. The configuration of the field terminal 20 is the same as that of the office terminal 10, so a detailed description will be omitted.

[0043] Similar to the office terminal 10, the storage device of the on-site terminal 20 stores a program for executing pouring management processing. By executing the pouring management processing program, the on-site terminal 20 can accept input of concrete pouring report data (corresponding to construction implementation data), for example. In other words, the on-site terminal 20 (specifically, the input device of the on-site terminal 20) corresponds to an implementation data input unit. By executing the pouring management processing, the on-site terminal 20 can also create documents such as concrete pouring reports and share information about concrete with other terminals. The on-site terminal 20 can also receive results of concrete acceptance inspections (hereinafter also referred to as concrete tests) from the tester terminal 30.

[0044] The tester terminal 30 is, for example, a terminal of a person who performs a concrete test (hereinafter referred to as a tester), and is an information processing device operated by the tester. The tester terminal 30 of this embodiment is a portable terminal (for example, a smartphone, a tablet, etc.) that can be carried around. The tester terminal 30 includes hardware such as a CPU, memory, a storage device, a communication module, a display device (for example, a liquid crystal display), and an input device (for example, a touch panel), all of which are not shown.

[0045] The storage device of the tester terminal 30 stores programs for executing the acceptance approval process and pouring management process, which will be described later. By executing the acceptance approval process program, the tester terminal 30 can accept input of concrete test results, as will be described later. In other words, the tester terminal 30 (specifically, the input device of the tester terminal 30) corresponds to a test data input unit. Furthermore, each of the office terminal 10, the field terminal 20, and the tester terminal 30 (specifically, their respective display devices) corresponds to an output unit that displays a screen.

[0046] The concrete management device 40 is a device that acquires various types of concrete-related data from the office terminal 10, the field terminal 20, and the tester terminal 30, and manages this data. Specifically, the concrete management device 40 acquires various types of data, such as pouring plan data, pouring report data, and concrete test data, and consolidates and manages this data. In this embodiment, the concrete management device 40 corresponds to a data management unit.

[0047] FIG. 2 is a block diagram showing an example of the configuration of the concrete control device 40. As shown in FIG.

[0048] The concrete management device 40 is a computer such as a server, and each unit is formed by the cooperation of various hardware and software. The concrete management device 40 of this embodiment includes an acquisition unit 41, a calculation processing unit 42, a memory unit 43, and a display unit 44.

[0049] The acquisition unit 41 acquires data (pouring plan data, test data, pouring report data, etc.) input to each terminal.

[0050] The calculation processing unit 42 is a CPU or the like, and performs various calculation processes. For example, the calculation processing unit 42 stores the data acquired by the acquisition unit 41 in the storage unit 43, creates a table in which each piece of data for each concrete work (construction) is associated with each other, and creates a ledger using each piece of data.

[0051] The storage unit 43 has a concrete database (hereinafter referred to as "concrete DB") that stores the various data (pouring plan data, test data, and pouring report data) acquired by the acquisition unit 41. The storage unit 43 also stores programs for executing various processes performed by the concrete management device 40. The programs are read into a memory (not shown) and executed by the calculation processing unit 42.

[0052] The display unit 44 is a part (function) for outputting the calculation results of the calculation processing unit 42 and various data read from the concrete DB in the memory unit 43 to the display device of each terminal (e.g., office terminal 10) via the communication network 2.

[0053] The concrete control device 40 may be a cloud server that exists on the web (cloud). Using a cloud server reduces the initial costs of preparing the server itself and peripheral devices, and also allows various services to be used regardless of location.

[0054] <<Data on concrete>> Various data related to concrete in concrete construction is generally created as paper-based documents (e.g., pouring plans, pouring reports, etc.) and stored separately at the site, construction office, etc. This makes it difficult to share various data related to concrete in concrete construction between sites, for example, or to use it for concrete quality control.

[0055] Furthermore, the location of the acceptance inspection (hereinafter referred to as concrete testing) that is conducted before the concrete is unloaded is usually far from the concrete pouring site, and the pouring site manager or other personnel must travel to the testing site to be present, resulting in lost time and effort in travelling.

[0056] In addition, after the concrete test was completed, the tester wrote each piece of concrete test data on a blackboard, took a photo, and saved it. This made it difficult (and time-consuming) to retrieve the concrete test data if a problem occurred in the building at a later date.

[0057] Therefore, in the concrete management system 1 of this embodiment, various data relating to concrete, such as concrete work and concrete testing (such as pouring plan data, pouring report data, and test data, which will be described later), are collected and centrally managed in the concrete management device 40. This makes it possible to easily check various pieces of information (data) relating to concrete in concrete work, thereby improving the efficiency of quality management and productivity.

[0058] <<Processing by Concrete Management System 1>> The concrete control system 1 of this embodiment mainly has the functions of executing “acceptance approval processing” and “pouring management processing.” The acceptance approval processing and pouring management processing will be described below.

[0059] <About acceptance approval processing> As mentioned above, acceptance inspection (concrete testing) is an inspection to confirm that the type and quality of concrete delivered to the pouring site meets the ordered conditions, and is an important inspection in quality maintenance management. Concrete testing items include measuring the outside air temperature and concrete temperature, slump testing, chloride content testing, air content testing, and collecting compressive strength test specimens.

[0060] Note that compressive strength tests are conducted at ages of 7 days, 28 days, and X days using specimens at the time of acceptance inspection. The test results (data) from these strength tests at ages of 7 days, 28 days, and X days are not included in the acceptance inspection items, and are added after the acceptance inspection (after 7 days, 28 days, and X days have passed). In this embodiment, of the data obtained from concrete tests, data included in the acceptance inspection items (including plant information, etc.) corresponds to test data, and data from tests conducted after the acceptance inspection (for example, 7-day strength, 28-day strength) corresponds to elapsed test data.

[0061] 3 is a diagram showing an example of a screen displayed on the tester terminal 30 during the acceptance approval process. This screen is displayed by executing a program for the acceptance approval process on the tester terminal 30.

[0062] As shown in Fig. 3, input fields for concrete information and test results for each test item (slump, air content, etc.) are displayed on the screen (e.g., touch panel) of the tester terminal 30. For example, the tester can click on the blank space for each test item on the screen in Fig. 3 to input the measurement value (test data). Furthermore, by clicking on the camera icon displayed corresponding to the test item, the tester enters imaging mode, where a photo showing the measurement value (photo of the instrument) can be taken and registered.

[0063] After entering the test results, you can take a photo of the acceptance test situation as shown in Figure 4 by clicking on the "Take a photo of the acceptance test situation" section at the bottom of Figure 3. Figure 4 is a diagram showing an example of a photo of the acceptance test situation. The blackboard section of Figure 4 displays the values ​​of the data entered on the screen in Figure 3.

[0064] The acceptance test status photographs, measurement values, and other data are sent, for example, by email to the on-site terminal 20 at the target pouring site via the communications network 2. Once the pouring site manager or other person checks and approves the data, unloading of the concrete begins. Each piece of concrete test data (test data) is also sent to the concrete control device 40 via the communications network 2.

[0065] In this way, by executing the acceptance approval process on the tester terminal 30, remote approval becomes possible, reducing the effort and time lost by the pouring site manager or the like to travel from the pouring site to the testing site to be present. The test data is also sent to the concrete management device 40 and stored in the concrete DB. In the concrete management device 40, the test data (data on concrete tests conducted before unloading) is stored in association with concrete work data (pouring plan data and pouring report data, described below). This makes it possible to quickly retrieve test data for concrete tests corresponding to concrete work.

[0066] Similarly, for tests conducted after the acceptance inspection (for example, tests on 7-day strength and 28-day strength), test result data (progress test data) is input to the tester terminal 30. The input data is then sent to the concrete control device 40 and integrated with the test data from the acceptance inspection.

[0067] <About concrete pouring management processing> FIG. 5 is a diagram showing an example of a home screen for the concrete pouring management process. This home screen is the screen that is first displayed when the concrete pouring management process program is executed on each terminal. The home screen is also a screen for accessing each function of the concrete pouring management process. In addition, by clicking the home button (not shown) in the concrete pouring plan input table or concrete pouring report input table described later, you can return to the home screen of FIG. 5.

[0068] The concrete pouring management process mainly includes a pouring plan process that creates a pouring plan for concrete work, and a pouring report process that creates a pouring report for the concrete work that has been carried out. For example, clicking the pouring plan section (button) in Figure 5 takes you to the pouring plan creation screen (Figure 6), where you can register, change, or view the schedule. Also, for example, clicking the pouring report section in Figure 5 takes you to the pouring report creation screen (Figure 7), where you can register a pouring report or view the registered pouring report.

[0069] (Pitching plan creation screen) Fig. 6 is a diagram showing an example of an input table for a concrete construction pouring plan. For example, when a pouring management processing program is executed on the office terminal 10 and the pouring plan section (button) in Fig. 5 is clicked, the screen shown in Fig. 6 appears, allowing input of each data item in the pouring plan to be accepted.

[0070] The input table for the pouring plan shown in Figure 6 contains items (corresponding to plan items) related to the pouring plan, such as pouring ID, pouring date, pouring location, ready-mixed concrete plant, type of concrete, pouring contractor, etc., and the data (pouring plan data) are organized in table format (Excel format in this embodiment). In the table shown in Figure 6, the data for each item lined up horizontally corresponds to one concrete work.

[0071] When registering a new concrete work plan, new pouring plan data can be added by clicking the "New" button on the toolbar in Figure 6. Furthermore, when modifying the contents of the pouring plan, the "Modify" button on the toolbar can be clicked to select the concrete work to be modified and modify its contents (data). The data (pouring plan data) entered into each item in Figure 6 is sent from the office terminal 10 via the communication network 2 to the concrete management device 40 and stored in the memory unit 43 (concrete DB) in a file format such as CSV or JSON.

[0072] (Pouring report creation screen) Fig. 7 is a diagram showing an example of an input table for a concrete work pouring report. Like the input table for the plan, the input table for the pouring report is also configured, for example, in a table format (Excel format in this embodiment). In the table shown in Fig. 7, data for each item lined up in a horizontal row corresponds to one concrete work (and concrete test).

[0073] As shown in Figure 7, the input items for the concrete pouring report include the input items for the plan (planned items), the test items for the acceptance inspection, and the test items for the tests (progress tests) conducted after the acceptance inspection (e.g., 7-day strength, 28-day strength). In other words, the concrete pouring report data includes the implementation results of the items in the pouring plan (planned items), the implementation results of the test items for the acceptance inspection, and the implementation results of the test items for the tests (progress tests) conducted after the acceptance inspection (e.g., 7-day strength, 28-day strength).

[0074] The creation (recording) of the pouring report in FIG. 7 is performed on the site terminal 20 where the concrete pouring work was carried out. As shown in FIG. 7, the toolbar of the pouring report input table has a pouring plan data input button. Clicking this button first displays a list of the work created in the pouring plan. By selecting the corresponding work from the list, the same data as the pouring plan data registered in the input table of that pouring plan is copied and pasted (copied) into the pouring report input table (pouring report data). At this time, the pouring plan data and the pouring report data are associated. Then, depending on the concrete pouring implementation status, only the items that differ from the plan need to be entered (i.e., only the data for those items needs to be rewritten). This reduces the effort required for data entry.

[0075] Furthermore, by registering (associating) the acceptance inspection corresponding to the concrete work, the test results (including the results of progress tests) are automatically imported into the data for test items in the input table for the pouring report. Therefore, as shown in Figure 7, the pouring report data and test data are displayed integrated in the input table for the pouring report. Note that the pouring plan data in the pouring plan document may also be integrated by, for example, indicating that it is a plan, such as by adding an item such as "Pouring date (planned)." In other words, all data related to the concrete work (pouring plan data, pouring report data, test data, progress test data) may be integrated into the data.

[0076] <Functions of concrete pouring management processing> 8 is a diagram showing an example of the function of the concrete pouring management process. By executing the concrete pouring management process program, various documents as shown in the diagram can be easily created.

[0077] For example, in Figure 6, clicking the "Create a plan" button on the toolbar will create a pouring plan in a specified format based on the data entered in the pouring plan input table. You can also create and send a concrete ordering document.

[0078] Also, for example, in Figure 7, clicking the "Create Report" button on the toolbar creates a pouring report in a specified format based on the data entered in the pouring report input table. In this embodiment, since the pouring plan data and the pouring report data are associated with each other, a graph showing a comparison between the concrete pouring schedule and the actual results can be created in this pouring report. For example, a graph showing the schedule (pouring plan data) showing the pouring amount by time can be created by superimposing it on a graph showing the corresponding actual results (pouring report data).

[0079] In this way, various documents can be easily created through the pouring management process.

[0080] <About the user interface of Concrete Management System 1> Fig. 9 is a diagram showing an example of a user interface (UI) of the concrete control system 1. Fig. 9 shows a screen that is displayed when the concrete control apparatus 40 is accessed from any terminal (such as the office terminal 10, the on-site terminal 20, the tester terminal 30, or another user terminal) connected to the communication network 2. In other words, the display unit 44 of the concrete control apparatus 40 displays a screen such as that shown in Fig. 9 on each terminal.

[0081] As shown in the figure, on the screen, you can select the location and type of concrete work, and enter the date and time (duration), thereby specifying the desired concrete work.

[0082] Although not shown, buttons may be provided to select whether or not to display each data item (concrete work test results, pouring plan, and pouring report) for the concrete work. By selecting these buttons appropriately (multiple selections are possible), the relevant data may be selectively displayed. Also, the output example at the bottom of Figure 9 has buttons to download each data item (test results, pouring plan, and pouring report) in CSV format. Here too, by selecting the appropriate button, the relevant CSV data can be selectively output (downloaded).

[0083] In this way, the concrete management system 1 makes it possible to easily check the history (various data) of the concrete used in the concrete work by aggregating and centrally managing various data related to the concrete in the concrete management device 40. This makes it possible to improve the efficiency of quality control and productivity.

[0084] Furthermore, the concrete control system 1 can also realize the following functions, for example.

[0085] It is possible to determine the relationship between concrete temperature and outside air temperature. For example, it is possible to predict concrete temperature based on changes in outside air temperature, such as during hot or cold weather, and to issue an alert if there is a risk that the temperature will exceed a predetermined value (e.g., 35°C).

[0086] It is also possible to determine the relationship between elapsed strength and demolding strength. For example, it is possible to determine the relationship between the outside temperature and the 7-day strength (or the previous 3-day strength, for example) and the 28-day strength, and to estimate the demoldable strength.

[0087] It is also possible to predict the number of people required for pouring each concrete section. Specifically, by understanding the "section," "quantity poured," and "number of contractors" listed in the concrete construction report, it is possible to estimate the optimal number of personnel.

[0088] It also enables support teams to check the progress. For example, by uploading test results such as fresh properties to the concrete control device 40 in real time, the quality control department, technical research institute, etc. can check the progress of the test.

[0089] It is also possible to grasp the relationship between pouring volume, pouring time, and pouring location. For example, it is possible to predict the completion time for pouring depending on the location (slab, column, beam, wall, etc.), which serves as a guide to prevent overtime.

[0090] You can also check the track record of the environmentally friendly concrete "Cleancrete" (you can see how much environmentally friendly concrete has been poured, which also serves as an appeal to environmental consciousness).

[0091] ===Other=== The above-described embodiments are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and it goes without saying that the present invention includes equivalents thereof. [Explanation of symbols]

[0092] 1. Concrete Management System 2. Communication Network 10 Office terminal 20 Field terminal 30 Tester terminal 40 Concrete management equipment 41 Acquisition Department 42 Processing unit 43 Storage section 44 Display section

Claims

1. a planning data input unit that receives input of construction material construction plan data; a test data input unit that accepts input of test data for the construction material; an implementation data input unit that receives input of construction implementation data for the construction material; a data management unit that manages the construction plan data, the test data, and the construction execution data in association with each other; A material management system comprising:

2. 10. The material management system of claim 1, an output unit for displaying a screen; The screen can selectively display the construction plan data, the test data, and the construction implementation data. A material management system characterized by:

3. 10. The material management system of claim 1, The construction execution data includes a copy of the same data as the corresponding construction plan data, The construction execution data is input when the data is rewritten. A material management system characterized by:

4. 10. The material management system of claim 1, The test data input unit is provided in a portable terminal. A material management system characterized by:

5. 10. The material management system of claim 1, The implementation items of the construction implementation data are: Plan items of the construction plan data; Test items of the test data; A material management system comprising:

6. 10. The material management system of claim 1, The construction execution data is Implementation results of the plan items of the construction plan data; The results of the test items of the test data; A material management system comprising:

7. 10. The material management system of claim 1, The test data input unit further inputs progress test data of the construction material after the input of the test data, The data management unit manages the construction plan data, the test data, the progress test data, and the construction implementation data in association with each other. A material management system characterized by:

8. 8. The material management system of claim 7, an output unit for displaying a screen; The screen can selectively display the construction plan data, the test data, the progress test data, and the construction implementation data. A material management system characterized by:

9. 8. The material management system of claim 7, The implementation items of the construction implementation data are: Plan items of the construction plan data; Test items of the test data; A progress test item of the progress test data; A material management system comprising:

10. 8. The material management system of claim 7, The construction execution data is Implementation results of the plan items of the construction plan data; The results of the test items of the test data; The implementation results of the progress test items of the progress test data; A material management system comprising:

11. a planning data input step of accepting input of construction material construction plan data; a test data input step of accepting input of test data of the construction material; An implementation data input step of accepting input of construction implementation data of the construction material; a data management step of managing the construction plan data, the test data, and the construction execution data in association with each other; A material management method comprising:

Images