JP2009098762A - Pipeline information system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that when integrating maintenance management data necessary for maintaining a long facility structure such as a pipeline, items of data, numerical units, and notations are different from each other. <P>SOLUTION: In association with a pipeline name, a distance section, and effective time, there are prepared an item conversion table in which a conversion item name and a general-purpose database name are associated, and a unit-notation conversion table. Then, input data of a table format is associated with a general-purpose data item according to the contents of the item conversion table for each item, and by referring to notations described in the unit-notation conversion table, conversion to a unit-notation system adopted in the general-purpose database is obtained according to the unit of input data and the notation method. Even when data management items, languages, numerical description units and notation methods are different from each other, data are stored in a consolidated manner without generating a conversion program at each case. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a geographic information system (GIS) and relates to a pipeline information system using an integrated database of pipeline facility attribute data having different data management items, units, and notation methods.

  The following conventional technologies exist for pipeline facility management and data conversion.

  In Patent Document 1 (Piping Equipment Management Support Device) and Patent Document 2 (Transmission and Distribution Pipe Management Support Device), piping data is displayed using three-dimensional data. It is characterized by three-dimensional display using height information.

  Patent Document 3 (piping system modeling method) is a method of performing data collation and conversion between models on data constructed for different purposes. It is a feature that the shape is converted between the objects described in the three-dimensional shape and the system diagram described in a plane.

  Patent Document 4 (Plant Design Support Database System) is characterized in that data can be used in a plurality of systems by performing data conversion when data description units and data types are different in different systems.

  Patent Document 5 (Heterogeneous Database Integration Support Device) is characterized in that different databases having a high degree of matching of attributes are associated as the same one.

  In Patent Document 6 (CAD data conversion apparatus and method and program), CAD (Computer Aided Design System) data type conversion is performed. The feature is that the inter-component correspondence rules are visually displayed.

  Patent Document 7 (pipeline management data, pipeline management data processing method, pipeline management data program, and pipeline management data processing system) associates corrosion and cathode protection potential data with a map displayed on the pipeline. Features.

  Patent Document 8 (pipeline search position specifying method, portable terminal and pipeline search position specifying program) shows a method of specifying the position of a pipeline using GPS.

