JP4974648B2 - Bridge chart output program, bridge chart output method, and elevated structure data - Google Patents

Description

  The present invention relates to an elevated structure constructed by connecting a plurality of bridges, and an account book data in which information relating to members constituting the elevated structure is recorded, and an account book data in which information relating to a maintenance history for each member is recorded. In addition, the present invention relates to a program and method for causing a computer to output a member constituting an arbitrary bridge among a plurality of bridges constituting an elevated structure and information relating to its maintenance history. Further, the present invention relates to elevated structure data for recording information on members constituting such an elevated structure and information on maintenance history of the members.

FIG. 1 shows a configuration of a civil engineering structure that bridges a road from the ground. Such a civil engineering structure that bridges high roads and tracks from the ground is hereinafter referred to as “elevated structure” in the present specification and claims.
The elevated structure 50 mainly includes a bridge pier 53 that instructs the load of an upper structure such as a main girder 51 and a floor slab 52 that supports a road to be bridged, and a contact point between the main girder 51 and the pier 53, and has an upper structure. The bearing 54 is configured to safely transmit the weight to the lower structure, and the paved surface 55 and the like. The main girder 51 is spanned between two or more piers 53 (between spans), and the main girder 51 spanned between the two piers 53 is between a simple girder and three or more piers 53. The main girder 51 spanned by is called a continuous girder.
Here, the term “bridge” is generally used as a term indicating the entire elevated structure. However, in the elevated structure in which roads are continuously bridged between a plurality of bridge piers 53, A length of the range spanned by one main girder 51 in the entire elevated structure may be called a “bridge”. The specification and claims shall also be used according to this usage.

In addition, as the members constituting the elevated structure 50, there are a ground cover 56a, a balustrade 56b, drainers 57a and 57b, a sound insulation wall 58, a back sound absorbing plate 59, and the like.
The ground cover 56a is a protrusion-like structure installed at the extreme end of the width of the bridge surface to prevent the vehicle from deviating from the bridge surface, and the railing 56b prevents the vehicle from deviating from the bridge surface. It is a protective fence provided on the ground cover to prevent.
Further, the drainers 57 a and 57 b are concave stripes and protrusions for preventing raindrops connecting the lower surface of the floor slab 52 from leaking into the floor slab 52. The back surface sound absorbing plate 59 is a sound absorbing plate that prevents automobile noise traveling on the lower road from being reflected on the back surface of the elevated road.
In addition, for elevated structures, expansion joints (not shown) for connecting the pavement surfaces spanned between different floor slabs, and preventing the superstructure from falling in the event of an earthquake, etc. Therefore, members such as a bridge fall prevention device (not shown) for connecting the main girder 51 and the pier 53, and a bridge pier seismic reinforcement device (not shown) for preventing the pier from collapsing in the event of an earthquake, etc. Is provided.

  There is no prior art document to be described regarding the present invention. This is because the prior art known to the applicant is not related to the literature known invention.

Conventionally, the equipment specification data of the elevated structure as described above is managed by creating a different equipment ledger for each type of each member (that is, main girder 51, floor slab 52, pier 53, etc.) constituting the elevated structure. In addition, the maintenance history of the elevated structure was also managed by creating an inspection and repair ledger separately from these equipment ledgers.
However, in recent years, there has been a need to consider the priority order of repairs between different types of members because of the demand for more efficient maintenance costs for elevated structures. For this reason, when drafting an inspection plan and repair plan, facility specification data and maintenance histories of many types of members that make up the bridge part to be inspected and repaired manually from the equipment ledger and repair ledger created individually. You have to get in, and you've paid a lot of effort for this.

  In view of the above problems, in the present invention, for an elevated structure constructed by connecting a plurality of bridges, members constituting any bridge among these bridges and information relating to maintenance history thereof are used. The purpose is to extract and output to a computer from member ledger data in which information relating to constituent members is recorded separately in a plurality of ledgers for each type of member and maintenance ledger data in which information on maintenance history for each member is recorded. To do.

In order to achieve the above object, the present invention provides bridge ledger data for recording a bridge pier identifier indicating a pier supporting each of a plurality of bridges and a bridge identifier indicating a bridge supported by the pier. In addition, in the member ledger data and the maintenance ledger data, at least different records are provided for each member, and the pier identifier of the pier on which the member is provided is recorded in these records.
Then, the bridge designation process that designates one of the bridges to the computer that can access the material ledger data, maintenance ledger data, and bridge ledger data, and the record related to the designated bridge among the bridge ledger data are selected. First record selection processing to be performed, and second record for selecting a record that records the same pier identifier as the pier identifier recorded in the record selected by the first record selection processing from the member ledger data and the maintenance ledger data The selection process and the data output process for outputting the data of a predetermined field among the fields included in the records selected by the second record selection process are performed.
As a result of the above processing, the facility specification data and maintenance history of each member constituting the bridge portion of the bridge portion specified in the bridge specification processing of the elevated structure are created for each type of member. It can be easily extracted from the equipment ledger or a repair ledger created separately.

  According to the present invention, among the elevated structures constructed by connecting a plurality of bridges, the facility specification data and maintenance history relating to the members constituting any bridge are created by a plurality of facilities. Since it is possible to make the computer extract from the ledger and a repair ledger created separately from this, it is possible to save labor that has been required in the past when preparing inspection plans and repair plans .

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. FIG. 2 is a block diagram showing a hardware configuration example for executing a bridge chart output program according to an embodiment of the present invention.
The computer 1 includes a CPU 2, a memory 3 connected to the CPU 2, a display 4 and a printer 7 as data output devices, a keyboard 5 as a data input device, and a hard disk 6 as a storage device.
The hard disk 6 includes an operating system (OS) 10 necessary for operating the computer 1, a bridge chart application program 11 and a relational database application program 12, which respectively form a bridge chart output program according to an embodiment of the present invention. The elevated structure database 14 created by the relational database application program 12 and the bridge chart application program 11 can be used to access the elevated structure database 14 and use the database operation function of the relational database application program 12. The program interface component 13 and image data 15 such as a photograph of the elevated structure and a completed drawing are stored. To have.

In this configuration example, Microsoft Windows (registered trademark) of Microsoft Corporation is used as the operating system 10 and Microsoft Access (registered trademark) is also used as the relational database application program 12.
In addition, the bridge chart application program 11 is also created using Microsoft Visual Basic (registered trademark), and the structure is elevated via Active X Data Objects (ADO: ActiveX Data Objects) as the program interface component 13. The database 14 is accessed and the database operation function of the relational database application program 12 is used.

  FIG. 3 is a block diagram showing a list of each ledger data and image data 15 in the elevated structure database 14 stored in the hard disk 6. As shown in the drawing, the elevated structure database 14 includes a high rail cover ledger for recording equipment specification data of the handrail 56b and the ground cover 56a shown in FIG. 1, a pavement ledger for recording equipment specification data for the pavement 55, and a sound insulation wall. 58, a sound insulation wall ledger for recording equipment specification data, a backside sound absorbing board ledger for recording equipment specification data of the backside sound absorbing plate 59, a draining ledger for recording equipment specification data for the drainers 57a and 57b, and a floor slab 52. Floor ledgers for recording equipment specification data, expansion joint ledgers for recording equipment specification data for expansion joints (not shown), bearing ledgers for recording equipment specification data for bearings 54, and a bridge-bridge prevention device It has a falling bridge prevention ledger for recording equipment specification data (not shown) and a bridge pier seismic reinforcement ledger for recording a pier seismic reinforcement device (not shown).

The elevated structure database 14 is used for recording basic information such as the superstructure ledger for recording the equipment specification data of the superstructure, which is a structure provided on the main girder 51, and the location of the superstructure. It has a basic ledger and a substructure ledger that records equipment specifications data for piers and other substructures.
Each of these ledger data corresponds to the member ledger data in which information relating to members constituting the elevated structure is recorded in a plurality of ledgers for each type of the members described in the claims. In the present specification, in the following description, the above ledger data may be collectively referred to as “member ledger data”.

