JP2015056122A - Equipment management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an equipment management system capable of extracting data of types different by users even in the case of the users belonging to the same organization.SOLUTION: A first database 4 classifies equipment data 10 into a plurality of types to hold the equipment data 10, and a second database 5 holds management data 20 for searching the equipment data 10. The management data 20 includes type hierarchy management data 21 for hierarchizing and managing types of the equipment data, type/display condition relation data 24 for managing the equipment data by associating each type with a display condition for searching the equipment data, and type/user relation data 25 for managing the equipment data by associating each type with users having the authority to search the equipment data.

Description

  The present invention relates to an equipment management system that manages equipment data and displays it in response to a user request.

  In the equipment management system, it is desirable to give the authority to manage equipment data for each user in consideration of the organizational structure. As a technology related to this, Japanese Patent Laid-Open No. 2004-228867 discloses that “when managing a user in consideration of an organizational structure using a directory service, it is possible to delegate the administrative authority of a lower organization user / group to a user of an upper organization. In addition, a user management system is provided that does not change an ACL (Access Control List) for network resources even when a change in affiliation occurs, and does not require a change in administrator authority for an OU (organizational unit). "Is described.

JP 2008-117052 A

  Patent Document 1 describes a mechanism of authority management in consideration of an organizational structure. However, since the authority management in Patent Document 1 gives display authority for each organization, it is not possible to extract desired management data for each user. That is, in order to set authority for data extraction for each user, setting work becomes complicated.

  For example, the facility data managed by the user includes a plurality of types such as a single facility and a linear facility (a facility connecting a plurality of positions, for example, an electric wire). For example, a user A belonging to a certain organization may want to extract only data of a single facility. In addition, another user B belonging to the same organization may want to extract all managed data (both single facility and linear facility). In such a case, the method of uniformly giving management authority for each organization cannot distinguish and extract the single equipment and the linear equipment according to the user.

  Therefore, an object of the present invention is to provide an equipment management system that enables extraction of different types of data depending on users even if they belong to the same organization.

  The present invention relates to a facility management system including a data management device that manages facility data. The data management device includes a first database that classifies and holds facility data and a management for searching for facility data. A second database that holds data, and a data processing unit that registers facility data and management data in the first and second databases and searches facility data using the management data. The management data includes type hierarchy management data for managing the types of facility data in a hierarchy, type / display condition relation data for managing the display conditions for searching for facility data for each type, and for each type. And the type / user relation data for managing the user who has authority to search the facility data in association with each other.

  According to the present invention, even for users belonging to the same organization, it is possible to extract different types of data depending on the user, and user convenience is improved.

The figure which shows the whole structure of an equipment management system. The figure which shows the specific example of equipment data and management data. The figure which shows the tied | linking state of management data. The figure which shows the example which described management data in the table format. The flowchart which shows the flow of the search display process of equipment data. The figure which shows the example of the display screen which displays the extracted equipment data. The figure which shows the example of a change of the management data accompanying a user's management change.

  Embodiments of the present invention will be described below with reference to the drawings. Each embodiment is characterized by managing facility data hierarchically (type hierarchy management) and managing the display conditions (extraction conditions) and users in association with each type (linkage management).

  FIG. 1 is a diagram illustrating an overall configuration of a facility management system according to the first embodiment. The facility management system 1 includes a data management device 2, an input device 6, and a display device 7. The data management device 2 stores and manages the facility data, retrieves the facility data in response to a user request input from the input device 6, and outputs the retrieved data to the display device 7 for display.

  The data management device 2 is, for example, a server, a data processing unit 3 that performs data registration and search processing, a first database 4 that stores facility data 10, and a first database that stores management data 20 for searching and extracting facility data 10. 2 database 5.

  The data processing unit 3 executes the program and registers the facility data 10 and the management data 20 input from the input device 6 in the first and second databases 4 and 5. In response to a user request, the facility data 10 is searched using the management data 20, and the extracted facility data is output to the display device 7.

  The first database 4 holds equipment data 10 that is data of each equipment. At that time, each piece of equipment data 10 is classified into a plurality of items and stored. For example, in order to classify the equipment data, the equipment name and the item (large / medium / small) indicating the attribute are combined, the type A large item 11, the type A medium item 12, the type A small item 13, the type B item 14, Classify as follows. The “type” here is an equipment name or item name for classifying equipment. This classification item (type) serves as a search item when facility data is extracted as will be described later.