JP-A-6-33493 JP-A-6-108501 JP-A-7-103400 JP-A-10-283392 JP200486782 JP 2005-301630 A JP 2005-308441 A JP 2006-250619 A

  In a long-distance structure such as an oil / natural gas main pipeline, construction and inspection are performed for each partial section constituting the pipeline. At this time, a plurality of organizations (businesses and public organizations) inspect and construct each section. Data in tabular form is created and reported as a result of inspection and construction. In tabular data, item names are described first. Since the report is made by a report determined for each organization, data items, numerical units, and notation may not be unified. Therefore, it has not been possible to integrate these data. Furthermore, if the language used to indicate the items is different, such as Japanese, English, or Russian, these data could not be entered and used in the same system. Therefore, it is necessary to create a conversion program for each item in order to integrate these data.

  Here, even if different data management items, different languages, numerical units, and notation methods are different, conversion programs can be stored centrally without having to be created each time. It is an issue to be able to prioritize repair and replacement by extracting pipe sections.

  To solve the above data integration problem, pipeline name, distance section (start distance and end distance to be converted), effective time (pipeline name, start of data conversion in the distance section becomes effective The item conversion table in which the conversion item name is associated with the general-purpose database name is prepared in association with the time and the end time. Similarly, a unit / notation conversion table is prepared in which the unit / notation conversion item name is associated with the unit used and the notation method in association with the specific pipeline name, distance section, and valid time. Then, input data in tabular format is made to correspond to general-purpose data items according to the contents of the item conversion table for each item, and further, with reference to the notation described in the unit / notation conversion table, in the general-purpose database according to the unit and notation method of the input data Convert to the unit and notation used. Furthermore, by providing a language dictionary and synonym dictionary, associative search based on synonym search and word association, item mapping table item association, unit / notation conversion table unit system, notation The method may be estimated. Here, the pipeline name is information for specifying the pipeline, and may be managed by a number or the like in addition to a specific name.

  Next, by using these data, corrosion expansion prediction and cathode protection (electrocorrosion) potential change prediction are performed. The converted data has a time attribute. Even if input from different data item names can be integrated as history data, corrosion expansion prediction and cathode protection potential change prediction can be performed by using the passage of time. Confirm the timing of pipe replacement and repair according to the forecast. As a result, pipes that are subject to replacement / repair are extracted by predicting deterioration of pipes and insulation materials by integrating data with different management item names, units / notation systems, which could not be integrated, into a general-purpose database. And can be prioritized.

  Even if each pipeline inspection organization uses its own data management items, these data can be used directly without any change. Data can be used as history data by managing it with a time attribute. This makes it possible to find and prioritize pipes that are subject to replacement / repair and pipes that are subject to replacement of insulating materials based on corrosion expansion prediction and cathode protection potential change prediction. . Even if multiple organizations are involved in maintenance management, all data can be used directly without creating a new data conversion program for data conversion. Furthermore, it is not necessary to prepare a database according to the organization that created the data, so the database construction cost can be reduced.

  The present invention is implemented by computer software.

  In a long structure such as an oil / natural gas pipeline, internal corrosion may occur when highly corrosive fluid flows, and external corrosion may occur when the pipeline is buried underground. For this reason, an inspection robot called a pig measures corrosion inspections and changes in shape, and repairs are performed when damage is minor, and pipes that are severely damaged and have problems are replaced or repaired. Such measurement for maintenance management is performed by a plurality of specialized organizations for each pipeline section. In particular, when fluid is pressurized by a pump station or a compressor station on the way, inspection may be performed between pump stations or between compressor stations. The specialized organization reports the results of construction and maintenance performed by itself in a database. The inspection / measurement may not be performed by a single organization, and unless the item name is specified, the result of the inspection result data is reported by a unique item determined by the specialized organization. Therefore, although the data has the same contents for each section, there are different items of data. This situation is the same in pipe replacement / repair and cathode protection potential measurement. The results of construction replacement / repair and cathode protection potential inspection are compiled into a data file and delivered to the pipeline operator. In a long facility such as a pipeline, a single organization does not have a single organization, but multiple organizations share the sections to perform construction, repair, and measurement, and create data. Furthermore, items to be converted into data may be created in multiple languages depending on the country where the pipeline is constructed, repaired, or measured. In this situation, in order to search and use data across sections, the data obtained as a result of construction, repair, and measurement created for each section is integrated into a database and managed centrally. , Need to make it available.

The following can be considered as the differences in items.
-The management item name of the data passed to the pipeline operation organization / company is different.

For example, in corrosion data, the length may be described as Length, or may be described as Corrosion Length.
-The unit of the item value is different.

For example, in the cathode protection potential data, the measured voltage may be described in volts “V” or “mV”.
-Item notation is different.

For example, the start position of the corrosion data may be described as 5:30 by the clock (this is a notation method in which the start position is expressed by the position of the hour hand) because the pipe cross section is circular. (5.5 indicates 5:30. In such a case, the decimal part can be converted to a time by multiplying by 60).
・ The description language of the item is different.

For example, “corrosion” in Japanese is “Corrosion” in English.
・ The method of taking data reference values may change.

  For example, pipeline maintenance data such as corrosion and cathode protection potential is acquired using distance as key data, but the reference position of this distance may be different. In a certain year, even if it is 500 km, it may be changed to 501 km in the coming year after accurate measurement.

In order to centrally manage and use data created with different data management items, units, and notations in this way, perform data item name conversion, unit / notation conversion, and convert them to general-purpose item names. Is required. At the same time, instead of making these conversions a program each time a new item appears, the conversion program does not change but converts the information that needs to be converted into data, and the conversion program refers to the conversion. To do. Further, instead of manually preparing the change of the conversion data, it may be estimated by synonym search from the input item name and associated with a general-purpose item. Such a conversion method is shown below. FIG. 1 shows the system configuration.
Pipe section measurement data (101): Input data, which is data storing corrosion of the section of the pipeline, cathode protection potential and construction related information.
Synonym database (102): A dictionary for language conversion showing synonym correspondence of item names and conversion between different languages.
Attribute database (103): a database storing measurement data such as construction attributes such as length, inner diameter, thickness, construction date, material, and corrosion / cathode protection potential of each pipe constituting the pipeline. Here, in order to integrate the input data, it is hereinafter referred to as a general-purpose database.
Map shape database (104): This is a database for storing vector map data constituted by two-dimensional or three-dimensional coordinate sequences. The shape of the map includes a two-dimensional shape described by coordinate data based on X and Y coordinates, and a three-dimensional shape described by X, Y, and Z coordinates.
Unit / notation conversion data (105): Table data describing the unit / notation method when the description of stored data is different from the unit / notation system of the general-purpose database (103).
Item name conversion data (106): table data describing which of the general-purpose database (103) items each item corresponds to when there is a data item different from the predetermined general-purpose database (103) item .
Data analysis interface unit (107): a function of reading pipeline section measurement data (101) and arranging input data for each item.
Item data extraction unit (108): a function of selecting each item of input data and extracting the data.
Item name conversion unit (109): This function refers to the item name of the input data and associates the item name with the item name in the general-purpose database (103) when the item conversion has to be performed.
Unit / notation conversion unit (110): a function for performing unit / notation conversion on data that must be subjected to unit / notation conversion or notation conversion in accordance with unit / notation conversion data.
Database registration unit (111): a function of registering item data whose unit / notation has been converted in the general-purpose database (103).
Word / notation item search unit (112): This function analyzes a real data object described in input data and extracts unit / notation information.
Unit / notation synonym item registration unit (113): a function of registering the contents that can be registered as unit / notation conversion data in the unit / notation conversion data 105 after the user confirms the contents.
Related item name search unit (114): Search for synonyms from the item name conversion data with reference to the synonym database (102) for items that are not included in the item name conversion data among the input data items to be converted. This is a function for searching for conversion candidates.
Item name registration function (115): After confirming the user based on the search result in the related item name search unit 114, the correspondence between the input data item and the general-purpose database (103) item is stored in the item name conversion data 106. It is a function.
Database search unit (116): a function for searching for an attribute from a specified pipeline name, time, and distance range. Here, a search is performed by issuing an inquiry sentence to the general-purpose database 103.
Item name reverse conversion unit (117): Refers to the item name conversion table to convert the general-purpose data item into the input item for display in the input data item.
Unit / notation reverse conversion unit (118) is a function for converting numerical data units and notations in the general-purpose database (103) for display in input data items.
Display unit (119): This is a function for displaying the data of the general-purpose database (103) subjected to item conversion and unit / notation conversion in correspondence with the name of the input data.
Applied function (120): A function for predicting corrosion expansion and insulation abnormality using corrosion data based on history and cathode protection potential data.

  FIG. 2 shows a situation that requires item name conversion, unit / notation conversion, and notation conversion. FIG. 2 shows three compressor stations (in the case of natural gas) or pump stations (in the case of oil) 203, 204, 205 that pressurize oil and natural gas flowing through two pipeline sections 201, 202. In this figure, an internal inspection and a piglancher (206) for mounting an inspection robot (pig) for measuring the shape and a pig receiver (207) for collecting the inspection robot are installed in each pipe section. In addition, when the pipe is buried in the ground, a transformer 208 which is an electric cathode protection device for preventing corrosion by causing a current to flow through the pipe to create a potential difference and a measurement outlet 209 which is a measurement point are installed. . In FIG. 2, it is shown that the organization performing the pipeline pig inspection and the periodic inspection of the electrocathode protection equipment also varies depending on the time in the pipe section and the same section. As shown in the lower part of FIG. 2, in the pipe section 201 and the pipe section 202, it is shown that contractors who perform construction, repair, replacement, pig inspection, and cathode protection potential inspection are different. In such a case, management data items may differ for the data delivered in each operation.

FIG. 3 shows data items of the corrosion data.
301 is a format of the general-purpose database (103), which is a table format. General corrosion data items are
Distance: Corrosion start distance (distance from the starting point)
Start Position: Corrosion start position
Length: Length of corrosion pipe in the axial direction
Width: width of corrosion
Depth Rate: Relative depth of corrosion (maximum depth / pipe thickness)
Units and notations are
Distance: km
Length: mm (mm)
Width: mm (mm)
Depth Rate:% (percent)
And The input data is similarly described in a tabular format, but two examples of corrosion data items (302, 303) are shown.
In item example A (302)
Start Distance: Corrosion start position
Start_Pos: Corrosion start position
Corrosion Length [mm]: Length of corrosion pipe in the axial direction. The unit is “mm”.
Corrosion Width [mm]: Length of pipe in the circumferential direction of corrosion. The unit is “mm”.
Maximum Corrosion Depth [%]: Maximum corrosion depth. Units"%".
These languages may be written in languages other than English. For example, in Russian-speaking countries, as shown in item example B (303),
[Fig. 17]
become. Since the data management items are different from each other as described above, the data described in 302 and 303 needs to be associated with the general-purpose database item by conversion.

The structure of the item name conversion data is shown in FIG. This item name conversion data 401 is composed of five description areas with a pipeline name, item effective distance, item effective period, general data item name, and input data item name.
Pipeline name (402): The name of the pipeline is described. Add a name for each pipeline.
Item effective distance (403): Describe the distance section (start distance, end distance) in which the item name is valid.
Item valid period (404): The period (start time, end time) in which the item name is valid is described.
General-purpose database item name (405): Describes the item name of the general-purpose database (103).
Input data item name (406): The item name of the input data is described.
401 and 407 show the correspondence between the item example A (302) and the item example B (303) in FIG. As can be seen from the item validity period (404), 401 and 407 are data of the same pipeline distance, but 401 is valid in the period from December 5, 2000 to June 4, 2006. Indicates the latest version after June 5, 2007. Thus, 401 and 407 become history data. The month and day may be omitted.

Next, the structure of the unit / notation conversion table is shown in FIG. This unit / notation conversion table (501) is composed of five description areas: pipeline name, unit effective distance, unit effective time, input data unit name, unit / notation.
Pipeline name (502): The name of the pipeline is described. Add a name for each pipeline.
Unit effective distance (503): A distance section (start distance, end distance) in which the unit / notation is valid is described.
Unit effective time (504): Enter the time when the unit / notation is valid.
Unit item name (505, 507, 509): The item name of input data that requires unit / notation conversion is described.
Unit / notation (506, 508, 510): Enter a symbol indicating the unit or notation method of the unit item name 504.
Reference numeral 506 denotes a unit included in the item 505. The start length that indicates the start of corrosion is not the distance from the pipeline base point, but may be expressed as the distance from the base point of the compressor station or pump station. The base point distance values at may not match. For such a case, it is also necessary to add an offset as shown at 508. In the general-purpose database (103), as described above, the corrosion start position is described in time notation based on hours and minutes such as 9:30, but 509 indicates that it is expressed as 9.5. . This can be determined by checking the contents of the data. For this reason, *. * Is described as notation information. Furthermore, the cathode protection potential is shown. The units of the general-purpose database 103 of ON potential, OFF potential, and anode current are mV (millivolt), mV (millivolt), and mA (milliampere), respectively, but in the input data item 505, V (volt), V (volt), Since it is A (ampere), it indicates that unit conversion is necessary as indicated by reference numeral 506.

  Next, the flow of additional registration for item name conversion is shown in FIG. This input data item name 606 does not match the item name 605 of the general-purpose database (103). Therefore, it is necessary to convert item names. Since the synonym database 112 stores synonym data, the item name can be estimated. This is done by dividing the input data item 606 into words and capturing their meanings. For example, in 601, since Start Distance has Distance, it indicates that it is estimated as Distance of the general-purpose database item name. Further, since Start Pos of 602 has the keyword Start, it is estimated that it corresponds to Start Position or Start Distance. If there is a description in the synonym database (102) that Pos is the same as Position, it is estimated that it is converted to Start Position as a result. Further, the Corrosion Length, Corrosion Width, and Maximum Corrosio Depth [%] of 602 are estimated to be Length, Width, and Maximum Depth Rate as indicated by 603. If the input data item does not exist in the synonym database (102), the user is inquired to determine which of the general-purpose database items should be converted.

  For example, it is assumed that there is a word O′Clock in the input data item corresponding to Start Position, and this is not in the synonym database (102). At this time, the user is inquired, but when converted to Start Position, synonyms of O'Clock with Start and Position are registered in the synonym database (102).

  Similarly, the same additional registration is performed for units and notations. FIG. 7 shows a unit / notation conversion method. It is assumed that P / S On [V] (702) is newly added to the unit / notation conversion data 701. At this time, since there is the keyword On, it is estimated that it is equivalent to the already registered POTENTIALS On (703) by analogy with the POTENTIAL ON (703) described above. For this reason, it is a unit of POTENTIALS On. V (bolts) (704, 705) are associated. This can also be estimated from the symbol [V] included in PS On [V]. If there is no description such as [V], the data itself is directly checked to determine whether it is in the mV range or V description. Similarly, PS Inst.OFF [V] is estimated to be the same as POTENTIALS OFF. Since PS Inst.OFF [V] is described as [V] in parentheses, V is described. It can be seen that Anode Current [A] is the same as Anode Current, but A is added at the end. For this reason, it is estimated that a unit is A (ampere). For this reason, A is described. Furthermore, the notation method can be registered by checking the data itself. As described above, for the item name conversion and unit / notation conversion, the item name is estimated by the synonym database (102) and the existing item name conversion data (106) and existing unit / notation conversion data (105) are registered. New data is registered in the item name conversion data 106 and the unit / notation conversion table 105 by the unit / notation equivalence of words. In addition, when newly registering an item, confirmation by the user is performed.

  As a procedure for storing data, an object file is put in a specific folder, the files are taken out in order, and the data is registered in the general-purpose database (103). A data registration button is provided in the menu of such pipeline information management software, and when this button is selected and pressed, data conversion is started. All conversions are automatically performed except for confirmation of conversion support. A specific folder may be divided according to data contents. However, in any case, it is necessary to decide in advance how to name the input data.

Specifically, the data name is
PipelineName_ DataType _StartLength_EndLength_StarTime_EndTime_Cycle_ Dimension
And here,
PipelineName: Indicates the pipeline name.
DataType: Indicates the type of data. Enter names such as corrosion data and cathode protection potential data.
StartLength: Start distance, which indicates the start distance of a distance section in which data is valid. EndLength: This is the end distance, and indicates the end distance of the distance section in which the data is valid.
StartTime: This is the start time and indicates the start time of the period in which the data is valid.
EndTime: This is the end time and indicates the end time of the period during which the data is valid.
Cycle: Indicates a data acquisition cycle. Since the cathode protection potential and the like are periodically measured and acquired, this period cycle (4 months, 6 months, etc.) is shown.
Dimension: Indicates whether the distance measurement is a three-dimensional distance or a two-dimensional distance. In the case of a three-dimensional distance, a symbol such as “D” is used in the case of a two-dimensional distance.

FIG. 8 shows a data registration flow for registering data having different item names, units, and notations in the general-purpose database (103) as described above. It is assumed that data is stored in one folder. However, even if it is put in a different folder for each data content, the following flow can be easily corrected without making essential changes.
Step 1 (Step 801): Confirmation of data storage When all the input data are stored in the general-purpose database (103) by the database registration unit (111), the processing is terminated. If not stored, step 2 (802) and subsequent steps are executed.
Step 2 (802): Data selection One unstored data file is selected and read from the pipe section measurement data (101) from the data analysis interface unit (107). At this time, the above-described data name is analyzed to determine the content, pipeline name, section distance, effective period, and dimension of the distance, and inform the database registration unit (111).
Step 3 (803): Item name conversion table read determination Step 4 (804) is executed when the item name conversion data 106 is read, and step 5 (805) is executed when it has already been read.
Step 4 (804): Reading item name conversion data The related item search unit 114 reads item name conversion data (106). If the languages are different, the language conversion dictionary is read together with the synonym database (102).
Step 5 (805): Unit / notation conversion data read determination When the unit / notation related item search unit (112) reads the unit / notation conversion data (105), it executes step 6 (806) and has already read it. If yes, step 7 (807) is executed.
Step 6 (806): Reading of unit / notation conversion data The unit / notation related item search unit 112 reads the unit / notation conversion data (105).
Step 7 (807): Check storage status for each item (FIG. 9)
The database registration unit (111) determines whether all data is registered for each item described in the data file. When all items are stored in the general-purpose database (103), step 1 (801) is executed to obtain a new data file. If not stored, step 8 (808) is executed.
Step 8 (808): Selection of Non-Storage Item The item data extraction unit (108) selects a non-storage item if it exists.
Step 9 (809): Confirmation of Item Name of General-Purpose Database (103) The item name conversion unit (109) determines whether or not the selected item name matches the name of the general-purpose database (103). If it matches the general-purpose database item name, step 15 (815) is executed. If they do not match, step 10 (810) is executed.
Step 10 (810): Collation with item name conversion data The item name conversion unit (110) compares the item name stored in the item name conversion data (106), and the item name corresponds to the general-purpose database item name. Check whether the is listed.
Step 11 (811): Confirmation of Conversion Item The item name conversion unit (110) searches for an item name that matches the keyword of the existing item described in the item name conversion data (106). This corresponds to matching the general-purpose database item (405) from the input data item (406) in the item name conversion data (401) in FIG. If there is a match, the general-purpose database item name of the data storage destination is determined and step 15 (815) is executed. If they do not match, step 12 (812) is executed.
Step 13 (812): Selection of synonym items The related item name search unit (114) searches the synonym data from the read synonym database (102), and searches for the correspondence with the synonyms by decomposing the item names. Then, a corresponding candidate for the general-purpose database item name is presented to the user for each item. In this case, if there is no corresponding item, the user is notified that there is no corresponding item.
Step 14 (813): Confirmation by User The related item name search unit (114) selects the correct conversion by referring to the correspondence between the item name presented by the user and the item name of the general-purpose database (103). If there is only one candidate, if it is the correct conversion item name, it is selected by pressing the appropriate key. If not correct, the user describes the correct conversion method in the item name conversion data (106).

When there are two or more candidates, one correct answer is selected from them. If not correct, the user describes the correct conversion method in the item name conversion data (106).
Step 15 (814): Registration in the item conversion table (FIG. 10)
The item name registration unit (115) stores the correspondence between the general database item name and the input data item name in the item name conversion data (106).
Step 16 (815): Collation with Unit / Notation Conversion Table Next, the unit / notation is checked and converted. The unit / notation-related search unit (112) refers to the unit / notation conversion data (105) to search whether the item selected in step 2 (802) is an item for which word / notation conversion is performed.
Step 17 (816): Confirmation of unit / notation conversion If the item is a unit / notation conversion target, step 18 (817) is executed. However, if the item is not the unit / notation conversion target, step 19 (818) is executed.
Step 18 (817): Execution of Unit / Notation Conversion The unit / notation conversion unit (109) executes unit / notation conversion.
Step 19 (818): Determination of general-purpose item The unit / notation-related search unit 112 determines whether the item selected in Step 2 (802) is a general-purpose database item. If it is a general-purpose database item, step 24 (824) is executed in order to register the general data of the actual data of the input data. If it is not a general database item, step 20 (819) is executed in order to verify the necessity of unit / notation conversion.
Step 20 (819): Estimation of unit / notation conversion from general-purpose database item name and data name The input data item for verifying necessity of unit / notation conversion is already stored in the item name conversion data (106). The unit / notation-related search unit (112) refers to the general-purpose database item name and the input data name acquired by the related item name search unit (114), and searches the unit / notation of the general-purpose database to find the unit.・ Estimate the notation. For example, differences in units such as m and mm, km, and V and mV can be estimated from the numerical values. The offset can be estimated from the effective distance. Then, the unit / notation method is presented to the user for each item of the input data. In this case, if there is no corresponding item, the user is notified that there is no corresponding item.
Step 21 (820): Confirmation of unit information from item name In the unit / notation-related search unit (112), if the item is a target of the unit / notation conversion item based on the search result in step 20 (819), Search for clues of units from the item names. Specifically, when there is a notation such as [V] in the cathode protection potential data, this may be a unit of voltage. If there is unit information, step 22 (821) is executed. If there is no unit information, step 23 (822) is executed.
Step 22 (821): Unit / notation estimation If the unit / notation-related search unit (112) can detect unit / notation information, this is extracted.
Step 23 (822): Unit Input by User The unit / notation-related search unit (112) presents a corresponding candidate for each item to the user. In this case, when the unit / notation is different from the general-purpose item, the user confirms.
Step 24 (823): Storage of unit / notation conversion data (FIG. 11)
The unit / notation conversion registration unit (113) writes the unit / notation symbol in the unit / notation conversion data (105). Then, Step 18 (817) is executed.
Step 25 (824): Storage of item data The database registration unit (111) associates data corresponding to the item name of the input data with the general-purpose database item name, and further converts the actual data in the input data while performing unit / notation conversion. Store in the attribute database (103). When completed, step 1 (801) is executed.

  According to the steps shown in step 1 (801) to step 25 (824), even if the item name, unit / notation is different from the general database item name, actual data unit, or notation method, it can be registered in the general database (103). . The history can be analyzed by using these data.

When these data are displayed to the user, the input database item may not correspond to a clear item provided in the general-purpose database item. In this case, it corresponds to the “Other” item. If so, the user may not be able to understand when displayed in accordance with general-purpose database items. The content of the “Other” item is unknown to the user even if “Other” is displayed. For this reason, it is appropriate to display the input data item. For this reason, items and data are displayed in the following steps.
Step 1: Database Search The database search unit (116) searches for data in the general-purpose database (103) in a specific pipeline name, distance range, and time range.
Step 2: Reverse item name conversion In reverse item name conversion (117), the correspondence between the general database item name and the item name of the input data is referred to the item name conversion data (106) to acquire the input data item name. This corresponds to collating the input data item (406) from the general-purpose database item (405) in the item name conversion data (401, 407) in FIG.
Step 3: Unit / notation reverse conversion The unit / notation reverse conversion unit (118) refers to the unit / notation conversion data (105) for the unit / notation method corresponding to the input data item name, Convert to notation.
Step 4: Display The display unit (119) displays the data returned to the unit / notation of the input data.
The pipeline facility deterioration prediction is performed by the application function unit (120), and is performed using the data of the general-purpose database (103) acquired by the database search unit (116). The result analyzed and predicted here is associated with the map shape database (104) by distance and time and sent to the display unit (119) to display the prediction result.

FIG. 17 is a system configuration diagram for performing prediction. Here, the functions from 1701 to 1719 correspond to the functions from 101 to 119 shown in FIG. 1, respectively, but the application function (120) in FIG. Details are given in acceleration calculation (1721) and deterioration state prediction (1572).
History calculation unit (1720): a function for searching history data including the latest data with respect to the attribute database (1703).
Deterioration calculation / acceleration calculation unit (1721): This function calculates the deterioration speed and acceleration based on the history data.
Deterioration situation prediction unit (1722): This function calculates a change prediction up to a specific time using the deterioration rate and acceleration obtained by the deterioration calculation / acceleration calculation unit (1721).

  FIG. 18 shows the entire flow including data registration to data usage analysis. First, input data (1802) is prepared during input setup (1801). By supporting the instruction execution by the computer, the item / unit / notation conversion (1803) is executed and stored in the general-purpose database (1804) in correspondence with the general-purpose items and the storage format. They are displayed on the computer screen as display data (1806) through item / unit / notation reverse conversion (1805).

  Next, the deterioration of pipes and insulating materials is calculated using data for corrosion and cathodic protection. In the deterioration calculation instruction (1807), the pipeline name and the distance / time data (1808) are prepared. In the database search query language generation (1809), the history data is searched from the general-purpose database (1804) according to the time designation, the deterioration prediction calculation (1810) is performed, and the prediction result is calculated as the deterioration prediction data (1811). Is displayed. Reference numerals 1801, 1802, 1806, 1807, 1808, and 1811 denote user interface functions, which correspond to computer hardware screens. Reference numerals 1803, 1805, 1809, and 1810 denote data analysis functions, and calculations are performed inside the computer hardware. Reference numeral 1804 denotes a database function, which similarly shows the internal data storage structure of the computer hardware.

FIG. 12 shows a method for predicting pipeline corrosion expansion based on time series. It is assumed that different vendors conduct corrosion inspections for the same section. Pipeline corrosion inspection is performed by an inspection robot called “Pig” or an appearance inspection of a pipe. 1201 is corrosion data acquired in 2000, and 1202 is corrosion inspection data acquired in 2007. Further, it is assumed that the distance starting point of the pipeline 1201 is 345 km and the distance starting point of the pipeline 1202 is 344 km in the subsequent investigation. For this reason, the starting point of the distance is 344 km.
Here, the management items and units / notation of the general-purpose database (103) are:
Starting distance: Distance Unit: m
Start position: Start_Position Notation: Time notation according to 9:30 Corrosion length: Length Unit: mm
Corrosion width: Width Unit: mm
Corrosion depth: Depth_Rate Unit% (maximum depth / pipe thickness)
It is. For this reason, since the corrosion data of 1201 is different from general-purpose items, the correspondence relationship between general-purpose database items and input data items in the item name conversion data 106 is
Distance-Start Distance
Start_Position-Start_Pos
Length-Corrosion Length
Width-Corrosion Length
Depth_Rate-Maximum Corrosion Depth
It becomes. The unit / notation conversion data 105 is described as follows:
Start_Pos *. *
Start Distance −1000
It becomes. Since Length, Width, Maximum, and Corrosion Depth are the same as the units in the general-purpose database (103), the units are not changed. Here, Start Distance is supposed to add an offset of −1000 because the starting point of the distance is 344 km. Thus, the data once input to the general-purpose database (103) is re-input because the starting point of the distance is different. Since 1202 is also different from general-purpose items, the correspondence between general-purpose database items and input data items in the item name conversion data 106 is as follows.
Start_Length-S_Length
Start_Position-O'clock
Length-Length [m]
Width-Width [m]
It becomes. The unit / notation conversion data 105 is described as follows:
Lengh [m] m
Width [m] m
It becomes. In other cases, the unit / notation is not changed by checking the data in 1202.

1203 is a development view of the corrosion data 1201 and 1202. Corrosion numbers 1 to 4 of 1201 correspond to 1205, 1208, 1211, and 1214, respectively. Further, the numbers 1 to 4 of the corrosion of 1202 correspond to 1206, 1209, 1212, and 1215, respectively. A method for predicting corrosion expansion using these data is as follows. The time change of the length of the corrosion data is L [1], L [2], the width is W [1], W [2], and the depth is D [1], D [2]. [1] is data acquired in 2000, and [2] is data acquired in 2007.
Corrosion rate Vel
Vel = (L [2] -L [1]) / T21 (Equation 1)
It becomes. T21 indicates the time difference between two pieces of corrosion data acquisition. Thus, the corrosion length L at time T after 2007 is L = L [2] + Vel · T (Equation 2)
It becomes.

  Similarly, by changing L to W and D, respectively, the change rate of the corrosion width and the change rate of the corrosion depth are obtained. 1204, 1207, 1210, and 1213 are corrosion expansion prediction positions.

This prediction can improve the accuracy of the prediction because the corrosion progress acceleration is calculated if there is another piece of corrosion data. If there is corrosion data of L [0] before the corrosion data of L [1], the corrosion progress acceleration Acc is
Acc = (((L [2] -L [1]) / T21)-((L [1] -L [0]) / T10)) / T21 (Equation 3)
It becomes.
The corrosion rate Vel at time T is
Vel = ((L [2] -L [1]) / T21) + Acc · T (Equation 4)
It becomes.

  Here, the history data search is performed by the history search unit (1720), and the deterioration rate and acceleration calculation (corresponding to [Equation 1], [Equation 3], and [Equation 4]) based on this is performed. (1721). The deterioration calculation unit (1722) performs prediction calculation (corresponding to [Formula 2]). This prediction result can be superimposed on the pipeline shape in association with the pipeline shape data stored in the map shape database (1704). In this case, the prediction result is calculated by the distance, and this distance is associated with the pipeline shape.

  Even different data items can be used as the same data by storing them in the general-purpose database (103). Furthermore, it is also possible to obtain pipe exchange information from this data. Although the evaluation method differs depending on the country or region of use, a pipe durability determination graph (1301) as shown in FIG. 13 is presented. When corrosion occurs in the dangerous area (1304), it is a target for pipe replacement, and in the safety area (1302), it becomes a safety area. In addition, it may be necessary to make a judgment by an expert in a boundary region such as a region requiring attention (1303). The vertical axis is the length of corrosion, and the vertical axis is the depth of corrosion.

  Here, it is necessary to predict the time for transition from the safe area (1302) to the dangerous area (1304). This is based on prediction based on [Formula 1] [Formula 2] [Formula 3] [Formula 4]. Will do.

  Even if corrosion (1305) is included in the safety area (1302) at the time of measurement, if corrosion countermeasures are not taken, it will be included in the dangerous area (1304) after passing through a caution area (1303) as in 1306 after several years. Transition to corrosion 1307. In this way, the magnitude of the corrosion expansion is obtained according to the above formulas [Formula 1], [Formula 2], [Formula 3] and [Formula 4], and plotted on the pipe durability judgment graph 1301, which is changed from the safety region (1302) to the dangerous region. By calculating the period included in (1304), the number of years until the pipe replacement is calculated. Thereby, the number of years required for pipe replacement / repair can be obtained. This year makes it possible to give priority to pipe replacement and repair.

  Application to not only corrosion data but also cathode protection potential data is possible. If the cathode protection potential falls below a certain value, it is considered a pipe insulation abnormality. At this time, the insulating material covering the pipe is replaced.

As shown in FIG. 14, cathode protection potential data (1401) is cathode protection potential data acquired in April and October 2004, and 1402 is cathode protection potential data acquired in April and October 2005. It is assumed that (1403). Further, it is assumed that the pipeline distance starting point at the time of measurement 1401 and 1402 is 344 km and the distance starting point of the pipeline at the measurement time of 1403 is determined at 344 km by the subsequent investigation. For this reason, the starting point of the distance is 344 km.
The item of the general-purpose database (103) of cathode protection potential data is
Start distance: Start_Length Unit: m
ON voltage: Potential On Unit: mV
And The correspondence relationship between the general-purpose database item and the input data item in the item name conversion data (106) for 1401 is
Start_Length-S_Length
Potential On-P / S ON [mV]
It becomes. The unit / notation conversion data (105) is described as follows:
Length [km] −1000
It becomes. Correspondence between general-purpose database items and input data items in the item name conversion data (106) for 1402 is
Start_Length-Length [km]
Potential On-PS ON
It becomes.
The unit / notation conversion data (105) is described as follows:
Length [km] km
PS ON V
Length [km] −1000
It becomes.
In 1403, the correspondence relationship between the general-purpose database item and the input data item in the item name conversion data 106 is
Start_Length Length [km]
It becomes.
The description of the unit / notation conversion data 105 is as follows.
Length [km] km
Ps On [mV] mV
It becomes.

Thereby, the series data of the cathode protection potential of the pipeline is stored in the database in the same section. Next, the future prediction using the cathode protection potential data is performed. Since the cathode protection potential data is periodically acquired, prediction for each period is performed. When pipelines are buried, the properties of soil, etc. change from period to period. For example, if acquired in April and October, forecasts for April-October and October-April Do.
The acceleration rate of the change in cathode protection potential between April and October is
AcCP = (((V [3] -V [2]) / T32)-((V [1] -V [0]) / T10)) / T31
It becomes. V [0], V [1], V [2], and V [3] are ON voltages in April, October, October, and April, October, 2005, respectively. T32 is a time difference in measurement of V [2] and V [3], and T10 is a time difference in measurement of V [1] and V [0].
The rate of change is
VelCP = ((V [3] −V [2]) / T32) + αT (Equation 5)
T indicates the time after V [4] measurement. As a result, the cathode protective potential change from the new April to October is V [5] = V [4] + VelCP · T (Equation 6)
It becomes. V [4] is the ON voltage in April 2007. The same forecast can be made for the October-April forecast over the years. On the other hand, when the acceleration cannot be obtained, it is predicted by the speed. Note that for the prediction after April 2007, the prediction formula is changed from April to October and from October to April. As a result, when the upper limit threshold voltage and the lower limit threshold voltage determined in advance are exceeded, the pipe section becomes a dangerous area and an insulation replacement candidate area as an insulation abnormal section. Then, it is possible to determine the time for replacing the insulating material by predicting the time exceeding the threshold. 1040 is a graph of the cathode protection potential, and 1405 shows the distribution of the ON voltage. Reference numeral 1407 denotes a lower limit threshold, and a predicted value 1406 exceeding the lower limit threshold is superimposed and displayed (1409) on the pipeline shape (1408) on the map.

  These item name conversion and unit / notation conversion can also be used for pipeline construction. As item names, data such as pipe section length, pipe thickness, and inner diameter are subject to item name conversion and unit / notation conversion. By integrating these construction / repair data, it is possible to determine which section of the pipeline has been repaired or replaced, and thus the construction, repair, or replacement status of the entire pipeline can be determined.

Furthermore, a prediction method that considers a case where a part of the measurement intervals overlaps in time will be described. FIG. 15 shows the state of existence of piecewise measurement data. As sections of the pipeline 1501, 1502 and 1503 are 2004, section 1504 is 2005, and sections 1505 and 1506 are 2006 measurement sections. These measurement sections may appear partially in this way from the data preparation status. Then, by dividing these sections, it is possible to divide from section 1 (1507) to section 7 (1513). In such cases, the future is predicted from the available data. In section 1 (1507), data corresponding to the range of section 1 (1507) of measurement sections 1502 and 1505, and in section 2 (1508), it corresponds to the range of section 2 (1508) of measurement sections 1502, 1504 and 1505. In data, section 3 (1509), data corresponding to the range of section 3 (1509) of measurement sections 1502 and 1504, and in section 5 (1511), sections of measurement sections 1503 and 1504 and section 5 (1511) of measurement section 1506 In the data corresponding to the range, section 6 (1512), prediction is performed using data corresponding to the range of the section 6 (1512) of the measurement sections 1503 and 1506. In section 4 (1510) and section 7, only the measurement section data of measurement sections 1504 and 1506 can be used. Therefore, the measurement data is extracted further or the prediction is performed from one piece of data. When there is only one measurement time data as in section 4, the cathode protection potential of the section (section 4) is predicted from the cathode protection potential data of other sections (for example, section 3 and section 5). . Pipe deterioration can be predicted from the cathode protection potential data. When the prediction of section 4 is performed, it is performed as follows. First, prediction is performed using the data of the section 3 and the section 5 in which the parameter for which the change speed is obtained in the adjacent section is obtained. In section 3 (1509), the potential change rate from measurement sections 1502 and 1504 is Vel3. In section 5, if the speed obtained from measurement sections 1503 and 1504 is Vel5, the speed in section 4 (1510) is
Vel4 = (Vel3 + Vel5) / 2 ... [Formula 7]
It becomes.

  If the speed cannot be obtained in the section 3 (1509) or the section 5 (1511), the pipe section is further traced to expand the section having the usable change speed.

  Note that the accuracy can be improved by further subdividing the prediction section from the section shown in FIG.

The distances from the specific position of the pipe in the section 4 (1510) to the section 3 (1509) and the section 5 (1511) are L1 and L2, respectively. Then, the velocity Vel at the position to be predicted can be obtained as follows.
Vel = (Vel3 × L2 + Vel5 × L1)) / (L1 + L2) ... [Equation 8]
The closer to section 3 (corresponding to L1 approaching 0), the stronger the influence of the change speed Vel3 of section 3, and the closer to section 5 (corresponding to L2 approaching 0), section 5 The effect of change speed Vel5 becomes stronger.