Furthermore, the elevated structure database 14 has an inspection / repair ledger for recording the inspection results and repair contents of each member constituting the elevated structure, and the inspection / repair ledger is described in the claims. This corresponds to maintenance ledger data in which information related to the maintenance history for each member is recorded.
In the present embodiment, each of the ledger data (the data in the range surrounded by the dotted line in the figure) is table data included in the elevated structure database 14 created by the relational database application program 12, and is a spreadsheet software. Existing table data created in advance using wear or the like is read into the elevated structure database 14 and used. By doing so, it is possible to use member ledger data and inspection / repair data that have been previously recorded in a computer-readable medium in a plurality of ledgers.

FIGS. 4 to 8 show table structures of a basic ledger, a balustrade cover ledger, a pavement ledger, a sound insulation wall ledger, and a back sound absorbing plate ledger, respectively. Each figure shows a column of fields, field names, and data types included in one record in the table. The same applies to FIGS. 10 to 15 and FIGS. 17 to 21 shown below.
In the group ledger shown in FIGS. 4 to 8, the installation position and facility specification data of each member are recorded using one record for each member. Here, the target of this group ledger is provided across the span shown in the side view of the elevated structure in FIG. 9 (that is, between the adjacent piers 53a and 53b and between the piers 53b and 53c). It is a kind of member. Therefore, in these ledgers, in order to distinguish between spans where each member is provided, each record has a start leg number field for recording a start leg number that is a bridge pier number at which the span starts, and a pier number at which the span ends. It has an end number field for recording the end number.

Moreover, the member which becomes the object of the ledger of this group is a member arrange | positioned for every direction of the road on a superstructure, or for every main line or a ramp lane. Therefore, when lanes with different directions are provided on the same superstructure, or when the main line and the ramp lane are provided on the same superstructure, there are a plurality of members provided in different lanes within the same span. Be placed. Therefore, in the ledger of this group, a direction field and a main lamp division field are provided in each record in order to distinguish the direction in which each member is provided and the main lamp.
Therefore, in the ledger of this group, a record for each member can be specified by using a combination of data stored in the start leg number field, end leg number field, direction field, and main line ramp section field as a key.

10 to 12 show the table structures of the superstructure ledger, drainer ledger and floor slab ledger, respectively. Even in these ledgers, one record is used for each member, and the installation position and facility specification data of each member are recorded.
The target of this group's ledger is the type of member provided across the span. Therefore, in these ledgers, in order to distinguish between spans where each member is provided, each record has a start leg number field for recording a start leg number that is a bridge pier number at which the span starts, and a pier number at which the span ends. It has an end number field for recording the end number.
And in the ledger of this group, the starting leg number field and the ending leg number field can be specified.

  These superstructure ledger, drainer ledger and floor slab ledger also have direction field and main line ramp section field, but these are installed on the superstructure and superstructure where drainer and floor slab are provided. The field is provided to indicate the direction of the road to be used and the main line lamp, and different lanes provided on the same superstructure as in the basic ledger are not distinguished.

FIG. 13 to FIG. 15 show table structures of the expansion joint ledger, the support ledger, and the falling bridge prevention ledger, respectively. Even in these ledgers, one record is used for each member, and the installation position and facility specification data of each member are recorded.
The member which is the target of this group is a member provided in the superstructure, but is not a member provided between a plurality of piers like the superstructure, but a member provided in each pier location. Accordingly, the ledger of this group has a pier number field for recording a pier number indicating a pier on which each member is provided.

Here, the expansion joint used as the object of the expansion joint ledger is a member arranged for each road direction on the superstructure, or for each main line or ramp lane. For this reason, in the expansion joint ledger, a direction field and a main ramp division field are provided in each record in order to distinguish the direction in which each expansion joint is provided and the main ramp.
In addition, the support subject to the support ledger is a member provided at the location of the pier, but at the location of the pier that is the boundary of the main girder, there is support for each of the two adjacent main girders supported by this bridge. Provided. This will be described with reference to FIG.
The main girder 51a is supported by three piers 53a, 53b, and 53c. Between the spans 53a to 53b, the pier 53a is defined as a start leg and the pier 53b is defined as an end leg, and between the spans 53b to 53c, 53b. And 53c is defined as the end leg.

As shown in the figure, the pier 53a is a boundary between the main girder 51a and the main girder 51b adjacent thereto, and supports 54a and 54d for supporting the main girder 51a and the main girder 51b are provided. A boundary between the main beam 51a and the adjacent main beam 51c is provided, and supports 54c and 54e are provided for supporting the main beam 51a and the main beam 51c, respectively.
In this way, since the bridge pier that is the boundary of the main girder is provided with a support that supports two adjacent main girder supported by this pier, a support position field is provided in the support ledger to distinguish these supports. In this embodiment, in the record that records the bearing 54a provided on the end point side of the start leg 53a, "end point side" is input in the support position field, and in the record that records the support 54c provided on the start point side of the end leg 53c. In the bearing position field, “starting point side” is entered. In the record that records the bearing 54b that supports the middle part of the main girder, “on the middle fulcrum” is entered in the bearing position field.

Similarly, the bridge prevention device that is the target of the bridge prevention ledger is also a member provided at the location of the pier, but each bridge is provided with a bridge prevention device for each main girder connected thereto. This will be described with reference to FIG.
As shown in the figure, the bridge pier 53a is provided with a falling bridge prevention device 60a that connects the main girder 51a and the pier 53a, and a falling bridge prevention device 60c that connects the main girder 51b and the pier 53a, and the pier 53c has the main girder 51a. And a bridge prevention device 60d for connecting the main girder 51c and the bridge pier 53c are provided.
In this way, since a plurality of fall prevention devices are provided for one bridge pier, the start leg / end leg classification field is provided in the fall prevention book to distinguish these fall prevention devices. In the present embodiment, in the record that records the fallen bridge prevention device 60a provided on the end point side of the start leg 53a, “end leg” is input in the start leg / end leg classification field, and the fall bridge prevention provided on the start point side of the end leg 53c. In the record for recording the device 60b, “start leg” is input in the start leg / end leg classification field.

17 and 18 show the table structures of the substructure ledger and the bridge pier seismic reinforcement ledger, respectively. Even in these ledgers, one record is used for each member, and the installation position and facility specification data of each member are recorded.
Members that are the subject of this group are members provided at each pier location. Therefore, this group ledger has a field to record the pier number indicating the pier on which each member is provided, the substructure ledger records the pier number in the first pier number field, and the pier seismic reinforcement ledger records the pier number. Record the pier number in the field.

FIG. 19 shows the table structure of the inspection / repair ledger. The inspection and repair ledger records the results of inspections and repairs inspecting elevated structures, and the inspection results or repair contents are recorded in different records for each member and each time inspection or repair is performed. To be recorded.
As shown in the figure, the inspection and repair ledger has a year field (column B) that records the year in which inspection or repair was performed, a structure field (column D) that indicates the type of member that has undergone inspection or repair, an inspection location, or a repair location. Start leg number field and end leg number field (F and G columns), secondary judgment field (J column) indicating the result of inspection, quantity field (K column) indicating the number of inspection and repair points, and repair An emergency response implementation date field (M column) indicating the date is provided.

  In the inspection and repair ledger, when the object of inspection or repair is a member provided across the span, such as a superstructure, the pier number at both ends of the span where the object of inspection or repair is provided is the starting leg. Record in the number field and end pier number field, and when the object of inspection or repair is a member provided at the location of a pier such as a substructure, the pier number of the pier where the object of inspection or repair is provided Record in the starting leg number field.

  Returning to FIG. 3, the elevated structure database 14 includes the member ledger data divided for each type of member surrounded by the dotted line shown in FIG. 3 and the inspection / repair ledger separately created for each bridge. In other words, according to the usage of the term “bridge” described above, the facility specification data of the members in the range of the bridge for each length part of the range spanned by one main girder in the entire elevated structure. And a bridge ledger used to extract inspection and repair data. FIG. 20 shows the table structure of the bridge ledger.