The second database 5 holds management data 20 for searching the facility data 10. The management data 20 includes type hierarchy management data 21 for managing the hierarchies of types (equipment, items), display condition management data 22 for managing display conditions, and user management data 23 for managing users. Further, in this embodiment, the type / display condition relationship data 24 for associating the relationship between the type hierarchy management data 21 and the display condition management data 22 and the type for associating the relationship between the type hierarchy management data 21 and the user management data 23. / It has the characteristic that it has the user relationship data 25.
The first database 4 and the second database 5 may be configured as a common database.

FIG. 2 is a diagram showing a specific example of facility data 10 and management data 20 held in the first and second databases 4 and 5.
The equipment data 10 of (a) classifies each equipment by types such as a large item (installation location), a medium item (equipment function), a small item (inspection date) indicating the attributes, and describes the information. . For example, “fire extinguishing equipment A” is installed in “building A”, the function is “fire extinguishing equipment”, and the latest inspection implementation date is “June 26, 2013”. By classifying in this way, it is possible to search for a classification item (type) as a keyword and extract desired facility data.

  Next, each data of the management data 20 will be described.

    The type hierarchy management data 21 in (b) is obtained by managing the type (equipment name, item) of the equipment data 10 in a hierarchical manner and registering the hierarchical relationship thereof. The vertical relationship is registered as data in a table format to be described later, but here it is shown as an image for easy understanding. For example, the building A101 is an upper level facility, and the fire extinguishing facility A102 and the alarm facility A103 are included as lower facilities belonging to the building A101. Similarly, the building B is a higher-level facility, and the fire extinguishing facility B is included as a lower facility belonging to the facility (not shown). On the other hand, the fire extinguishing equipment inspection 104 is an upper type, but there is no lower type belonging to it, and it is configured alone. In this manner, a plurality of various types (equipment) having a vertical relationship are managed by the hierarchical group. In that case, one hierarchy group may be comprised by the single classification (equipment), and the same classification may be registered redundantly in a plurality of hierarchy groups.

  The display condition management data 22 in (c) describes the relationship between the display condition name and the search expression, and defines the conditions for retrieving data from the facility data 10 for the requested display condition name. . For example, if the display condition name is “building A information”, the search is performed under the condition that the major item of the facility data 10 is “building A”. If the display condition name is “fire extinguishing equipment inspection information”, the search is performed on the condition that the middle item is “fire extinguishing equipment” and the small item (inspection date) exceeds 30 days.

  The user management data 23 of (d) is registered with a user name authorized to search and display specific equipment data. Which equipment each user can search and display is separately defined by the type / user relationship data 25. The user may be a group name as well as an individual name.

  FIG. 3 is a diagram showing the association state of the management data 20. There are classification / display condition relation data 24 and classification / user relation data 25 as the association data. This linking state is displayed overlapping the type hierarchy management data 21 in FIG.

  First, the type / display condition relationship data 24 associates various types in the type hierarchy management data 21 with the display conditions 22. For example, the building A 101 in the display condition name is linked to the building A 101 in the upper hierarchy, and this is indicated by a broken line 111 s. Moreover, the building A fire extinguishing equipment 112 of the display condition name is linked to the fire extinguishing equipment A102 in the lower hierarchy (broken line 112s), and the building A alarm equipment 113 is linked to the alarm equipment A103. (Dashed line 113s). Furthermore, the fire extinguishing equipment inspection information 114 is linked to the fire extinguishing equipment inspection 104 (broken line 114s).

  On the other hand, the type / user relationship data 25 associates various types in the type hierarchy management data 21 with user names. For example, the user A121 is linked to the building A101 in the upper hierarchy, and this is indicated by a broken line 121s. Further, the user B122 is linked to the fire extinguishing equipment A102 in the lower hierarchy (broken line 122s), and the user C123 is linked to the alarm equipment A103 (broken line 123s). Further, the user D124 is linked to the fire extinguishing equipment check 104 (broken line 124s).

  By setting such a linking relationship, the user's search display authority can be set as follows. For example, the user A121 is linked to the upper building A101. As a result, the display condition name given to the user A is not only the building A information 111 linked to the building A101, but also the building A fire extinguisher linked to the fire extinguishing equipment A102 and the alarm equipment A103 which are lower layers of the building A101. The range extends to the facility 112 and the building A alarm facility 113. On the other hand, the user B122 is linked to the fire extinguishing equipment A102 in the lower hierarchy. Thus, the display condition name given to the user B is only the building A fire extinguishing equipment 112 linked to the fire extinguishing equipment A102. As described above, in the hierarchical type configuration, by appropriately selecting the type associated with the user, the range of data that can be displayed by the user can be easily set.

  FIG. 4 is a diagram illustrating an example in which the data structure of management data is described in a table format. Here, as a management table constituting the management data 20, a type hierarchy management table 21T that manages by hierarchizing types, a display condition management table 22T that defines a search expression for display conditions, and a relationship between the type hierarchy and display conditions are managed. The type / display condition relationship table 24T and the type / user relationship table 25T for managing the relationship between the type hierarchy and the user will be described.

  The type hierarchy management table 21T in (a) describes a type group and various hierarchical levels constituting the type group. For example, group A includes three types (001, 002, 003), and describes the hierarchy level (1, 2) and the parent-child relationship of the types. With this table, it is possible to recursively search the hierarchical relationship of the type of interest (the types of the upper and lower layers).

  The display condition management table 22T in (b) describes a search expression for the display condition name. By using this table, a search expression can be acquired. In addition to the search expression, a table name to be searched may be described.

  The type hierarchy / display condition relationship table 24T in (c) describes the association state between the type name and the display condition name. The display conditions for each type can be acquired by searching this table.

  The type hierarchy / user relationship table 25T in (d) describes the association state between the type name and the user name. The type assigned to the logged-in user can be acquired by searching this table.

  FIG. 5 is a flowchart showing the flow of the facility data search and display process. The following processing proceeds while the data processing unit 3 of the data management device 2 refers to the first and second databases 4 and 5. In the following description, it is assumed that the user is, for example, the user A121 in FIG.