FIG. 16 shows a case where a specific section does not have measurement data other than the case of FIG. For pipeline 1601, section 1 (1608) has measurement sections 1602, 1604, and 1606 for 2004, 2005, and 2006, and section 3 (1610) has measurement sections for 2004, 2005, and 2006. Although it has 1603, 1605, and 1607, it does not have in section 2 (1609). In this case, prediction of section 2 (1609) is performed using change speeds Vel1 and Vel2 of section 1 and section 3. Specifically, if the rate of change in section 2 is Vel,
Vel = (Vel1 + Vel2) / 2 ... [Formula 9]
To determine the rate of change using the average value. At this time, V1 and V2 are predicted speeds using the latest data.

  The present invention is applied to a case where data necessary for maintenance management is integrated for the purpose of managing a long facility structure such as a pipeline. In particular, it is necessary to identify the pipe section where pipe replacement or insulation protection material replacement is performed by making a future prediction based on historical data when comprehending the current state and problems of the pipeline and making a replacement / repair plan. is there. In such a case, it is necessary to centrally manage data reported by different management items by a plurality of organizations and manage them so that they can be used as history data. In the present invention, a method of converting to a general-purpose database (103) by data item conversion and unit / notation conversion is presented to enable this integrated management. Corrosion inspections organized by individually defined items, cathode protection potential data are stored in a unified database, and similar data is searched and displayed across sections, and analysis such as prioritizing countermeasures for problem areas It becomes possible to make such uses.