The bridge ledger has a bridge ID field (A column) for recording a bridge ID, which is a uniquely assigned bridge identifier for one bridge, and a start leg number field and an end leg number field (F column and G column). The ledger indicates that the span indicated by the start leg number field and the end leg number field is included within the range of the bridge indicated by the bridge ID field.
The bridge ledger has a different record for each span, and records the same bridge ID in the bridge ID field of each record indicating the span included in the same bridge. Thus, if a bridge is a continuous girder spanning multiple spans (ie, one main girder spans three or more piers), multiple records are used for one pier, In these records, a start leg number and an end leg number indicating bridge numbers at both ends of each span are recorded, respectively, and the same bridge ID is recorded in the bridge ID field.

With reference to FIG. 9, the range of the structure which one bridge ID shows, and the range between each diameter contained in this are demonstrated. The bridge on which the main girder 52a is bridged is a two-span continuous girder, and the main girder 52a is spanned on three piers 50a-50c, and this bridge includes two spans 53a-53b and 53b-53c. ing.
In this case, in the bridge ledger, a record in which the bridge pier numbers at both ends of the spans 53a to 53b are recorded in the start leg number field and the end leg number field for the bridge with the main girder 52a, and the span span, respectively. Records for recording the pier numbers at both ends of 53b to 53c in the start leg number field and the end leg number field are provided separately, and the same bridge ID is recorded in the bridge ID fields of these two fields.
In the bridge ledger, a bridge pier number field (column D in FIG. 20) for recording the pier number of the pier 53a supporting the start point of the main girder 52a, and a bridge ending leg for recording the pier number of the pier 53c supporting the end point. A number field (G column in FIG. 20) is provided.

If the bridge ledger is defined in this way, a record that records the bridge for which data is to be displayed and output is selected from the bridge ledger, all other records having the same bridge ID are extracted, and these records are extracted. By referring to the start leg number field and the end leg number field, it is possible to obtain all the pier numbers of the piers supporting the selected bridge. And by extracting the records that record these pier numbers using the acquired pier numbers as keys from the member ledger data and the inspection / repair ledger, the equipment specification data of the members provided in the selected bridge part and A record in which inspection / repair data is recorded can be extracted.
The table structures shown in FIGS. 4 to 8, 10 to 15, and 17 to 20 are exemplifications in which only field names necessary for explaining the present embodiment are listed. May provide more fields according to actual management items.

The elevated structure database 14 further includes a bridge finding prescription table, a remarks table, and a drawing photo table shown in FIG.
The bridge findings prescription table is a table that records the inspector's findings and repair work prescriptions as comments for each bridge, and each record is a bridge ID field (column B) that records the bridge ID of the target bridge. And a finding field (column C) for recording findings and a prescription field (column D) for recording prescriptions.
The remark table is a table for recording a memo or the like as a comment for each bridge. Each record has a bridge ID field (column B) for recording a bridge ID of a target bridge, and a remarks field for recording a comment ( Column C).
The drawing photograph table is a table that records drawings and photographs of the bridge and each member constituting the bridge for each bridge, and each record has a bridge ID field (B that records the bridge ID of the target bridge). Column), a type field (column C) indicating the distinction between drawings and photos, and a file path field (column D) for recording path names in the hard disk 6 in which image data of drawings and photos to be recorded are stored. A file name field (E column) for recording a file name of image data of a drawing or photo to be recorded and a comment field (F column) for recording a memo about the drawing or photo.

Hereinafter, the relationship between the table data described above will be described with reference to FIGS. As is well known, in a relational database, by connecting each common field between a plurality of tables and using a selection query, records in each table having the same value in these common fields are connected to each other. It can be handled like a record.
In this embodiment, the relationship is mainly between the start and end number fields of the bridge ledger and the start and end number fields and end and end number fields of each member register data and inspection / repair ledger. It is used to connect the bridge ledger to each member ledger data and inspection / repair ledger.

FIG. 22 is a diagram showing a relationship provided between the bridge ledger and the superstructure ledger. As described above with reference to FIG. 10, in the upper work ledger, in order to distinguish between the spans where the members are provided, the start leg number field for recording the start leg number at which the span starts and the end leg number at which the span ends. On the other hand, the bridge ledger has a start leg number field for recording a start leg number starting from each span included in each bridge portion as described above, and the span ends. It has an end number field for recording the end number.
Therefore, as shown in the figure, there is a relationship between the start leg number field of the upper construction ledger and the start leg number field of the bridge ledger, and between the end leg number field of the upper work ledger and the start leg number field of the bridge ledger. Provide.
In FIG. 22, a state in which a relationship is provided between fields is shown by connecting the fields in which the relationship is provided with dotted lines. The same applies to FIGS. 23 to 31 and 33.

  In addition, even if the same pier number is assigned to the piers with different road routes, directions, main lines, and ramp lanes, the upper ledgers can be distinguished between the route name fields in the upper ledgers and bridge ledgers. And a relationship between the direction fields of the bridge ledger and between the main ramp sections of the superstructure ledger and the bridge ledger.

  FIG. 23 is a diagram showing a relationship provided between the bridge ledger and the basic ledger. As described above with reference to FIG. 4, in order to distinguish between the spans in which the members are provided in the basic construction ledger, the start leg number field for recording the start leg number at which the span starts and the end leg number at which the span ends. Has an end number field for recording. Therefore, similar to the superstructure ledger, between the start number field of the superstructure book and the start number field of the bridge book, and between the end number field of the superstructure book and the start number field of the bridge book, respectively. Establish relationships. Similarly to the superstructure ledger, a relationship is provided between the route name fields of the basic ledger and the bridge ledger.

On the other hand, as described above with reference to FIG. 4, when a lane in a different direction is provided on the same superstructure or when a main line and a ramp lane are provided on the same superstructure, For the superstructure of the same span portion, different records are provided for each lane and / or for each main line ramp. For this reason, identification information for distinguishing the direction is recorded in the direction field, and identification information for distinguishing the main lamp is recorded in the main lamp classification field.
However, in the superstructure ledger and bridge ledger, even if lanes and main lines and ramp lanes in different directions are provided on the same superstructure, in principle, one record is allocated between one span, The content recorded in the main lamp section field is not information that can distinguish the direction and the main lamp. For this reason, the information recorded in the direction field and the main line ramp section field differs between the basic ledger and the bridge ledger.

For this reason, the main ledger record is provided with a main ramp division (superstructure) field and a direction (superstructure) field (S column and T column in FIG. 4). The main line indicator (superstructure) field and direction (superstructure) field of each record in the basic ledger include the values of the start number field and pier number field of the record, and the same start number field and pier number field. Record the same contents as the main ramp section field and the direction field of the superstructure ledger record having a value.
Then, a relationship is provided between the main ramp section (superstructure) field of the basic ledger and the main ramp section field of the bridge ledger, and the direction of the basic ledger (superstructure) field and the direction field of the bridge ledger.

FIG. 24A is a diagram showing the relationship provided between the balustrade ledger and the basic ledger, and FIG. 24B shows the relationship provided between the pavement ledger and the basic ledger. FIG. 25A is a diagram showing a relationship provided between the sound-insulating wall ledger and the basic ledger, and FIG. 25B is provided between the back-side sound absorbing plate ledger and the basic ledger. It is a figure which shows a relationship.
As described above with reference to FIGS. 4 to 8, in the railing ledger, pavement ledger, sound insulation wall ledger, and back surface sound absorption board ledger, records are assigned for each direction or for each main line lamp as in the basic ledger. Therefore, between each of these ledgers and the basic ledger, between the route name fields, between the start number fields, between the end number fields, between the main ramp division fields and between the direction fields. A relationship is established between them.
These four ledgers are connected to the bridge ledger by the relationship between the respective ledger and the basic ledger and the relationship between the basic ledger and the bridge ledger.