When the user logs in from the input device 6 in S201, the data processing unit 3 refers to the user management data 23 and confirms that the user A is registered.
In S202, the type / user relationship data 25 is referred to, and the type (first type) associated with the user A is acquired. Referring to FIG. 3, it can be seen that the user A121 is linked to the building A101.

In S203, the type hierarchy management data 21 is referred to, and the type list (second type) belonging to the lower level of the acquired first type is acquired. Referring to FIG. 3, it can be seen that the fire extinguishing equipment A102 and the alarm equipment A103 belong to the lower hierarchy of the building A101.
In S204, the type / display condition relationship data 24 is referred to, and the display condition names associated with the various types (first and second) acquired in S202 and S203 are acquired. With reference to FIG. 3, the building A information 111, the building A fire extinguishing equipment 112, and the building A warning equipment 113 are acquired as corresponding display condition names. Each acquired display condition name may be displayed once on the display device 7 and the user may select a display condition name.

In S205, the display condition management data 22 is referred to, and a search expression for the display condition name acquired (selected) in S204 is acquired.
In S206, data matching this is extracted from the equipment data 10 using the search expression acquired in S205.
In S207, the extracted equipment data is displayed on the display device 7.

FIG. 6 is a diagram illustrating an example of a display screen that displays the extracted facility data.
When the user 301 logs in to the system, the equipment group screen 300 is displayed first, and the equipment type 302 and the display condition 303 related to the user 301 are displayed. In the equipment type 302, the equipment type associated with the user 301 and the equipment type belonging to the lower hierarchy are searched and displayed. The display condition 303 is a display condition set in various levels, and when there are a plurality of display conditions, the number of cases is displayed and the user is allowed to select. When the user selects a desired display condition, corresponding facility data is extracted according to a defined search expression.

  On the equipment ledger screen 310, the equipment data extraction result is displayed. As a result of the extraction, if there are a plurality of corresponding data, the number of data can be displayed and the user can select it. In addition, a character string reminiscent of the corresponding data may be displayed.

  As described above, in the first embodiment, the facility data is managed hierarchically (type hierarchy management), and the display condition (extraction condition) and the user are managed in association with each type (linkage management). Even users belonging to the same organization can extract different types of data depending on the user, and user convenience is improved.