It is a figure which shows a function structure. It is a figure which shows the style of pipeline construction and measurement sharing. It is a figure which shows the example of a pipeline attribute item. It is a figure which shows item name conversion data. It is a figure which shows unit and description conversion data. It is a figure which shows the flow of additional registration to item name conversion data. It is a figure which shows the flow of the item registration to a unit and description conversion data. It is a figure which shows a data registration flow (the 1). It is a figure which shows a data registration flow (the 2). It is a figure which shows a data registration flow (the 3). It is a figure which shows a data registration flow (the 4). It is a figure which shows the log | history management of the corrosion data which have a different management item, and corrosion expansion prediction. It is a figure showing the prediction method of the pipe service life by corrosion prediction. It is a figure showing the history management by the cathode protection potential data which has a different management item, and a cathode protection potential change prediction. It is a figure which shows a divisional measurement area. It is a figure which shows the area where measurement data does not exist. It is the figure which detailed the application function of FIG. It is the figure which showed the cooperation of software and hardware. It is the figure which showed the meaning of Russian.

Explanation of symbols

  101 ... Pipe section measurement data, 102 ... Synonym database, 103 ... Attribute database, 104 ... Map shape database, 105 ... Unit / notation conversion data, 106 ... Item name conversion data, DESCRIPTION OF SYMBOLS 107 ... Data analysis interface part, 108 ... Item data extraction part, 109 ... Item name conversion part, 110 ... Unit / notation conversion part, 111 ... Database registration part, 112 ... Word Notation related item selection unit, 113... Unit / notation item registration unit, 114... Related item name search unit, 115... Item name registration unit, 116. Name reverse conversion unit, 118... Unit / notation reverse conversion unit, 119... Display unit, 120.