FIG. 26A is a diagram showing a relationship provided between the draining ledger and the bridge ledger, and FIG. 26B is a diagram showing a relationship provided between the floor slab ledger and the bridge ledger. It is. The draining ledger and the floor stencil ledger are connected to the bridge ledger by the relationship between the respective ledger and the superstructure ledger and the relationship between the superstructure ledger and the bridge ledger.
As described with reference to FIGS. 10 to 12, in these draining ledgers and floor slab ledgers, records are assigned for each span as in the case of the upper construction ledger. Accordingly, between each of these ledgers and the superstructure ledger, a relationship is provided between the start number fields and between the end number fields. Similarly to the relationship between the superstructure ledger and the bridge ledger, between the draining ledger, the floor slab ledger, and the superstructure ledger, between the route name fields, between the main ramp division fields, and the direction field There is a relationship between them.

  FIG. 27A is a diagram showing the relationship provided between the supporting ledger and the pier number query described below, and FIG. 27B is provided between the falling bridge prevention ledger and the pier number query. It is a figure which shows the relationship made. The support ledger and the falling bridge prevention ledger are linked to the bridge ledger by a relationship with a pier number query that is a query created from the bridge ledger.

As described with reference to FIG. 13 to FIG. 15, the members constituting the elevated structure include a member of a type provided across the span like an upper work, and a bridge pier like a support and a falling bridge prevention device. There is a kind of member provided at the location.
Ledger data relating to the types of members provided across the span, for example, the superstructure ledger and the basic ledger, have a start leg number and an end leg number representing the span as data indicating the installation location of the member. Also, in the bridge ledger indicating the span included in the range of each bridge, the span included in the range of each bridge needs to be represented, and therefore the span is designated by the start leg number and the end leg number in the same manner.

On the other hand, as described with reference to FIGS. 13 to 15, the support ledger and the fallen bridge prevention ledger that are ledger data related to the types of members provided at the piers are the start data representing the span as the data indicating the installation points. It has no pier number and no end limb number and one pier number.
Here, for example, a relationship is established between the bridge ledger and the support ledger between the bridge ledger and the falling bridge prevention ledger, and it is considered to extract a support and a falling bridge prevention device provided in a specific bridge section. At this time, if a relationship is established between the pier number field of the support ledger and the bridge prevention ledger (hereinafter referred to as “support ledger etc.”) and the start limb number field of the bridge ledger, it will be provided on the pier supporting the end point of the bridge. In the same way, if a relationship is established between the pier number field of the support ledger etc. and the end limb number field of the bridge ledger, the support provided on the pier supporting the start point side of the bridge It becomes impossible to extract the fall prevention device.

  For this reason, by combining the selection query that extracts the bridge ID and the starting leg number field of each record of the bridge ledger with the selection query that also extracts the bridge ID and the end number field, the bridge ID is obtained for each bridge. And a pier number query that extracts pairs of pier numbers of the piers that support the bridge for all of the piers that support the bridge. An example of such a pier number query is described in SQL (Structured Query Language) language as follows.

SELECT Bridge leg, Bridge ID,
Bridge start pier number AS pier number,
Bridge start leg, route name,
IIf (Bridge start leg. Start leg number = Bridge start leg. Bridge start leg number, "end side", "on intermediate fulcrum") AS bearing position,
IIf (Bridge start leg. Start leg number = Bridge start leg. Bridge start leg number, "end leg", Null) AS start leg end leg classification,
Bridge start leg, main ramp classification,
Bridge leg.
FROM Bridge Ledger AS Bridge First Leg
UNION SELECT Bridge end leg, Bridge ID,
End of the bridge.End number AS Pier number,
End of the bridge.
IIf (Bridge end leg. End leg number = Bridge end leg. Bridge end leg number, "Starting point side", "Intermediate fulcrum") AS bearing position,
IIf (Bridge end leg. End leg number = Bridge end leg. Bridge end leg number, "Start leg", Null) AS Start leg end leg classification,
Bridge end leg, main line ramp classification,
End of the bridge.
FROM bridge ledger AS bridge end;

  By executing the pier number query, the pier identifiers of all the bridges that support this bridge are extracted from the record for the given bridge selected from the bridge ledger, so execution of the pier number query is within the scope of the claims. Corresponds to the described pier identifier extraction process. The above SQL description describing the pier number query corresponds to the query definition data described in the claims.

Between the pier number query and the support ledger, relationships are provided between the route name fields, between the pier number fields, between the main line ramp section fields, and between the direction fields.
In addition, as described with reference to FIG. 16, each record in the support ledger is a support that supports a bridge that starts with this pier even if the support is provided on the same pier. In order to distinguish whether it is a support that supports the bridge, a support position field is provided. If the target support supports the start point side of the bridge (that is, the start point side of the main girder), the end point side is displayed in the support position field. When it is input and the end point side of the bridge is supported, “starting point side” is input in the support position field. When the intermediate part is supported, “on the intermediate fulcrum” is entered in the support position field.
For this reason, as shown in the SQL description above, the pier number query uses the value of “end point side” when the pier number is equal to the start point number of the bridge, and “start side” when the pier number is equal to the end number of the bridge. ", And in other cases, a bearing position field having a value of" on the intermediate fulcrum ", and a relationship is provided between the bearing position fields between the pier number query and the bearing ledger.

Similarly, each record in the bridge prevention ledger distinguishes whether a bridge prevention device installed on the same pier is connected to a bridge that uses this pier as the starting leg or a bridge that uses the pier. For this purpose, a start leg / end leg section field is provided, and when the target fall prevention device is connected to the start point side of the bridge (that is, the start point side of the main girder), “end leg” is displayed in the start leg / end leg section field. Is input and “start leg” is input in the start leg / end leg classification field.
For this reason, as shown in the SQL description above, the pier number query uses the “end” value when the pier number is equal to the start number of the bridge, and “start” when the pier number is equal to the end number of the bridge. And a relationship is established between the start and end leg field between the pier number query and the falling bridge prevention ledger.

  FIG. 28 is a diagram showing a relationship among the pier number query, the basic ledger, and the expansion joint ledger. The expansion joint ledger is connected to the bridge ledger by the relationship between the expansion joint ledger and the basic ledger and the relationship between the basic ledger and the pier number query. In the expansion joint ledger, a record is assigned to each pier on which the expansion joint is provided in the same manner as the support ledger and the like, and a record is assigned for each direction or for each main line lamp as in the basic ledger.

Therefore, first, the route name field, pier number field, main ramp division field and direction field of the pier number query, and the route name field, start pier number field, main ramp division field (superstructure) and direction field (superstructure) of the basic ledger. ) And a pier number query and a basic ledger are connected. By doing this, for each pier number in the pier number query, if lanes with different directions are provided on the same pier, a record is provided for each direction, and main line and ramp lane are provided on the same pier A table is generated in which a record is provided for each of the main line and the ramp lane.
The relationship between the route name field, the pier number field, the main ramp division field and the direction field of the expansion joint ledger and the route name field, the start leg number field, the main ramp division field and the direction field of the basic ledger To connect the expansion joint ledger and the basic ledger.

FIG. 29A is a diagram showing the relationship between the substructure ledger and the pier number query, and FIG. 29B shows the relationship between the pier seismic reinforcement ledger and the pier number query. FIG.
In the substructure ledger, records are assigned to each pier location where the substructure is provided, as in the case of the support ledger, etc., so the route name field and the start limb number field of the substructure ledger, and the route name field of the pier number query In addition, a relationship is established between the pier number field and the pier number field to connect the substructure ledger and the bridge ledger.

  In the pier seismic reinforcement ledger, records are assigned to each location of the pier where substructures are provided in the same way as the support ledgers, etc., so between the pier seismic reinforcement ledger and the pier number query route name fields and the pier number field A relationship is established between them to connect the bridge pier seismic reinforcement ledger and the bridge ledger.

30 and 31 are diagrams illustrating a method for generating a combined inspection / repair query generated by connecting an inspection / repair ledger and a bridge ledger. As described with reference to FIG. 19, the inspection / repair ledger is generated by assigning different records to each member and each time inspection / repair is performed. Are stored in the structure field and in the start leg number field and the end leg number field indicating the inspection or repair point.
Here, if the member that has been inspected or repaired is a member installed across the span, the records generated for this member are inspected by specifying the span (ie, the start leg number and the end leg number). If the repaired part is specified, and the member that has been inspected or repaired is a member installed at the pier part, it is necessary to specify the pier number and specify the part that has been inspected or repaired.

  Therefore, a structure table as shown in FIG. 32 is provided in the elevated structure database 14. The structure table is a structure field that records the type of member, and a type field that indicates whether the member is a type of member that is installed across the span or a type of member that is installed at a bridge pier. Have When the member recorded in the structure field is a member installed across the span, the type field has the value of “superstructure”, and when the member is installed at the location of the pier, the type field is “ It has a value of “under construction”.