In this embodiment, a process for changing the type managed by the user will be described.
FIG. 7 is a diagram illustrating an example of change in management data accompanying a change in user management.
The type hierarchy management data 41 in (a) includes a type A 401 and a type B 402, and the display condition A 411 is linked to the type A 401, and the display condition B 412 is linked to the type B 402. Regarding the user, the type A 401 was managed by the user A 421 and the user B 422 before the change, and no user was managed by the type B 402. After the user management change, the management of the user B 422 for the type A 401 is removed, and the type B 402 is managed by the user A 421 and the user B 422.

  In the management data change in this case, the association of the user B422 with respect to the type A401 is deleted, and the association with the type B402 is newly made as the user B422 '. Further, the user A 421 ′ is newly associated with the type B 402. Of course, the user A421 and the user A421 'are the same user, and the user B422 and the user B422' are the same user. In this way, the management change of the user can be easily executed by changing the type to be associated.

  (B) is a type / user relationship table 45T which describes the association status between the type and the user. The association state can be described by a combination of the type name and the user name, but this table 45T further describes the application period 450 of the association state. In other words, the association state between the type name and the user name described is a valid period for the described application period 450 (from the application start date to the application end date), and is invalid for other periods. By providing the application period 450 in this manner, the type / user relationship data can be easily changed, and usability is improved in an organization that frequently requires user management changes.

1: Facility management system,
2: Data management device
3: Data processing unit,
4: First database,
5: Second database,
6: Input device,
7: Display device,
10: Equipment data,
20: management data,
21, 41: Type hierarchy management data,
22: Display condition management data,
23: user management data,
24: Type / display condition relationship data,
25: Type / user relation data,
21T: Type hierarchy management table,
22T: Display condition management table,
24T: Type / display condition relationship table,
25T, 45T: Type / user relationship table,
300: Equipment group screen,
310: Equipment ledger screen,
450: Application period.

Claims (4)

In an equipment management system comprising a data management device for managing equipment data,
The data management device includes:
A first database that holds the facility data classified into a plurality of types;
A second database holding management data for retrieving the equipment data;
A data processing unit that registers the facility data and management data in the first and second databases, and retrieves the facility data using the management data;
The management data includes
Type hierarchy management data for hierarchizing and managing the types of the equipment data,
Type / display condition relationship data that links and manages display conditions for searching the facility data for each type,
Type / user relationship data for managing a user who is authorized to search the facility data for each type,
An equipment management system comprising: The facility management system according to claim 1,
The data processing unit, when searching the facility data using the management data according to a user request,
With reference to the type / user relationship data, the first type associated with the user is acquired,
Referring to the type hierarchy management data, obtaining a second type belonging to a lower hierarchy of the obtained first type;
Refer to the type / display condition relationship data, acquire the respective display conditions associated with the acquired first and second types,
A facility management system, wherein the facility data is searched according to the acquired display conditions. The facility management system according to claim 1 or 2,
The facility management system described in the type / user relation data describes an application period in which the association state between the type and the user is valid. The facility management system according to claim 1 or 2,
The data management device is connected to an input device for inputting a request from a user and a display device for displaying the retrieved equipment data.
In the display device, the equipment type and the display conditions associated with the user are displayed as an equipment group screen,
When a desired display condition is selected by the user, the equipment management system displays the equipment data searched according to the display condition as an equipment ledger screen.

Images