Claims (10)

A general-purpose database in which laying information of a plurality of pipelines with different laying locations and laying times is stored;
Item name conversion data for associating items of the input data with the items of the general-purpose database;
Unit / notation conversion data for associating the input unit / notation with the unit / notation of the general-purpose database, and
The general-purpose database stores the input data associated with the item name conversion data and the unit / notation conversion data together with time information,
Means for calculating deterioration rates and accelerations of the plurality of pipelines from a general-purpose database in which input data is stored together with the time information;
Means for predicting the degradation status based on the means for calculating the degradation status;
A pipeline information system comprising: means for specifying and outputting a pipeline section and timing to be newly repaired / laid based on the predicted deterioration state. Furthermore, it has a synonym database that stores synonyms,
2. The pipeline information system according to claim 1, wherein the synonym database is searched for the items of the input data, synonyms are extracted, and the items of the synonyms are associated with the items of the general-purpose database.   2. The pipeline information system according to claim 1, wherein the item name conversion data includes items of pipeline name, effective distance, effective period, general-purpose database item name, and input data item name. The general-purpose database accumulates history information of laying locations in the same section for each section,
2. The pipeline information system according to claim 1, wherein a section and a timing of a pipeline to be newly repaired / laid are specified from the history information. A general-purpose database in which laying information of a plurality of pipelines with different laying locations and laying times is stored;
Item name conversion data for associating items of the input data with the items of the general-purpose database;
Unit / notation conversion data for associating the input unit / notation with the unit / notation of the general-purpose database, and
The general-purpose database stores the input data associated with the item name conversion data and the unit / notation conversion data together with time information for each of a plurality of pipeline sections,
Means for calculating deterioration rates and accelerations of the plurality of pipelines from a general-purpose database in which input data is stored together with the time information;
Based on the means for calculating the deterioration status, means for predicting the deterioration status from the accumulated history information for sections other than the sections stored in the general-purpose database;
A pipeline information system comprising: means for specifying and outputting a pipeline section and timing to be newly repaired / laid based on the predicted deterioration state. Furthermore, it has a synonym database that stores synonyms,
6. The pipeline information system according to claim 5, wherein, for the input data item, the synonym database is searched to extract a synonym, and the synonym item is associated with the general-purpose database item.   For the sections other than the sections accumulated in the general-purpose database, the means for predicting the deterioration status from the accumulated history information is based on the average value of the change rates of the sections on both sides sandwiching the sections other than the sections accumulated in the general-purpose database. 6. The pipeline information system according to claim 5, wherein a deterioration state is predicted. A general-purpose database in which laying information of a plurality of pipelines with different laying locations and laying times is stored;
Item name conversion data for associating items of the input data with the items of the general-purpose database;
Unit / notation conversion data for associating the input unit / notation with the unit / notation of the general-purpose database, and
The general-purpose database stores the input data associated with the item name conversion data and the unit / notation conversion data together with time information for each of a plurality of pipeline sections, and the stored information is at different time points. And having the information of the section that is not common to the section that is common in the above, and dividing and managing the common section and the non-common section,
Means for calculating deterioration rates and accelerations of the plurality of pipelines from a general-purpose database in which input data is stored together with the time information;
Based on the means for calculating the deterioration state, the means for predicting the deterioration state of the pipeline in a predetermined section from the divided and managed information;
A pipeline information system comprising: means for specifying and outputting a pipeline section and timing to be newly repaired / laid based on the predicted deterioration state. Furthermore, it has a synonym database that stores synonyms,
2. The pipeline information system according to claim 1, wherein the synonym database is searched for the items of the input data, synonyms are extracted, and the items of the synonyms are associated with the items of the general-purpose database.   The means for predicting the deterioration state of the pipeline in the predetermined section predicts the deterioration state of the non-common section based on an average value of the change speeds of the common sections on both sides of the non-common section. 9. The pipeline information system according to claim 8, wherein

Images