Then, as shown in FIGS. 30A and 31A, the inspection / repair ledger and the structure table are joined to each other by providing a relationship between the structure fields.
And for the record whose type field value of the table generated by combining in this way is “superstructure”, as shown in FIG. 30A, the route name field of the inspection / repair ledger and the bridge ledger The inspection repair ledger and the bridge ledger were joined by providing relationships between each other, between the start leg number fields, between the end leg number fields, between the main ramp division fields and between the direction fields. Above, the selection query which has the field shown to (B) of Drawing 30 is generated.

  As shown in FIG. 30B, for the record in which the value of the type field generated by combining the inspection / repair ledger and the structure table is “under construction”, the route of the inspection / repair ledger and the pier number query is shown in FIG. Inspect and repair ledgers by establishing relationships between name fields, between main ramp division fields and between direction fields, and between the start limb number field of the inspection and repair ledger and the pier number fields of the pier number query. And the selection query which has the field shown to (B) of Drawing 31 is generated after combining pier number queries.

  The selection queries shown in FIG. 30 (B) and FIG. 31 (B) are the bridge ID field, inspection / repair ID field, year field, inspection type field, A damage field, B damage field, A repair field, and B repair. A field, a quantity field, a damage summary field, and a structure field. Each field has the following values.

  The inspection / repair ID field, year field, inspection type field, quantity field, damage summary field, and structure field value of the record in the selected query are the inspection / repair ID record, year field of the inspection / repair ledger record corresponding to this record. These are the values recorded in the inspection type field, quantity field, damage summary field, and structure field.

The A damage field of the record in the selection query is assigned the value of “A” when the value of the secondary determination field of the record of the inspection / repair ledger corresponding to this record is “A”, otherwise Has no value.
The B damage field of the record in the selection query is assigned the value of “B” when the value of the secondary judgment field of the record of the inspection / repair ledger corresponding to this record is “B”, otherwise Has no value.

In the A repair field of the record in the selection query, when the value of the secondary determination field of the inspection / repair ledger record corresponding to this record is “A”, the emergency response execution date field of the inspection / repair ledger record A value is assigned, otherwise it has no value.
In the B repair field of the record in the selection query, when the value of the secondary determination field of the record of the inspection / repair ledger corresponding to this record is “B”, the emergency response execution date field of the record of the inspection / repair ledger A value is assigned, otherwise it has no value.

In the selection query of FIG. 30B, the bridge ID field of the record in the query has the same start leg as the set of the start leg number and end leg number values of the inspection / repair ledger record corresponding to this record. The bridge ID value of the bridge ledger record having a set of number and end leg number values is substituted. This value becomes the bridge ID of the bridge to which the span, which is the inspection or repair location indicated by the record of the inspection / repair ledger corresponding to the record in the selection query, belongs.
On the other hand, in the selection query of FIG. 31 (B), the bridge ID field of the record in the query has the same pier number value as the start limb number value of the inspection / repair ledger record corresponding to this record. The bridge ID of the pier number query having is substituted. This value is the bridge ID of the bridge to which the bridge pier that is the inspection or repair location indicated by the record of the inspection / repair ledger corresponding to the record in the selection query belongs.

  Then, by combining the selection queries shown in FIG. 30B and FIG. 31B, these members are provided for both the members installed across the span and the members installed at the piers. It is possible to generate a combined inspection / repair query in which the bridge ID of the bridge to be connected and the inspection result or the content of the repair performed on each member are connected. By selecting a record in the combined inspection / repair query using the bridge ID as a key, it is possible to extract the inspection result or the content of the repair performed on each member constituting an arbitrary bridge. An example of such a combined inspection / repair query is described in SQL language as follows.

SELECT
Superstructure bridge.Bridge ID AS Bridge ID,
Superstructure inspection, inspection and repair ID,
Superstructure inspection.
Superstructure inspection, inspection type AS inspection type,
IIf (Superstructure inspection. Secondary judgment = "A", Superstructure inspection. Secondary judgment) AS A damage,
IIf (Superstructure inspection, secondary judgment = “B”, Superstructure inspection, secondary judgment) AS B damage,
IIf (Superstructure inspection. Secondary judgment = “A”, Superstructure inspection. Emergency response implementation date) AS A repair,
IIf (Superstructure inspection. Secondary judgment = “B”, Superstructure inspection. Emergency response date) AS B repair,
Superstructure inspection.Quantity,
Superstructure inspection, damage summary,
Superstructure.structure AS structure,
Superstructure
FROM bridge ledger AS superstructure bridge, inspection repair ledger AS superstructure inspection,
Structure table AS Superstructure
WHERE Superstructure. Type = "Superstructure"
AND superstructure bridge direction = superstructure inspection direction
AND Superstructure bridge. Main ramp classification = Superstructure inspection. Main ramp classification
AND superstructure bridge, end number = superstructure inspection, end number
AND superstructure bridge, starting leg number = superstructure inspection, starting leg number
AND Superstructure bridge.Route name = Superstructure inspection.Route name
AND Superstructure inspection.Structure = Superstructure.Structure
AND Superstructure inspection.Secondary judgment is not null
UNION SELECT
Substructure bridge.Bridge ID AS Bridge ID,
Substructure inspection, inspection and repair ID,
Substructure inspection, AS year,
Substructure inspection. Inspection type AS inspection type,
IIf (Superstructure inspection. Secondary judgment = "A", Superstructure inspection. Secondary judgment) AS A damage,
IIf (Superstructure inspection, secondary judgment = “B”, Superstructure inspection, secondary judgment) AS B damage,
IIf (Superstructure inspection. Secondary judgment = “A”, Superstructure inspection. Emergency response implementation date) AS A repair,
IIf (Superstructure inspection. Secondary judgment = “B”, Superstructure inspection. Emergency response date) AS B repair,
Substructure inspection.Quantity,
Substructure inspection, damage overview,
Substructure, AS structure,
Substructure
FROM pier number query AS substructure bridge, inspection and repair ledger AS substructure inspection, structure table AS substructure
WHERE Substructure. Type = "Substructure"
AND Substructure inspection, route name = substructure bridge, route name
AND Substructure inspection.Start leg number = Substructure bridge.Bridge number
AND Substructure inspection.Structure = Substructure structure.Structure
AND Substructure inspection.Secondary judgment is not null;

  33A is a diagram showing the relationship between the bridge finding prescription table and the bridge ledger, and FIG. 33B is a diagram showing the relationship between the remarks table and the bridge ledger, FIG. 33C shows a relationship between the drawing photo table and the bridge ledger. The bridge finding prescription table, the remarks table, the drawing photo table, and the bridge ledger are linked to each other by providing a relationship between the bridge IDs.

  It should be noted that the relationship information that defines the above-described relationships, and the query definition data that defines the pier number query and the combined inspection / repair query can be stored in the elevated structure database 14.

  Subsequently, the operation of the bridge chart application program 11 will be described with reference to FIGS. 34 to 56. FIG. 34 is a flowchart of the main routine of the bridge chart application program 11. The bridge chart application program 11 is written in Microsoft Visual Basic (registered trademark) and is created using an object-oriented programming technique. In the bridge chart application program 11, a form in which each object is embedded is displayed on the display 4, and when the user operates the displayed object, the computer 1 executes a process corresponding to the operated object. Works.

  When the program is executed, the computer 1 calls a bridge search form shown in FIG. 35 in step S10. In the bridge search form shown in FIG. 35, by entering “route name”, “point name”, “main line ramp classification”, “direction”, and “pier pier number” which are predetermined management keys, A record having data matching the management key input from is retrieved.

