KR101448423B1 - U-city infrastructure facility management system based on Life Cycle - Google Patents

Abstract

The present invention relates to a U-city public information infrastructure management system which can prevent waste of budgets and easily maintain a U-city public information infrastructure by managing the U-city public information infrastructure more systematically and effectively. To achieve this, the present invention provides an infrastructure management system which comprises: an infrastructure basic information database in which a plurality of facility information elements including a lifecycle of a facility installed in an U-city are stored; a management server including a maintenance/management analysis module for determining a maintenance timing of the facility, based on the lifecycle of the facility, and storing the determined maintenance timing in the basic information database; and a field terminal for receiving contents of the facility from the basic information database and transmitting the monitoring result of the facility to the basic information database. Therefore, according to the present invention, waste of manpower or costs can be prevented and failings or malfunctions of the U-city public information infrastructure can be prevented by automatically reporting a maintenance plan on the U-city facility in advance, using systematized data.

Description

[0002] U-City infrastructure facility management system based on life cycle [

The present invention relates to a lifecycle-based u-city public information infrastructure management system, and more specifically, a life-cycle management system that can more efficiently and efficiently manage u-city public information infrastructure management, Based u-city based facility management system.

Ubiquitous-city refers to a city that provides ubiquitous urban services anytime and anywhere through ubiquitous urban infrastructure built using ubiquitous urban technology to improve city competitiveness and quality of life.

In other words, u-city is a city that is created, managed and utilized as a fusion of information and communications, construction and urban engineering. It provides internally complex but well-converged services provided by converged technologies and infrastructures.

In u-City, various services are integrated and operated, such as crime prevention, traffic, media and environment.

In order to operate these services, a lot of facilities are used over a wide area. Currently, facilities are checked and on-site inspection is performed through monitoring, but the system is not operating systematically, resulting in wasted manpower and costs.

In particular, due to the repetition of one-time maintenance management tasks, there is a lack of active coping and management of disabilities by facilities. In addition, in the maintenance of the facility, it is managed based on the conventional inspection result without grasping the characteristics of the facility.

SUMMARY OF THE INVENTION The present invention provides a life-cycle-based u-City public information infrastructure management system capable of reducing redundant cost wastage by using more structured data and maintaining the facility in a timely manner It has its purpose.

Furthermore, it is aimed to provide a more efficient maintenance method for the management of u-city public information infrastructures, so that it can provide reasonable maintenance if lack of budget or maintenance judgment is difficult.

In order to achieve the above object, the present invention provides a public information infrastructure management system installed in a city, wherein the infrastructure management system stores a plurality of facility information including a life cycle of facilities installed in the city, Facilities basic information database; A maintenance management module for determining a maintenance period of the facility based on the life cycle of the facility and storing the maintenance period in the facility basic information database; And a field terminal for receiving contents of the facility basic information database and transmitting the result of the facility inspection to the facility basic information database.

The facility basic information database stores sanitary, safety, efficiency, comfortably divided property elements, a budget and a necessary budget for each facility, and the maintenance analysis module applies a weight corresponding to the property elements, And the management server transmits a maintenance command to the field terminal based on the property element ranking when the required budget is smaller than the budget.

The facility basic information database stores the number of years that are available for each facility, the number of years of use from the time of installation of the facility to the point of inspection, the cost of acquiring the facility, and the cost of repairing parts, It is preferable to calculate the repair limit by [0.7- {years of use / (2 * years of service)]] * cost of obtaining the facility, and then compare the economical repair limit and the repair cost of the parts to judge the replacement of the parts or the replacement of the facilities.

On the other hand, the management server includes a maintenance plan module that generates a plan for maintenance of the u-city public information infrastructure, and converts the work time data converted from the work to be done in each facility and the distance between the public information infrastructure into the time Storing the distance time data in the facility basic information database, the maintenance planning module generating facilities to be checked on the same day from the facility basic information database based on the geographic information system; Designating a reference working time and a starting facility for each operator; Designating a next facility to which distance time data is minimized from the departure facility to include it as a maintenance facility; Comparing the estimated operation time, which is the sum of the operation time data of the maintenance facility and the distance time data, with the reference operation time, and stopping the designation of the maintenance facility if it is determined to be within a predetermined range; ,

When an emergency visiting facility other than the regular check is generated, the maintenance plan module includes: detecting an operator having a maintenance facility within a certain range in the emergency visiting facility; Calculating an expected work time by including the emergency visiting facility in the maintenance facility for the detected worker; Detecting an operator having the best estimated working time; The step of including the emergency visiting facility in the maintenance facility of the operator having the smallest expected working time may be performed.

Also, the management server receives and stores position data and time data from the field terminal, compares the work time data and the distance time data with the position data and time data transmitted from the field terminal for each worker, Some of the maintenance facilities of the workers having a certain range or more can be changed to the maintenance facilities of the workers having the above range.

According to the present invention, it is possible to prevent the waste of manpower and cost and prevent the failure or malfunction of the u-city public information infrastructure by automatically informing the maintenance plan of the u-city public information infrastructure using the structured data.

In addition, it can help efficient maintenance by informing whether it is desirable to replace the parts of the facility when a failure occurs in the u-city public information infrastructure, or whether it is desirable to exchange the facility itself.

1 is a block diagram showing the configuration of a u-city public information infrastructure management system according to the present invention;
2 is an exemplary view showing a table for each facility part in the facility basic information database;
3 is an exemplary view showing a component part table for each facility in the facility basic information database;
4 is an exemplary view showing a facility management person table in the facility basic information database;
5 is an exemplary view showing a replacement cycle table among the facility basic information databases;
6 is an exemplary view showing a failure type list table in the facility basic information database;
7 is an exemplary view showing a failover table among the facility basic information databases;
FIG. 8 is an exemplary view showing a maintenance accumulation cost table for each facility in the facility basic information database; FIG.
9 is an exemplary view showing a repair limit calculation table in the facility basic information database;
10 is an exemplary view showing a work path of an operator in the maintenance schedule list;

The configuration and operation of the embodiment of the present invention will be described in detail with reference to the accompanying drawings.

Referring to FIG. 1, the U-City public information infrastructure management system according to the present invention includes a management server 100 and a field terminal 300. The U-City public information infrastructure management system includes various types of And systematically manage the city facilities 500.

The management server 100 includes a facility basic information database 110, a maintenance analysis module 130, a maintenance planning module 140, and a communication port 150.

The facility basic information database 110 includes a table for each facility part (FIG. 2), a table of constituent parts for each facility (FIG. 3), a table of facility management personnel (FIG. 4), a replacement cycle table 6), a failover table (FIG. 7), a maintenance accumulated cost table for each facility (FIG. 8), a repair limit calculation table (FIG.

The table for each facility part (FIG. 2) is a data table basically necessary for a database considering a life cycle and a cost, and stores a component part and a detail part cost.

The component component table (FIG. 3) for each facility is a table in which basic information (management code, location, and component parts) of facility maintenance is stored. The component parts table for each facility stores basic information that is applied to most tables such as a part table, a management person table, a replacement cycle table, a failover table, and a maintenance accumulation cost table.

The facility management person in charge table 113 is a table that is set so that adjacent facilities can be managed for efficient movement of the person in charge.

The replacement period table 114 is a database to which a life span and a cost are applied, and is a data table required when an economic repair limit to be described later is applied.

The failure type list table 115 is a database in which failure types necessary for facility maintenance are recorded as codes. By managing the contents of each type of failure using code values, administrators can efficiently manage the facilities. The failure type code value is subdivided into a large classification code value and a small classification code value and is linked with the failover table to display the failure information to the facility manager terminal.

The failover table 116 is a database that stores failover results. That is, at the same time as the fail-over, measures for failures are stored as code values, so that the administrator can quickly record business actions and accumulate accumulated data related to the subsequent life cycle. These failover tables apply to calculations taking into account lifecycle and cost of facility replacement.

The maintenance accumulation cost table 117 for each facility is a database that stores costs incurred in replacement due to a failure of each facility component.

The repair limit calculation table is a database for judging a more economical replacement method between a single facility replacement and a component replacement considering the life cycle. This can be used to estimate the economic repair limits and to determine a more economical way of replacing single components or replacing components.

In the facility basic information database 110, the facility average life cycle and the facility minimum life cycle are stored as shown in Table 1.

Facilities Average life cycle (months)
Facilities Minimum life cycle (months)
Security CCTV
20
One
Vehicle identification CCTV
22
2
Illegal parking regulation CCTV
-
-
Traffic CCTV
24
22
VMS (traffic information signboard)
26
7
BIT (bus information terminal)
21
7
Signal controller
27
16
VDS (image detector)
9
3
pressure gauge
6
16
Flow meter
18
2
Media board
5
4
Placard
15
8
Environmental pollution display board
26
6

The facility life cycle is the average of the average lifecycle of the components of a facility and the minimum life cycle of the facility represents the shortest life cycle of the average life cycle of the components in the facility.

For a facility to maintain its functionality, use the minimum life cycle of the facility, which represents the average life cycle of the components with the shortest average life span to ensure that all components of the facility are functioning normally, assuming normal functioning If it is desired, but a component with very few component failures has a very short average life span, this is a special case, so it may be unreasonable to determine the lifetime of the facility.

For example, the number of parts failures in a security CCTV video server occurs twice in a few years. If the period between the first replacement and the second replacement is one month, the first replacement component is a special failure The replacement was made with a very short life cycle. Therefore, it can not be seen as a normal life cycle.

Therefore, the maintenance and analysis module 130 of the management server can determine the maintenance period of the facility by calculating the life expectancy of the facility by calculating {average life cycle of the facility × α + minimum life cycle of the facility × (1-α)} / 2. Here,? Is a weighting value 0??? 1.

That is, when the maintenance analysis module 130 determines that the life-cycle of the u-City public information infrastructure has reached the life time based on the replacement timing of the u-city public information infrastructure, the maintenance management module 130 determines the maintenance period and stores it in the basic information database And transmits the maintenance date and place to the field terminal 300 through the communication port 150.

The on-site terminal 300 can be carried by an operator who directly carries out maintenance on the U-City public information infrastructure, and the location of each facility is displayed on the map by using the ZFP system. The field terminal 300 may be provided in the form of a smart phone, a PDA, a tablet, or the like.

On the other hand, when the worker completes the maintenance work on the field and inputs the work contents through the site terminal 300, the work contents and costs are transmitted to the management server and stored as updated data in each database.

On the other hand, as shown in Table 2, the facility basic information database stores sanitary, safety, efficiency, comfort factor, quality factor, and budget for each facility as shown in Table 2. Also, priorities are stored in the same property element.

Property factor

facility
weight
Within nature factor
Priority
Property factor
ranking
hygiene


pressure gauge
0.09
2
2
Flow meter
0.09
One
One


safety
Security CCTV
0.08
2
4
Vehicle Recognition CCTV
0.08
3
5
Illegal parking car CCTV
0.08
4
6
Street lamp
0.08
One
3




efficiency

Traffic CCTV
0.07
4
10
Traffic Information Display Board
0.07
3
9
Signal controller
0.07
One
7
Image detector
0.07
One
7
Media board
0.07
5
11
Placard
0.07
6
12
geniality

Bus information terminal
0.04
One
13
Environmental pollution display board
0.04
2
14

The maintenance analysis module 130 determines a property element ranking by applying a weight value corresponding to the property factor and a priority in the property factor. In addition, the maintenance analysis module 130 determines the maintenance period for the u-city public information infrastructure in accordance with the life cycle, and creates the maintenance schedule. At this time, the required budget for each component is calculated for the specific period.

Then, when the required budget is smaller than the budgeted budget, the required budget and the budgeted budget for each component are compared with each other. And transmits the maintenance command to the field terminal through the communication port.

On the other hand, the facility basic information database stores the number of years, the number of years of use, the facility acquisition cost, and the parts cumulative repair cost for each part.

The number of years is a period of time that can be used as an original function and is distinguishable from a variable life cycle, such as when a change occurs due to a failure of an actual facility or a change due to inspection. In addition, the cumulative repair cost is the sum of the repair costs that are stored each time the parts of the utility information infrastructure are repaired after replacing the facilities.

In the maintenance analysis module, the economic repair limit is calculated on the basis of the service life, the number of years of use, and the cost of acquiring the facility.

In other words, the economic limit of repair is calculated as [0.7- {years of use / (2 * number of years)}] * Facility acquisition cost, If the cost is higher than the cost, the maintenance analysis module sends the component repair command to the field terminal. If the economic repair limit is smaller than the component repair cost, the maintenance analysis module sends the facility replacement instruction to the site terminal.

For example, the cost of repairing a video server, which is a component of security CCTV, is estimated to be 150,000 won when the cost of acquiring security CCTV facilities is 1 million Yuan, the number of years is 5 years, and the number of years is 2 years.

In the maintenance analysis module, the economic repair limit is calculated to be 500,000 won using the above equation, and the cumulative repair cost of the video server is read by referring to the facility basic information database. If the video server has two identical maintenance costs for two years, the cumulative repair cost of the parts including the maintenance cost is 450,000 won. Since the economic repair limit is larger than the cumulative repair cost of the parts, the video server maintenance command is transmitted to the field terminal do.

On the other hand, if the video server has three identical maintenance costs for two years, the cumulative repair cost of the parts including the maintenance cost is 600,000 won and the economic repair limit is smaller than the cumulative repair cost of the parts. And sends a replacement command to the field terminal.

Meanwhile, the field terminal 300 may be provided with an APP (APP) related to the present system, and may receive or transmit various data from the management server 100. Map data is stored in the management server 100, and the name and location of the facility are displayed on the map based on the map data.

In addition, the maintenance plan module 140 receives data from the maintenance analysis module and stores the facilities and components to be maintained on a day by day basis as inspection plan data in the facility basic information database.

In the present embodiment, the maintenance contents are converted into maintenance time according to maintenance contents and converted into a database. That is, the standard time required to check one CCTV for security can be calculated, and the time taken depending on the components to be checked can be previously tabulated and stored.

The management server 100 stores location information of all the facilities based on the map data, and the distance between the facilities and the distance time data converted by the time are stored in a database based on the location information.

The distance time data between the facilities can not be calculated merely by the spatial distance between the two facilities, and it is preferable to measure the average time in consideration of the actual traffic environment.

The maintenance plan module 140 generates a facility to be maintained on the basis of the maintenance plan data and displays the facility on the map.

On the other hand, each worker has a predetermined standard work time for the day, and the standard work time is stored in the management server. The reference working time may be different for each worker, and may vary from one date to another. Therefore, according to the present system, it is possible to provide a flexible maintenance plan according to the circumstances of each worker, and at the same time, to provide accurate data in performance calculation and the like.

The start facility to be visited first is designated for each worker among the same day maintenance facilities generated by the maintenance plan module 140. Such a starting facility may be automatically designated based on the stored data, or may be manually designated for each specific worker.

When the departure facility A is designated for each worker, the distance time data is read out and compared for each facility around the starting facility. In the maintenance plan module, the facility with the smallest distance time data is designated as the next facility (B) and included in the maintenance facility. Similarly, the distance time data is read out and compared with each of the surrounding facilities based on the B facility designated as the next facility. Of course, facilities already included in maintenance facilities are excluded from comparison.

In this way, maintenance facilities are created continuously. In the maintenance plan module, the sum of the working time data and the distance time data of the designated facilities is calculated as the expected working time each time the next facility is designated.

For example, if the work time data of Facilities A, B, and C are 2.5 hours, 1.2 hours, and 1.5 hours, respectively, the distance time data of Facilities A and B are 0.6 hours, and the distance time data of Facilities B and C is 0.5 hours , The estimated working time is 6.3 hours when designated from facility A to facility C.

In the maintenance planning module, the maintenance facility is designated and the estimated operation time is compared with the reference operation time. In other words, if the estimated work time is subtracted from the reference work time and is within a certain range, designation of the next facility is stopped.

For example, if the base work time is 8 hours and the expected work time is 6.3 hours, the difference is 1.7 hours. If the minimum range of the difference is 0.7 hours, the maintenance plan module will exceed the minimum range. When designating the facility and subtracting the estimated work time from the standard work time, the next facility designation can be stopped.

The method of stopping the minimum range and designating the next facility may be modified in various ways depending on circumstances.

In this way, the maintenance planning module creates maintenance facilities to be checked on the same day for each worker. Therefore, when managing many workers, it is possible to perform flexible management according to each worker's circumstances and to share the most optimized work So that an effective management system can be provided.

On the other hand, the management server 100 can receive position data from the on-site terminal 300 carried by the workers using GPS, 3G, etc., and receives time data, maintenance status information, and the like, and stores them in the storage unit.

The maintenance status information can be transmitted to the management server 100 when the worker inputs a work visiting the facility using the field terminal. In this way, it is possible to send and receive information about maintenance activities in real time.

Next, when an urgent visit request urgently required in a specific facility is generated rather than a scheduled regular maintenance, the maintenance plan module includes the emergency visiting facility in which the urgent visit request occurred when the maintenance facility is generated, in the maintenance facility.

For example, if an emergency call request is generated in the E facility in FIG. 10, the maintenance planning module detects an operator having a maintenance facility within a certain range in the E facility. At this time, the operator 'A' on the right side and the operator 'A' on the left side can be detected.

In the maintenance plan module, the estimated work time is calculated by including the E facility as the emergency visiting facility in the maintenance facility of the worker A, and the E work facility as the emergency visiting facility is included in the maintenance facility of the worker, And detects an operator having the smallest expected working time.

A new maintenance facility is created by including the emergency visiting facility in the maintenance facility of the operator having the smallest expected operation time detected in this way.

On the other hand, when you are actually working, you may exceed the scheduled work time or finish the work much earlier than the work time. In addition, due to unexpected traffic conditions such as road construction and demonstration, the time between movements of facilities may be delayed or may arrive earlier than expected.

In this case, the maintenance planning module compares the difference between the position data and the time data transmitted from the field terminal 300 for each worker, and the predetermined work time data and the distance time data.

For example, if the 'A' worker starts operating at 9:00 am and the location data transmitted from the site terminal to the management server reaches the C facility, the time data is 16:30, and A, B, C When the time data of the facilities are 2.5 hours, 1.2 hours, 1.5 hours, and the distance time data of the facilities A and B are 0.6 hours, and the distance time data of the facilities B and C are 0.5 hours, respectively, The sum of the work time data and the distance time data of facilities A and B and the facilities B and C is 4.8 hours.

In addition, according to the time data transmitted from the 'A' operator's field terminal, the actual time taken is 7.5 hours because it is 7 hours and 30 minutes, and the actual working time is 6.5 hours excluding 1 hour of lunch time.

If the actual working time is 6.5 hours and the scheduled working time is 4.8 hours, the working time difference is 1.7 hours. If the maximum working time difference is +1 hour, the worker is out of the maximum working time difference.

On the other hand, if the working time difference of the worker is 0.5 hour, the worker is less than the maximum range of the working time difference. In the maintenance planning module, the maintenance facility D, , And these changes are transmitted to the field terminals of each operator.

In this way, an optimized maintenance management method can be provided according to the actual working environment, and a flexible management system can be maintained.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, and variations and modifications may be made without departing from the scope of the invention. It will be understood that the present invention can be changed.

100: management server 110: facility basic information database
130: maintenance analysis module 140: maintenance planning module
150: communication port 300: field terminal
500: Yu City Facilities

Claims (5)

In a public information infrastructure management system installed in u-city,
The public information infrastructure management system comprises:
A facility basic information database storing a plurality of facilities information including a life cycle of facilities installed in u-city;
A maintenance management module for determining a maintenance period of the facility based on the life cycle of the facility and storing the maintenance period in the facility basic information database; And
And a field terminal for receiving the contents of the facility basic information database and transmitting the result of the inspection of the facility to the facility basic information database,
The facility basic information database stores sanitary, safety, efficiency, comfortably divided property elements, a budget and a necessary budget for each facility, and the maintenance analysis module applies a weight corresponding to the property elements, Wherein the management server transmits a maintenance command to the field terminal based on the property element ranking when the required budget is smaller than the budget. In a public information infrastructure management system installed in u-city,
The public information infrastructure management system comprises:
A facility basic information database storing a plurality of facilities information including a life cycle of facilities installed in u-city;
A maintenance management module for determining a maintenance period of the facility based on the life cycle of the facility and storing the maintenance period in the facility basic information database; And
And a field terminal for receiving the contents of the facility basic information database and transmitting the result of the inspection of the facility to the facility basic information database,
The facility basic information database stores the number of years, which is a period of time available for the original function of each facility, the number of years of use from the installation point of the facility to the point of inspection, facility acquisition cost,
The maintenance analysis module can be used to
[0.7- {years of use / (2 * years of content)}] * After calculating the costs of acquiring facilities,
And comparing the economic limit of repair and the cost of repairing the parts to judge the replacement of the parts or replacement of the facilities. delete delete delete

Images