FIG. 36 is a flowchart showing a processing procedure executed by the bridge search form.
In step S11, the computer 1 accepts input of a management key (search condition) from the user to the management key input field 101 of the bridge search form, and waits until the bridge search button 102 is pressed in step S12.
When the bridge search button 102 is pressed, in step S13, the computer 1 determines whether or not the management key is properly input in the management key input field 101. If the management key is set, In step S14, the computer 1 executes a selection query for the bridge ledger through the program interface component 13 such as the above-mentioned ADO, so that records having data matching the input management key are retrieved from the bridge ledger. Search for. As a result of the search, a list of selected records is displayed in the bridge list 103.

In step S15, the computer 1 accepts a user's selection instruction for selecting one of the bridge lists displayed in the bridge display field 103, and waits until the bridge chart display button 104 is pressed in step S16.
When the bridge chart display button 104 is pressed, in step S17, the computer 1 determines whether any of the displayed bridge lists is selected, and if a bridge is selected, the step is performed. In S18, the computer 1 passes the bridge ID of the selected bridge to the data display / input form and calls the data display / input form (step S20 in FIG. 34).

FIG. 37 is a diagram showing another embodiment of the bridge search form. In the bridge search form shown in FIG. 37, select either a bridge ledger or a ledger of member ledger data such as superstructure ledger or basic ledger, select a field in the selected ledger, and search the value of that field Enter as a condition.
In step S11 of the flowchart of FIG. 36, the computer 1 accepts input of the ledger type and field selection instruction from the user to the ledger item input field 105 of the bridge search form and the input of the field value as the search key.
In step S14, the computer 1 is input by executing a selection query in which the ledger selected in step S11 and the bridge ledger are linked by relationships as shown in any of FIGS. Search the bridge ledger for records having data that matches the search key.

  FIG. 38 shows a data display / output form. In the data display / output form, the user displays each data recorded in the bridge ledger, member ledger data, inspection / repair ledger, etc. on the display 4 for the bridge selected by the bridge search form, or outputs it as a file. be able to. The user can select display contents by selecting one of the forms listed in the operation menu column 111. FIG. 39 is a flowchart showing a processing procedure executed by the data display / output form.

In step S <b> 21, the computer 1 accepts a selection instruction from a user who selects one of the form lists displayed in the operation menu column.
The computer 1 determines that the form selected in step S21 is any one of the bridge chart, basic information on the bridge, bridge structure specifications, repair status on the suspended scaffold, repair status on the partial scaffold, high-speed repair status, and inspection repair history. In some cases, the display is switched to the respective display forms shown in FIGS. 38 and 40 to 45 (steps S22 and S23), and data corresponding to the display contents of each form is displayed (step S24).

When the form selected in step S21 is the bridge finding prescription form, the computer 1 calls the bridge finding prescription form shown in FIG. 46 (steps S25 and S40). If the form selected in step S21 is a remark form, the remark form shown in FIG. 48 is called (steps S26 and S50).
Further, when the form selected in step S21 is a drawing form, the computer 1 calls the drawing form shown in FIG. 50 (steps S27 and S60). If the form selected in step S21 is a photograph form, the photograph form shown in FIG. 52 is called (steps S28 and S80).
Further, when the form selected in step S21 is the data output form, the computer 1 calls the drawing form shown in FIG. 54 (steps S29 and S100).
When the “return to bridge search” button 112 is pressed, the computer 1 calls the bridge search form shown in FIG. 35 again to end the data display / output form (steps S30 and S10). When pressed, the program is terminated (step S31).

The form shown in FIG. 38 displays a bridge chart such as a structural outline and an inspection / repair history outline regarding the bridge selected by the bridge search form. The contents displayed in the display columns 114 to 116 are as follows.
The contents displayed in the bridge information column 114 are as shown in the following table.

In Table 1, the “display item name” column indicates the item name displayed on the form, and the “source table / query” column indicates the name of the ledger or query from which the displayed data is extracted. In the column of “extraction source field”, the name of a field from which data is extracted from the table or query specified in the column of “extraction source table / query” is shown.
The column “display format” indicates a display method when the extracted data is processed at the time of display, and is blank when the extracted data is displayed as it is.

  When each table or query shown in the column “source table / query” is a bridge ledger, the computer 1 uses the bridge ID selected in the bridge search form as a key to program interface A record having the selected bridge ID is extracted by executing a selection query for the bridge ledger via the component 13, and data to be displayed is extracted from the “extraction source field” in the extracted record.

When each table or query shown in the column “source table / query” is a ledger or query other than the bridge ledger, the computer 1 uses the bridge ID selected in the bridge search form as a key. Then, the selection query in which the ledger or query shown in the “table / query to be extracted” and the bridge ledger are linked by the relationship is executed.
The relationships to be provided between each of the ledgers or queries shown in the “table / query to be extracted” and the bridge ledgers are as shown in FIGS. Then, the computer 1 extracts data to be displayed from the ledger or the query and record “extraction source field” indicated in the “extraction source table / query” extracted as a result of executing the selected query.
The same applies to Tables 2 to 21 below. Note that the query definition data defining each of the selection queries executed by the computer 1 can be held in the elevated structure database 14.

  The contents displayed in the structure summary column 115 are as shown in Table 2 below.

  The contents displayed in the inspection / repair history summary 116 are as shown in Table 3 below.

FIG. 40 is a diagram showing a state where basic bridge information is displayed. This display screen displays basic information about the bridge selected by the bridge search form, and has a span information column 120 and a position information column 121.
The contents displayed in the span information column 120 are as shown in Table 4 below.

  The contents displayed in the position information column 121 are as shown in Table 5 below.

FIG. 41 is a diagram showing a state in which bridge structure specifications are displayed. This display screen displays the structural specification information of the bridge selected by the bridge search form, and has an upper work column 130, a floor slab column 131, a balustrade cover column 132, and a lower work column 133.
The contents displayed in the superstructure column 130 are as shown in Table 6 below.

  The contents displayed in the floor slab column 131 are as shown in Table 7 below.

  The contents displayed in the high rail cover column 132 are as shown in Table 8 below.

  The contents displayed in the substructure column 133 are as shown in Table 9 below.

FIG. 42 is a diagram illustrating a state in which the repair status on the suspended scaffold is displayed. This screen displays the status of repairs that can be performed when a suspended scaffolding is temporarily installed for the bridge selected by the bridge search form. The floor slab reinforcement column 134, the floor slab other reinforcement column 135, the draining column 136, and the back surface sound absorption It has a plate column 137.
The contents displayed in the floor slab reinforcement column 134 are as shown in Table 10 below.

  The contents displayed in the floor slab and other reinforcement column 135 are as shown in Table 11 below.

  The contents displayed in the draining column 136 are as shown in Table 12 below.

  The contents displayed in the back surface sound absorbing plate column 137 are as shown in Table 13 below.

  FIG. 43 is a diagram illustrating a state in which the repair status on the partial scaffold is displayed. This screen displays the status of repairs that can be performed when a bridge pier and a surrounding scaffolding are temporarily installed for the bridge selected in the bridge search form. Substructure reinforcement column 141, substructure seismic reinforcement column 142, support column 143 and a fallen bridge prevention apparatus column 144.

  The contents displayed in the substructure reinforcement column 141 are as shown in Table 14 below.

  The contents displayed in the substructure seismic reinforcement column 142 are as shown in Table 15 below.

  The contents displayed in the support column 143 are as shown in Table 16 below.

  The contents displayed in the falling bridge prevention apparatus column 144 are as shown in Table 17 below.

FIG. 44 is a diagram showing a state in which the high-speed upper repair situation is displayed. This screen displays the status of repairs that can be performed from the road provided on the bridge selected by the bridge search form, and has a pavement column 151, a sound insulation wall column 152, and an expansion joint column 153.
The contents displayed in the pavement column 151 are as shown in Table 18 below.

  The contents displayed in the sound insulation wall column 152 are as shown in Table 19 below.

  The contents displayed in the expansion joint column 153 are as shown in Table 20 below.

FIG. 45 is a diagram illustrating a state in which an inspection / repair history is displayed. This screen displays the type and quantity of damage found as a result of inspections conducted in the past or the type and quantity of damages that have been repaired for the bridge selected in the bridge search form. 161.
The contents displayed in the inspection / repair history column 161 are as shown in Table 21 below.

FIG. 46 is a diagram showing a bridge prescription finding form called in the flowchart of FIG. In the bridge prescription finding form, the findings of the inspector and the prescription of repair work are displayed or input as comments for the bridge selected by the bridge search form.
FIG. 47 is a flowchart showing a processing procedure executed by the bridge prescription finding form.

In step S41, the computer 1 selects a record having the same ID as the bridge ID selected in the bridge search form from the bridge prescription finding table.
In step S42, the computer 1 displays the data recorded in the finding field 171 of the record selected in step S41 in the finding field 171 and displays the data recorded in the prescription field in the prescription field 172.

In step S <b> 43, the computer 1 accepts a user editing operation on the data in the finding column 171 and the prescription column 172 that are text boxes.
At this time, when the user presses the finding clear button 173, the computer 1 deletes the data input to the finding column 171 in step S44 and step S45. When the user presses the prescription clear button 174, the computer 1 deletes the data input to the prescription column 172 in step S46 and step S47.
When the user presses the update button 175, the computer 1 updates the contents of the finding field and the prescription field of the record selected in step S41 in step S49 to the contents displayed in the finding field 171 and the prescription field 172, respectively. To do.

FIG. 48 is a diagram showing a remark form called up in the flowchart of FIG. In the remark form, a memo or the like related to the bridge selected by the bridge search form is displayed or input for each bridge as a comment.
FIG. 49 is a flowchart showing a processing procedure executed by the remark form.
In step S51, the computer 1 selects a record having the same ID as the bridge ID selected in the bridge search form from the bridge prescription finding table.
In step S52, the computer 1 displays the data recorded in the remarks field of the record selected in step S51 in the remarks column 181.

In step S53, the computer 1 accepts a user editing operation on data in the remarks column 181 that is a text box.
At this time, when the user presses the clear button 182, the computer 1 deletes the data input to the remarks column 181 in step S54 and step S55.
When the user presses the update button 183, the computer 1 updates the contents of the remarks field of the record selected in step S51 in step S57 to the contents displayed in the remarks column 181.

FIG. 50 is a diagram showing a drawing form called up in the flowchart of FIG. In the drawing form, a drawing related to the bridge selected by the bridge search form is displayed and registered.
FIG. 51 is a flowchart showing a processing procedure executed by the drawing form.
In step S61, the computer 1 selects from the drawing photograph table a record having the same ID as the bridge ID selected in the bridge search form and having the value of the type field “drawing”.
In step S62, the computer 1 reads out from the hard disk 6 an image file having the same file name value in the folder indicated by the value of the file path field of the record selected in step S61. These are sequentially displayed in each image display column 191. The comments recorded in the respective comment fields are displayed in the respective comment fields 192.
In step S63, the computer 1 accepts a user editing operation on the data in each comment field 192, which is a text box.

  In step S <b> 64, the computer 1 accepts registration of an image file that the user displays in each image display field 191. For example, the image file is registered by dragging and dropping the image file in an image display field 191 to be displayed by the user using a mouse device or the like. At this time, the bridge chart application program 11 detects the event information generated by the OS 10, determines the display field, file path and file name corresponding to the dragged and dropped position, and sets the file path and file name. Register in the picture table.

When the user presses any one of the delete buttons 193 (step S65), in step S66, the computer 1 selects an image displayed in the image display field 191 corresponding to the pressed delete button 193 from the drawing photo table. Delete the record that records the file name and file path.
When the user presses any clear button 194 (step S67), the computer 1 clears the text box in the comment field 192 corresponding to the pressed clear button 194 in step S68.

  When the user presses the comment update button 195 (step S69), the computer 1 displays the contents of the comment field of the record selected in step S61 in step S70 and the record in which the image is newly registered in step S64 in each comment field. The contents displayed in 192 are updated.

FIG. 52 is a diagram showing a photo form called up in the flowchart of FIG. In the photo form, a photo (damage photo or current photo) related to the bridge selected by the bridge search form is displayed and registered.
FIG. 53 is a flowchart showing a processing procedure executed by a photograph form.
In step S81, the computer 1 selects from the drawing photograph table a record having the same ID as the bridge ID selected in the bridge search form and having the value of the type field “photo”.

In step S82, the computer 1 reads out from the hard disk 6 an image file having the same file name value in the folder indicated by the file path field value of the record selected in step S81. And sequentially displayed in each image display column 201. The comments recorded in the respective comment fields are displayed in the respective comment fields 202.
In step S83, the computer 1 accepts a user editing operation on the data in each comment field 202, which is a text box.
In step S <b> 84, the computer 1 accepts registration of an image file that the user displays in each image display field 201. Registration of the image file is performed in the same manner as described above for the drawing form.

When the user presses one of the delete buttons 203 (step S85), the computer 1 in step S86 selects an image displayed in the image display field 201 corresponding to the pressed delete button 203 from the drawing photo table. Delete the record that records the file name and file path.
When the user presses one of the clear buttons 204 (step S87), the computer 1 clears the text box in the comment column 202 corresponding to the pressed clear button 204 in step S88.
When the user presses the comment update button 205 (step S89), the computer 1 displays the contents of the comment field of the record selected in step S81 in step S90 and the record in which the image is newly registered in step S84 in each comment field. The contents displayed in 202 are updated.

FIG. 54 is a diagram showing a data force form called up in the flowchart of FIG. In this screen, data extracted from the bridge ledger, member ledger data and inspection / repair ledger for the bridge portion selected in the bridge selection form is output to a file in a predetermined format.
The output contents may be, for example, structural specifications and inspection / repair history summary, findings, prescriptions, drawings, and photographs, among the contents displayed on each screen of the data display / input form. The output file is, for example, Microsoft Excel (registered) Trademark) table file.

FIG. 55 is a flowchart showing a processing procedure executed by the data force form.
In step S <b> 101, the computer 1 receives an output format selection instruction performed by the user operating the option buttons 211 and 212. As a result, if the chart output is selected, the process proceeds to step S103, and if the ledger output is selected, the process proceeds to step S106 (S102).
In step S <b> 103, the computer 1 accepts an output destination designation input to the output destination folder field 213. When the “Excel output button” is pressed (S104), the output content file is output to the designated output destination (S105).

If ledger output is selected in step S101, the process proceeds to step S106, and the display screen changes to the screen shown in FIG. In this screen, a file including a record extracted for the bridge portion selected in the bridge selection form from the ledger selected in the ledger selection field 215 is output.
In step S <b> 106, the computer 1 accepts an output destination designation input to the output destination folder field 216. In step S107, an instruction to select a ledger to be output is accepted.
When the “Excel output button” is pressed (S108), a file including a record extracted for the bridge portion selected in the bridge selection form in the ledger selected in step S107 is designated in step S106. To the output destination (S109).

  INDUSTRIAL APPLICABILITY The present invention can be used for equipment ledger management and inspection / repair ledger management of an elevated structure constructed by connecting a plurality of bridges.

It is a schematic block diagram which shows the structure of the elevated structure used as the object of the bridge chart output program by the Example of this invention. It is a block diagram which shows the structural example of the hardware which performs the bridge chart output program by the Example of this invention. It is a block diagram which shows each ledger data in the elevated structure database memorize | stored in the hard disk of FIG. 2, and the list of image data. It is a figure which shows the table structure of a basic ledger. It is a figure which shows the table structure of a balustrade cover book. It is a figure which shows the table structure of a pavement ledger. It is a figure which shows the table structure of a sound-insulating wall ledger. It is a figure which shows the table structure of a back surface sound-absorption board ledger. It is a side view of an elevated structure. It is a figure which shows the table structure of a superstructure ledger. It is a figure which shows the table structure of a draining ledger. It is a figure which shows the table structure of a floor version ledger. It is a figure which shows the table structure of an expansion joint ledger. It is a figure which shows the table structure of a support ledger. It is a figure which shows the table structure of a fallen bridge prevention ledger. It is a figure explaining the data content stored in a support position field and a start leg end leg division field. It is a figure which shows the table structure of a substructure ledger. It is a figure which shows the table structure of a bridge pier earthquake-proof reinforcement ledger. It is a figure which shows the table structure of an inspection repair ledger. It is a figure which shows the table structure of a bridge ledger. It is a figure which shows the structure of a bridge finding prescription table, a remarks table, and a drawing photograph table. It is a figure which shows the relationship provided between a bridge ledger and a superstructure ledger. It is a figure which shows the relationship provided between a bridge ledger and a basic ledger. (A) is a figure which shows the relationship provided between a balustrade cover book and a basic ledger, (B) is a figure which shows the relationship provided between a pavement ledger and a basic ledger. (A) is a figure which shows the relationship provided between a sound-insulating wall ledger and a basic ledger, (B) is a figure which shows the relationship provided between a back surface sound-absorption board ledger and a basic ledger. (A) is a figure which shows the relationship provided between a draining ledger and a bridge ledger, (B) is a figure which shows the relationship provided between a floor slab ledger and a bridge ledger. (A) is a figure which shows the relationship provided between a support ledger and a pier number query, (B) is a figure which shows the relationship provided between a fall bridge prevention ledger and a pier number query. It is a figure which shows the relationship between an pier number query, a basic ledger, and an expansion joint ledger. (A) is a figure which shows the relationship between a substructure ledger and a pier number query, (B) is a figure which shows the relationship between a pier seismic strengthening ledger and a pier number query. It is FIG. (1) explaining the production | generation method of the joint inspection repair query produced | generated by connecting an inspection repair ledger and a bridge ledger. It is FIG. (2) explaining the production | generation method of the joint inspection repair query produced | generated by connecting the inspection repair ledger and the bridge ledger. It is a figure which shows a structure table. (A) is a figure which shows the relationship between a bridge finding prescription table and a bridge ledger, (B) is a figure which shows the relationship between a remarks table and a bridge ledger, (C) is a drawing photograph It is a figure which shows the relationship between a table and a bridge ledger. It is a flowchart of the main routine of a bridge chart application program. It is a figure which shows the bridge search form which performs the search by a management key. It is a flowchart which shows the process sequence performed by a bridge search form. It is a figure which shows the bridge search form which searches with a ledger item. It is a figure which shows a data display / output form. It is a flowchart which shows the process sequence performed by a data display / output form. It is a figure which shows the state where bridge basic information was displayed. It is a figure which shows the state by which the bridge structure specification was displayed. It is a figure which shows the state by which the repair condition on the suspension scaffold was displayed. It is a figure which shows the state by which the repair condition on the partial scaffold was displayed. It is a figure which shows the state in which the high-speed repair condition was displayed. It is a figure showing the state where inspection repair history was displayed. It is a figure which shows the bridge prescription finding form called with the flowchart of FIG. It is a flowchart which shows the process sequence performed by a bridge prescription finding form. It is a figure which shows the remarks form called with the flowchart of FIG. It is a flowchart which shows the process sequence performed by the remarks form. It is a figure which shows the drawing form called by the flowchart of FIG. It is a flowchart which shows the process sequence performed with drawing form. It is a figure which shows the photograph form called by the flowchart of FIG. It is a flowchart which shows the process sequence performed by the photograph form. It is a figure which shows the data power form called by the flowchart of FIG. It is a flowchart which shows the process sequence performed by a data force form. It is a figure which shows the data power form in the case of performing a ledger output.

Explanation of symbols

1 Computer 2 CPU
3 Memory 4 Display 5 Keyboard 6 Hard Disk 7 Printer 10 Operating System (OS)
11 Bridge chart application program 1
12 Relational Database Application Program 13 Program Interface Component 14 Elevated Structure Database 15 Image Data

Claims (4)

With regard to an elevated structure constructed by connecting a plurality of bridges, information on members constituting the elevated structure is recorded in a plurality of ledgers for each type of member, and member ledger data and maintenance for each member. It is possible to access maintenance ledger data that records history-related information, and bridge ledger data that is recorded as a set of bridge identifiers that indicate the piers that support each of the plurality of bridges and bridge identifiers that indicate the bridges supported by the piers. A program for causing a computer to perform a process of outputting information on the member constituting a bridge selected from any of the plurality of bridges and information on a maintenance history of the member,
The member ledger data has a different record for each member, and the record that the member ledger data has stores at least one information element related to the member and the pier identifier of the pier on which the member is provided,
The maintenance ledger data has a different record for each member, and the record of the maintenance ledger data stores at least one information element related to the maintenance history of the member and the pier identifier of the pier on which the member is provided. And
The bridge ledger data has a different record for each bridge, and the record that the bridge ledger data has is stored as a set of a bridge identifier indicating the bridge and a bridge pier identifier indicating the pier supporting the bridge,
The program is
An input process for accepting designation input for any of the plurality of bridges;
A first record selection process for selecting a record related to the designated bridge among records of the bridge ledger data;
Of the records that the member ledger data has, the record that stores the same pier identifier as the pier identifier that is stored in the record selected by the first record selection process, and the first of the records that the maintenance ledger data has. A second record selection process for selecting a record that stores the same pier identifier as the pier identifier stored in the record selected by the record selection process;
The information element stored in the record selected from the member ledger data by the second record selection process , and the information element stored in the record selected from the maintenance ledger data by the second record selection process Data output processing to output
Is executed by the computer, and a bridge chart output program. The member includes a member provided across the diameter and a member provided at the pier location,
The bridge ledger data has a different record for each span, and the record stores the pier identifiers of the piers at both ends of the span,
The program causes the computer to further execute a pier identifier extraction process for extracting the pier identifiers of all piers supporting the bridge from the record selected from the bridge ledger data by the first record selection process,
The second record selection process is a record that stores information elements related to members provided at the pier location among records of the member ledger data, and is the same as the pier identifier extracted by the pier identifier extraction process. Including selecting a record to store the pier identifier,
The bridge chart output program according to claim 1, wherein: With regard to an elevated structure constructed by connecting a plurality of bridges, information on members constituting the elevated structure is recorded in a plurality of ledgers for each type of member, and member ledger data and maintenance for each member. It is possible to access maintenance ledger data that records history-related information, and bridge ledger data that is recorded as a set of bridge identifiers that indicate the piers that support each of the plurality of bridges and bridge identifiers that indicate the bridges supported by the piers. A method of using a computer to output information on the member constituting the bridge selected from the plurality of bridges and information on a maintenance history of the structure,
The member ledger data has a different record for each member, and the record that the member ledger data has stores at least one information element related to the member and the pier identifier of the pier on which the member is provided,
The maintenance ledger data has a different record for each member, and the record of the maintenance ledger data stores at least one information element related to the maintenance history of the member and the pier identifier of the pier on which the member is provided. And
The bridge ledger data has a different record for each bridge, and the record that the bridge ledger data has is stored as a set of a bridge identifier indicating the bridge and a bridge pier identifier indicating the pier supporting the bridge,
The computer
A bridge input step for accepting a bridge designation input for designating any one of the plurality of bridges;
A first record selection step of selecting a record related to the designated bridge among records of the bridge ledger data;
The member register first among the records record that stores the first pier identifier and same pier identifiers stored in the selected record by record selection step among the records, and that the maintenance ledger data has the data has A second record selection step for selecting a record that stores the same pier identifier as the pier identifier stored in the record selected by the record selection step;
The information element stored in the record selected from the member ledger data by the second record selection step , and the information element stored in the record selected from the maintenance ledger data by the second record selection step A data output step for outputting
A method for outputting the charts of bridges. The member includes a member provided across the diameter and a member provided at the pier location,
The bridge ledger data has a different record for each span, and the record stores the pier identifiers of the piers at both ends of the span,
The computer performs a pier identifier extraction step of extracting pier identifiers of all piers supporting the bridge from the record selected from the bridge ledger data by the first record selection process,
The second record selection step is a record that stores information elements related to members provided at the pier location among records of the member ledger data, and is the same as the pier identifier extracted by the pier identifier extraction step. Selecting a record to store the pier identifier of
The bridge chart output method according to claim 3.