JP5256946B2 - Information management system and information management method - Google Patents

Description

  The present invention relates to an information management system and an information management method for managing incident information.

In recent years, when various incidents such as incidents occur in a company, the recurrence is prevented. In this case, in order to prevent the recurrence of various incidents, it is effective to share information (incident information) about the occurred incidents between the departments. In particular, corporate forms have recently diversified, and there are forms composed of a plurality of group companies. Therefore, an information management system that manages information shared by group companies using a database has been studied (for example, see Patent Document 1). In the technology described in Patent Document 1, formats such as procurement of goods and accounting processing in a group are unified in a group company, the group companies are connected by an intranet, and a centralized database is provided on the intranet. In this case, when accessing the centralized database, the employee master set in the in-house server and the entered employee number and password are collated to authenticate the access rights to the database. The company code to which belongs is acquired. Then, the database is accessed using the company code as a key, the display screen is controlled according to the parameters of each company, and the input information is stored. The stored information is provided to an accounting system terminal, a system for ordering, or the like.
Japanese Patent Laying-Open No. 2005-149392 (FIGS. 5 to 7)

  However, when an information management server that manages information shared by a group company is individually accessed from each client terminal of the group company, the load on the information management server increases. When the load increases, it is not possible to provide smooth data to each client terminal.

  On the other hand, if the standard is unified from the beginning, it is easy to construct a unified rule, but each group company may already manage information based on its own rule. In this case, if the unique rule is unilaterally changed to the unified rule, it may cause extra time and confusion. Even if incident information is considered to be known to each group company, it may be meaningful information for other group companies, so it is not restricted by each group company's own rules. Management is also necessary.

  The present invention has been made in view of the above-mentioned problems, and an object thereof is to provide an information management system and an information management method capable of uniformly managing incident information even if unique rules are different. It is in.

In order to solve the above problems, the invention described in claim 1 includes an incident data storage means for storing incident information, a rule correspondence data storage means for storing correspondence information between a unique rule and a general rule, and a client terminal. An information management system comprising: a local server including a local control unit to be connected; an overall data storage unit that stores incident information; and an overall management server that includes an overall control unit connected to the local server, When the incident information is acquired from the client terminal, the local control unit records the incident information as management registration information in the incident data storage unit, and records the management registration information in the incident data storage unit. If this management registration information Management including the incident information converted by converting the setting value set based on the included unique rule into the setting value based on the general rule using the correspondence information of the rule correspondence data storage unit Reporting means for transmitting registration information to the overall management server, wherein the overall control means stores the management registration information in the overall data storage means when acquiring the management registration information from the local server. The gist is that a recording means is provided.

  According to a second aspect of the present invention, in the information management system according to the first aspect, the local control unit is connected to a notification condition storage unit that stores a notification condition for transmitting incident information to the overall management server. The reporting means, after converting the setting value based on the general rule, compares the converted setting value with the value of the notification condition, and if the converted setting value satisfies the notification condition, The gist is to transmit the registration information to the overall management server.

  According to a third aspect of the present invention, in the information management system according to the first or second aspect, the local control unit makes a transmission request for incident information to the overall management server at each predetermined call time. Further comprising information update means for storing the incident information acquired in response to the incident data storage means, wherein the overall control means records the incident information recorded in the overall data storage means in response to a request from the local server. Is further provided with information distribution means for transmitting the message to the local server.

  According to a fourth aspect of the present invention, in the information management system according to the third aspect, when the information update unit acquires incident information from the general management server, the setting based on the general rule included in the incident information The gist is to convert a value into a set value based on the unique rule using the correspondence information of the rule correspondence data storage means, and store the converted incident information in the incident data storage means.

  The invention according to claim 5 includes incident data storage means for storing incident information, rule correspondence data storage means for storing correspondence information between unique rules and general rules, and local control means connected to the client terminal. An information management method in a system having a local server, an overall data storage means for storing incident information, and an overall management server provided with an overall control means connected to the local server, wherein the local control means is the client When the incident information is acquired from the terminal, the incident information recording stage for recording the incident information as management registration information in the incident data storage means, and the management registration information when the management registration information is recorded in the incident data storage means Before included in The setting value set based on the unique rule is converted into the setting value based on the overall rule using the correspondence information in the rule correspondence data storage means, and the management registration information including the converted incident information is converted to the overall management information. A management information recording step for storing the management registration information in the overall data storage means when the management registration information is acquired from the local server. The gist is to do.

(Function)
According to the present invention, when the local control unit acquires incident information from the input terminal, the local control unit records the incident information as management registration information in the incident data storage unit. When the management control information is recorded in the incident data storage means, the local control means uses the correspondence information of the rule correspondence data storage means to set the setting value set based on the unique rule included in the management registration information. The management registration information including the converted incident information is converted to a setting value based on the overall rule and transmitted to the overall management server. When acquiring the management registration information from the local server, the overall control unit stores the management registration information in the overall data storage unit. For this reason, the incident information obtained by converting the setting value set based on the unique rule into the setting value set based on the overall rule is transmitted to the overall management server. Therefore, the overall management server can uniformly manage incident information from local servers with different unique rules.

  According to the present invention, the local control means, after converting to the set value based on the overall rule, compares the converted set value with the value of the notification condition, and if the converted set value satisfies the notification condition The management registration information is transmitted to the overall management server. Therefore, the overall management server can acquire incident information from each local server based on a certain standard based on the overall rules. Therefore, the overall management server can automatically acquire and manage incident information that satisfies the reporting conditions.

  According to the present invention, the local control unit makes a transmission request for incident information to the overall management server at every predetermined call time, and stores the incident information acquired in response to the request to the incident data storage unit. The overall control means transmits incident information recorded in the overall data storage means to the local server in response to a request from the local server. Therefore, even if the overall control means cannot freely access the local control means, the incident information acquired and managed from the local server can be periodically provided to the local server. For this reason, a client terminal connected to a local server can acquire incident information registered in another local server without directly accessing the overall management server.

  According to the present invention, when the local control means acquires the incident information from the overall management server, the local control means uses the correspondence information in the rule correspondence data storage means to set the setting value based on the overall rule included in the incident information. Is converted into a set value based on the above, and the converted incident information is stored in the incident data storage means. Therefore, a person who accesses the local server and views the incident information can grasp the incident information registered in the other local server with the set value according to his / her own rule.

  According to the present invention, when the unique rule is included, the incident information converted into the general rule is transmitted to the general management server, so the general management server receives the incident information from the local server with a different unique rule, It can be managed uniformly.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that incident information is shared between a plurality of group companies and the controlling company that supervises these group companies. As shown in FIG. 1, a description will be given of an information management system including an in-company management server 10 as a local server of each group company and an overall management server 20 of the controlling company. In the present embodiment, the in-company management server 10 manages information (incident information) related to incidents occurring in each company. Here, the incident includes not only an event such as an incident that has occurred, but also an event that did not actually result in an incident but may have become an incident (an event called a “hiari hat”). The overall management server 20 manages incident information generated in each group company in an integrated manner, and manages each incident information managed in response to a request from the in-house management server 10 in each in-house management server 10. To deliver.

It is assumed that the in-company management server 10 cannot perform writing from external devices including the overall management server 20. This in-company management server 10 is connected to a plurality of client terminals (not shown) used in each company and allows writing from these client terminals. The client terminal includes a keyboard and a pointing device for inputting and selecting various data and instructions, and a display for displaying various processing screens.

  The in-company management server 10 includes a control unit 11 as a local control unit, a connection data storage unit 12, an incident data storage unit 13, a rule correspondence data storage unit 14, and a notification condition data storage unit 15. Here, the incident data storage unit 13 functions as an incident data storage unit, the rule correspondence data storage unit 14 functions as a rule correspondence data storage unit, and the notification condition data storage unit 15 functions as a notification condition storage unit.

  The control unit 11 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing described later (processing including an incident information recording stage, a reporting stage, an information updating stage, and the like). Then, by executing the in-company management server program for this purpose, the control unit 11 causes the connection means 110, the setting processing means 111, the incident reporting means 112, the rule conversion means 113, and the wake-up call processing as information updating means. It functions as the means 114. Further, the control unit 11 functions as an incident information recording unit that stores incident information from the client terminal in the incident data storage unit 13.

  The connection unit 110 executes processing for connecting to the overall management server 20. The connection means 110 stores connection destination specifying data for specifying the overall management server 20, and uses this connection destination specifying data to access the overall management server 20 connected via the network.

  The setting processing unit 111 acquires the connection destination specifying data and the wake-up call time of the overall management server 20 and executes setting processing such as connection to the overall management server 20 and the start time of the wake-up call process. The setting processing unit 111 executes processing when the in-company management server 10 first connects to the overall management server 20.

  The incident reporting unit 112 executes a process of transmitting incident information to the overall management server 20. The incident reporting unit 112 transmits only incident information registered in the in-company management server 10 via the client terminal.

  The rule conversion unit 113 executes processing for converting the setting value given based on the rule used in the in-house management server 10 into the setting value based on the rule used in the overall management server 20.

  The wake-up call processing unit 114 accesses the overall management server 20 to acquire incident information and records it in the incident data storage unit 13 every morning at a predetermined time. Thereby, the wake-up call processing means 114 executes an incident information update process.

  On the other hand, the connection data storage unit 12 stores connection data 120 used by each in-company management server 10 to connect to the overall management server 20 as shown in FIG. This connection data 120 is recorded when the in-company management server 10 first accesses the overall management server 20. The connection data 120 includes data relating to an organization code, a database number (DB number), and a wake-up call time.

  In the organization code data area, data relating to an identifier (organization code) for identifying the organization (in this embodiment, each group company) that manages the incident information by the in-company management server 10 is recorded.

  In the DB number data area, data relating to an identification number (DB number) for specifying a database managing incident information in this organization is recorded. The in-company management server 10 can be specified by this DB number and organization code.

In the wake-up call time data area, data relating to the time for the in-company management server 10 to access the overall management server 20 every morning is recorded.
As shown in FIG. 2B, the incident data storage unit 13 stores incident data managed in each group company. This incident data includes incident attribute data 131 and incident document data 132. Incident attribute data 131 is data related to attributes of incident information. Incident document data 132 is data relating to a document created for incident information.

The incident attribute data 131 includes data relating to an incident identifier, a general identifier, a classification item, an importance level, and a registration date and time.
Data relating to an identifier (incident identifier) for identifying each incident is recorded in the incident identifier data area. In the present embodiment, this incident identifier is given only to incident information registered from a client terminal connected to the in-company management server 10.

In the overall identifier data area, data relating to an identifier (overall identifier) assigned in the overall management server 20 for specifying this incident is recorded.
In the classification item data area, data specifying the classification item of the incident is recorded. Here, an item indicating an incident or an item indicating a so-called “hiari hat” is used as a classification item.

  Data relating to a value indicating the importance of the incident is recorded in the importance data area. As this importance, a unique importance in the company managed by the in-company management server 10 is used.

In the registration date / time data area, data on the date and time when the incident information is registered is recorded.
On the other hand, the incident document data 132 includes data relating to an incident identifier, a general identifier, an access restriction flag, a document type, document content, and update registration date and time.

  Data relating to an identifier (incident identifier) for identifying each incident is recorded in the incident identifier data area. In the present embodiment, this incident identifier is given only to incident information registered from a client terminal connected to the in-company management server 10.

In the overall identifier data area, data relating to an identifier (overall identifier) assigned in the overall management server 20 for specifying this incident is recorded.
In the access restriction flag data area, data relating to a flag indicating whether or not there is an access restriction on the document is recorded. In the present embodiment, the access restriction can be set to “present” only when the incident document data 132 is registered from the client terminal connected to the in-company management server 10. When the flag indicating that the access restriction is “present” is recorded, the in-company management server 10 does not report the incident document data 132 to the overall management server 20. On the other hand, the incident document data 132 acquired from the overall management server 20 and stored in the incident data storage unit 13 is recorded with an access restriction flag “None”.

  In the document type data area, data relating to an identifier for specifying the type of the document is recorded. As the document type, for example, identifier data for specifying the type of document such as a progress report or a recurrence prevention document is used.

In the document content data area, data relating to the content of the document is recorded.
In the update registration date / time data area, data related to the date / time (year / month / day and time) when the document was registered or the date / time when the document was updated / registered when the document was updated is recorded.

  As shown in FIG. 2C, the rule correspondence data storage unit 14 stores correspondence data 140 in which the setting value set based on the unique rule and the setting value set based on the general rule are associated with each other. ing. Specifically, the correspondence data 140 is data in which a correspondence item identifier, a local value based on a unique rule, and a common value based on a general rule are associated with each other. Here, the corresponding item identifier is an item identifier that identifies an item. The unique rule is an in-house rule used by each company. The general rule is an internal rule used by the general company. For example, when an identifier that specifies the importance is described as the corresponding item identifier, the importance (local value) based on the unique rule and the importance (common value) based on the overall rule are associated with each other.

  The report condition data storage unit 15 stores report condition data. The notification condition data is data relating to a condition that is satisfied in order to automatically report incident information registered in the in-company management server 10 from the client terminal to the overall management server 20. This notification condition data is recorded before the in-company management server 10 is operated. The report condition data includes data regarding a report condition identifier and a report condition.

In the notification condition identifier data area, data relating to an identifier for specifying each notification condition is recorded.
In the notification condition data area, a condition relating to a notification condition (item identifier indicating the type of data and its value) that is satisfied when automatic notification is made is recorded. For example, when the classification item of the incident attribute data 131 is “incident” and the automatic notification is performed when the common value is equal to or higher than a predetermined notification condition value, the classification item data and the “importance” are set as the notification condition data types ”Is recorded, and values indicating“ incident ”and“ notice condition value or more ”are recorded as respective values.

  On the other hand, the overall management server 20 connected to the in-company management server 10 via a network is connected to an overall client terminal (not shown). This general client terminal is used for inputting the content of notification to be notified to each in-house management server 10 and outputting an alarm. The overall client terminal includes a keyboard and a pointing device for inputting and selecting various data and instructions, and a display for displaying various processing screens.

  The overall management server 20 includes an overall control unit 21 as an overall control unit, an organization management data storage unit 22, a call time data storage unit 23, a contact data storage unit 24, an overall data storage unit 25 as an overall data storage unit, and a correspondence A support requirement data storage unit 26 is provided.

The overall control unit 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing described later (processing including an overall information recording stage and an information distribution stage). Then, by executing the overall management server program for this purpose, the overall control unit 21 causes the access response processing means 210, the connection data determination processing means 211, the incident information registration means 212 as the overall information recording means, and the response support process. Means 213 and information providing means 214 as information distribution means.

  In response to a request from the in-company management server 10, the access handling processing unit 210 executes processing for distributing the processing to the connection data determination processing unit 211, the incident information registration unit 212, and the information providing unit 214.

  The connection data determination processing unit 211 executes processing for determining data for connection to the in-company management server 10 when it is accessed for the first time from the in-company management server 10. Specifically, the connection data determination processing unit 211 acquires an organization name from the in-company management server 10 and specifies an organization code associated with the organization name. Furthermore, the connection data determination processing unit 211 newly sets a time at which the processing load does not increase with respect to the already registered call time in a pre-stored time zone (in the present embodiment, 6:00 to 8:00). Determine the correct call time. Further, the connection data determination processing unit 211 stores connection destination specifying data for specifying the overall management server 20 in order to connect to the overall management server 20.

  When the incident information registration unit 212 receives the incident information transmitted from the in-company management server 10, the incident information registration unit 212 executes a process of registering the incident information in the overall data storage unit 25.

  The response support processing means 213 executes processing for supporting the response to be performed for this incident according to the incident information registered in the overall data storage unit 25. Specifically, when the registered incident information satisfies the response support requirement stored in the response support requirement data storage unit 26, the response content associated with the requirement (for example, press release or recall investigation) is executed. Output an alarm to the client terminal.

  The information providing unit 214 transmits the incident information stored in the overall data storage unit 25 to the internal management server 10 when an update information transmission request is acquired in response to the information acquisition request from the internal management server 10.

  On the other hand, the organization management data storage unit 22 stores organization management data 220 for managing the organization, as shown in FIG. The organization management data 220 includes each organization name and the corresponding organization code.

  In the organization name data area and the organization code data area, the name of this organization and an identifier (organization code) for specifying this organization are recorded. In this embodiment, the company name of the group company is used as the organization name.

  Further, as shown in FIG. 3B, the call time data storage unit 23 stores call time data 230 related to a wake-up call time when each in-company management server 10 accesses the overall management server 20. The call time data 230 is used by the connection data determination processing unit 211 to determine a new call time so that accesses from the in-company management server 10 are distributed. Further, the call time data 230 is recorded when new call time data is determined. In the call time data 230, data relating to the organization code, DB number, and wake-up call time is recorded.

In the organization code data area, data relating to an identifier (organization code) for identifying the organization in which the in-company management server 10 manages incident information is recorded.
In the DB number data area, data relating to an identification number (DB number) for specifying a database managing incident information in this organization is recorded. The in-company management server 10 can be specified by this DB number and organization code.
In the wake-up call time data area, data relating to the time for the in-company management server 10 to access the overall management server 20 every morning is recorded.

  In the contact data storage unit 24, data related to contact contents to be communicated to each in-company management server 10 is recorded. This contact data is registered when it is input via the central client terminal connected to the central management server 20. This contact data includes data related to the contact date and the content of the contact to be communicated to each in-company management server 10.

  The overall data storage unit 25 stores incident overall data. The incident management data includes incident management attribute data 251 and incident management document data 252 as shown in FIG. The incident general attribute data 251 is data regarding incident attributes managed by the general management server 20. The incident general document data 252 is data relating to a document created for incident information managed by the general management server 20.

The incident general attribute data 251 includes data regarding general identifiers, organization codes, DB numbers, incident identifiers, classification items, importance levels, registration dates and the like.
In the overall identifier data area, data relating to an identifier (overall identifier) assigned in the overall management server 20 for specifying each incident is recorded.

  In the organization code data area and the DB number data area, the data related to the identifier (organization code) for identifying the organization in which this incident has occurred and the in-company management server 10 that manages the information related to this incident are registered. Data relating to an identification number (DB number) for recording is recorded. In the present embodiment, it is possible to identify the in-company management server 10 that acquires and manages this incident information from the client terminal from these organization codes and DB numbers.

  In the incident identifier data area, data related to an identifier (incident identifier) for identifying the incident is recorded in the in-company management server 10 that manages information related to the incident.

In the classification item data area, data specifying the classification item of the incident is recorded.
Data relating to a value indicating the importance of the incident is recorded in the importance data area. As this importance, the standardized importance for the entire group company is used.

In the registration date / time data area, data related to the date / time when this incident information was registered is recorded.
On the other hand, the incident general document data 252 includes data related to a general identifier, document type, document content, and update registration date and time.

In the overall identifier data area, data relating to an identifier (overall identifier) assigned in the overall management server 20 for specifying this incident is recorded.
In the document type data area and the document content data area, data relating to an identifier for specifying the type of the document and data relating to the contents of the document are recorded.

In the update registration date / time data area, data related to the date / time (year / month / day and time) when the document was registered or the date / time when the document was updated / registered when the document was updated is recorded.
The response support requirement data storage unit 26 stores response support requirement data. This response support requirement data is data relating to conditions that are satisfied in order to execute a response that can be taken in response to the incident information acquired from the in-company management server 10. This response support requirement data is registered before the overall management server 20 operates. The correspondence support requirement data includes correspondence content identifiers, correspondence content, and data related to the correspondence requirements.

In the corresponding content identifier data area and the corresponding content data area, data relating to an identifier for specifying each corresponding content and data relating to the corresponding content are recorded.
In the corresponding requirement data area, conditions for executing each corresponding content are recorded. For example, assume that a predetermined response (for example, press release) is performed when the classification item of the incident general attribute data 251 is “incident” and the importance value is equal to or greater than a predetermined response reference value. In this case, an item identifier (category item and item identifier indicating importance) corresponding to the identifier indicating the press release and the corresponding content (press release) and each value (“incident”) are indicated. And a value indicating “corresponding reference value or more”) are stored.

  Processing executed by the information management system configured as described above will be described with reference to FIGS. Here, the connection setting process, the incident report process, the wake-up call process, and the browsing process will be described in this order. Here, in the connection setting process, when the in-house management server 10 accesses the overall management server 20 for the first time, a setting for transmitting and receiving data between the in-house management server 10 and the overall management server 20 is performed. In the incident report process, incident information acquired from the client terminal in the in-house management server 10 is reported to the overall management server 20. In the wake-up call process, the integrated management server 20 delivers incident information every morning in response to a request from the in-house management server 10. In the browsing process, using the client terminal connected to the in-company management server 10, the incident information manager of each company browses information on incidents occurring in other group companies.

(Connection setting process)
First, a connection setting process that is performed when the in-company management server 10 is newly provided and first accesses the overall management server 20 will be described with reference to FIG.

  The control unit 11 of the in-company management server 10 first accesses the overall management server 20 and executes an organization code and DB number inquiry process (step S1-1). Specifically, the setting processing unit 111 of the control unit 11 accesses the overall management server 20 and executes a connection setting request in response to an instruction from the client terminal.

  Upon receiving this connection setting request, the overall control unit 21 of the overall management server 20 transmits organization name input screen data to the in-company management server 10. Specifically, the access handling processing unit 210 of the overall control unit 21 transmits organization name input screen data for acquiring an organization name that manages incident information. The in-company management server 10 displays an organization name input screen on the display of the client terminal. This organization name input screen includes an input field for inputting an organization name and a send button. Here, the in-company administrator inputs his organization name (group company name) in the input field and selects a transmission button. The client terminal transmits data related to the organization name input on the organization name input screen to the overall management server 20.

  Next, the overall control unit 21 of the overall management server 20 executes a wake-up call time setting process (step S1-2). Here, the overall control unit 21 specifies the organization code and DB number of the in-company management server that has transmitted the connection setting request. Specifically, the connection data determination processing unit 211 of the overall control unit 21 extracts the organization management data 220 including the organization name from the organization management data storage unit 22 and specifies the organization code corresponding to the organization name. .

Next, the connection data determination processing unit 211 calls the call time data 23 including the organization code.
0 is searched in the call time data storage unit 23. Here, when the corresponding call time data 230 is not extracted, the connection data determination processing unit 211 specifies “1” as the DB number. When the call time data 230 including the organization code is extracted, the last DB number of the call time data 230 is specified, and the number next to the DB number is specified as the DB number.

  Next, the connection data determination processing unit 211 extracts each wake-up call time from the call time data 230 recorded in the call time data storage unit 23. Then, the connection data determination processing unit 211 determines a new call time by using the time zone stored in advance and each extracted wake-up call time.

  Then, the connection data determination processing unit 211 generates call time data 230 that associates the identified organization code and DB number with the set wake-up call time, and stores the call time data 230 in the call time data storage unit 23.

  Next, the overall control unit 21 of the overall management server 20 executes a process for providing an organization code, a DB number, and a wake-up call time (step S1-3). Specifically, the connection data determination processing unit 211 of the overall control unit 21 transmits setting data to the in-company management server 10. The setting data includes data related to the organization code, DB number, and wake-up call time stored in the call time data storage unit 23. Further, the setting data includes connection destination specifying data for specifying the overall management server 20.

  The control unit 11 of the in-house management server 10 executes a storage process of the organization code, DB number, and wake-up call time (step S1-4). Specifically, the setting processing unit 111 of the control unit 11 generates connection data 120 including the organization code, DB number, and wake-up call time of the acquired setting data, and stores the connection data 120 in the connection data storage unit 12. Further, the setting processing unit 111 of the control unit 11 stores connection destination specifying data for specifying the overall management server 20 with respect to the connecting unit 110. Thus, the connection setting process ends.

(Incident report processing)
Next, incident report processing for reporting incident information registered in the in-house management server 10 from the client terminal connected to the in-house management server 10 to the overall management server 20 will be described with reference to FIG.

  The control unit 11 of the in-company management server 10 executes a process for registering incident information acquired from the client terminal (step S2-1). Specifically, the incident reporting unit 112 of the control unit 11 transmits initial screen data recorded in the control unit 11 to the client terminal when accessed from the client terminal. The client terminal displays an initial screen including various menu buttons on the display. The various menu buttons include a connection setting button, an incident information new input button, an incident information update input button, an information browsing button, and the like.

  Here, when the incident manager newly registers incident information related to a newly generated incident, the incident information new input button on the initial screen is selected. The client terminal transmits a new input screen request to the in-company management server 10. The in-company management server 10 generates new input screen data including an incident attribute information input field and a document selection field, transmits it to the client terminal, and displays the new input screen on the display of the client terminal. In this new input screen, the administrator inputs the classification item and the importance as incident attribute information.

  Furthermore, the administrator selects the “report” document in the document selection field. When the document selection field is selected, a document creation screen is displayed on the display of the client terminal. This document creation screen includes a selection field for selecting an access restriction flag, an entry field for describing document contents, a registration button, and a notification button. The administrator selects the access restriction flag in the selection field and enters the document content in the entry field. When the administrator reports this incident information to the supervising company and thinks that other group companies should share the information, the administrator selects the report button. In addition, when the administrator thinks that this incident information is managed only by the in-company management server 10 and does not need to share information with other group companies, the registration button is selected.

  On the other hand, when the incident information already registered in the in-company management server 10 is updated and registered, the incident information update input button on the initial screen is selected. The client terminal transmits an incident information update input screen request to the in-company management server 10. The control unit 11 of the in-company management server 10 extracts incident attribute data 131 including an incident identifier in the incident data storage unit 13. In this case, incident attribute data 131 related to the incident information registered from the client terminal connected to the in-company management server 10 is extracted. And the control part 11 produces | generates the list list screen containing the extracted incident attribute data 131, and displays it on the display of a client terminal.

  Here, the administrator selects the incident identifier of the incident information to be updated and registered on the list list screen. The client terminal transmits the selected incident identifier to the control unit 11 of the in-house management server 10.

  The control unit 11 of the in-house management server 10 extracts the incident attribute data 131 and the incident document data 132 including the received incident identifier from the incident data storage unit 13, generates update information input screen data, and transmits it to the client terminal To do. The client terminal displays an update information input screen on the display. In the update information input screen, the document content of the incident document data 132, an additional input field, a new document creation button for creating a new document, a button for selecting the type of document to be newly created, registration Button and a report button are included.

  Here, for example, when a progress report is added to a report of an incident that has occurred, the administrator inputs the content to be added to the additional input field. In addition, when creating a new document (for example, a recurrence prevention document) and adding incident document data 132 relating to already registered incident information, a type of a newly created document is selected and a new document creation button is selected. Select. A document creation screen is displayed on the display of the client terminal. As described above, this document creation screen includes a selection field for selecting an access restriction flag, an entry field for describing the document contents, a registration button, and a notification button. The administrator selects the access restriction flag in the selection field of the document creation screen, and enters the document content in the entry field. The administrator selects the report button when reporting the incident information to another group company, and selects the registration button in other cases.

  When the report button or the registration button is selected on the document creation screen or the update information input screen, the client terminal transmits registration data to the in-company management server 10. In the case of new registration, the registration data includes data relating to the set classification item, importance, the document type corresponding to the selected report, the selected access restriction flag, and the document content entered in the entry field. In the case of update registration, an incident identifier, an access restriction flag, a document type and document content of the input document are included. Further, when the report button is selected, a report flag is included in the registration data.

  And the control part 11 of the management server 10 in a company registers incident information. Specifically, the control unit 11 gives an incident identifier when the registration data does not include an incident identifier. Then, the control unit 11 generates incident attribute data 131 including the incident identifier, the classification item and importance included in the acquired new registration data, and records them in the incident data storage unit 13. Further, the control unit 11 includes the current time and date at this time in the incident attribute data 131 as the registration date and time. Then, the control unit 11 generates incident document data 132 including the assigned incident identifier, the document type of the received registration data, the access restriction flag, and the document content, and records the incident document data 132 in the incident data storage unit 13. Further, the control unit 11 records the current time at this time in the incident document data 132 as the update registration date / time. At this stage, the general identifier data area of the incident attribute data 131 and the incident document data 132 is blank.

  On the other hand, if the registered data includes an incident identifier, the control unit 11 searches the incident data storage unit 13 for incident document data 132 including the incident identifier and document identifier of the registered data. If there is corresponding incident document data 132, the incident report unit 112 adds and updates the incident document data 132 with the document content included in the registration data. Further, the incident report unit 112 includes the current time at this time as the update registration date / time in the incident document data 132.

  On the other hand, when there is no corresponding incident document data 132, the control unit 11 generates incident document data 132 including the incident identifier, the received access restriction flag, the document type, and the document content, and stores them in the incident data storage unit 13. Remember. Further, the control unit 11 includes the time at this time as the update registration date / time in the incident document data 132.

  Next, the control unit 11 of the in-house management server 10 executes a determination process for the presence / absence of a report instruction (step S2-2). Specifically, the incident reporting unit 112 of the control unit 11 makes a determination based on the presence or absence of a report flag in the registration data.

  Here, when it is determined that the registration data does not include a report flag and there is no report instruction (in the case of “NO” in step S2-2), the control unit 11 of the in-house management server 10 has its own. Judgment processing for the presence or absence of a rule is executed (step S2-3). Specifically, the incident reporting unit 112 of the control unit 11 determines that there is a unique rule when the correspondence data 140 is stored in the rule correspondence data storage unit 14.

  Here, when there is a unique rule (in the case of “YES” in step S2-3), the control unit 11 of the in-house management server 10 executes a rule conversion process (step S2-4). Specifically, the rule conversion unit 113 of the control unit 11 extracts correspondence data 140 including each setting value (local value) of the incident attribute data 131 corresponding to each corresponding item identifier from the rule correspondence data storage unit 14. Then, the rule conversion unit 113 identifies a common value of the correspondence data 140 corresponding to each extracted local value, and temporarily stores it in the memory in association with the incident identifier of the incident attribute data 131.

  Next, the control unit 11 of the in-company management server 10 executes a determination process as to whether or not the notification condition is satisfied (step S2-5). Specifically, the incident reporting unit 112 of the control unit 11 compares each value for each item of the notification condition data with the converted common value temporarily stored in the memory in association with the incident identifier.

  The incident reporting means 112, when the registered incident data satisfies the condition of the report condition data and the access restriction flag indicating that there is no access restriction is registered, Judge as satisfied.

  Here, when the report condition is not satisfied (in the case of “NO” in step S2-5) or when there is no unique rule (in the case of “NO” in step S2-3), the incident report processing ends.

  On the other hand, when there is a report instruction (in the case of “YES” in step S2-2) or when the notification condition is satisfied (in the case of “YES” in step S2-5), the control unit 11 of the in-company management server 10 Performs notification processing (step S2-6). Specifically, the incident reporting unit 112 of the control unit 11 sets incident data generated from registration data including the report flag or incident data satisfying the reporting condition as a reporting target. Then, the connection unit 110 connects to the overall management server 20 using the connection destination specifying data. The incident reporting unit 112 of the control unit 11 transmits report data to be reported to the overall management server 20 via the connection unit 110. The connection means 110 includes the organization code and DB number of the connection data storage unit 12 in this report data.

  Here, when the general identifier is not included in the incident data to be notified, the incident report unit 112, the incident attribute data 131, and the document type, document content and incident document data 132 including the incident identifier included in the incident attribute data 131 are included. The update registration date and time are included in the report data. In this case, when the incident attribute data 131 includes a local value, the converted common value is included in the notification data instead of the local value. If the incident attribute data 131 to be notified includes a general identifier, the incident report unit 112 determines the general identifier and the document type, document content, and update registration date and time of the incident document data 132 including the general identifier. Are included in the report data.

  The overall control unit 21 of the overall management server 20 that has received the incident report data executes a registration process in the overall data storage unit 25 (step S2-7). Here, the incident information registration unit 212 of the overall control unit 21 determines whether or not the overall identifier is included in the report data.

  When the general identifier is not included in the report data, the incident information registration unit 212 provides the general identifier. The incident information registration unit 212 generates incident general attribute data 251 including the general identifier, the organization code included in the incident report data, the DB number, and the incident attribute data 131, and records the incident general attribute data 251 in the general data storage unit 25. Furthermore, the overall control unit 21 includes the current time at this time as the registration date and time in the incident overall attribute data 251.

  Further, the incident information registration unit 212 generates incident general document data 252 including the assigned general identifier and the document type, document content, and update registration date / time included in the incident report data, and stores the incident general document data 252 in the general data storage unit 25. . Furthermore, the overall control unit 21 transmits the overall identifier in association with the incident identifier to the in-company management server 10. The in-company management server 10 records data related to the acquired general identifier in the general identifier data area of the incident attribute data 131 and the incident document data 132 including the incident identifier.

  On the other hand, when the incident attribute data 131 is not included, the incident information registration unit 212 searches the incident general document data 252 including the received incident identifier and document type.

  In this case, when the corresponding incident management document data 252 cannot be extracted, the incident information registration unit 212 includes the incident management including the incident identifier, the document type included in the received incident report data, the document content, and the update registration date and time. Document data 252 is generated and recorded in the overall data storage unit 25.

  On the other hand, when the corresponding incident general document data 252 can be extracted, the incident information registration unit 212 updates the data by recording the document content and the update registration date / time of the extracted incident general document data 252.

  Next, the overall control unit 21 of the overall management server 20 executes a determination process as to whether or not the support requirement is met (step S2-8). Specifically, the incident information registration unit 212 of the overall control unit 21 sets the value of each item of the registered incident overall attribute data 251 and the value of each item of the incident overall document data 252 to the response support requirement corresponding to this item. Compare with the value of each item recorded in the data requirement data area.

  Then, the overall control unit 21 of the overall management server 20 performs an alarm output process when the incident overall attribute data 251 and the incident overall document data 252 satisfy the condition of the corresponding requirement (in the case of “YES” in step S2-8). Is executed (step S2-9). Specifically, the response support processing unit 213 of the overall control unit 21 displays data related to the response content of the response support requirement data including the satisfied response requirement on the display of the client terminal. Thus, the incident report process ends.

(Wake-up call processing)
Next, a wake-up call process in which the overall management server 20 distributes incident information in response to a request from the in-company management server 10 will be described with reference to FIG. This wake-up call process is executed every day at the wake-up call time.

  Here, the control unit 11 of the in-house management server 10 executes the update data transmission request process when the current time becomes the wake-up call time (step S3-1). Specifically, the wake-up call processing unit 114 of the control unit 11 compares the current time with the wake-up call time stored in the connection data storage unit 12. The wake-up call processing unit 114 connects to the overall management server 20 via the connection unit 110 when the current time has passed the wake-up call time. And the incident report means 112 of the control part 11 transmits an update data transmission request. In this case, the connection unit 110 includes the organization code and DB number stored in the connection data storage unit 12 in the update data transmission request.

  The overall control unit 21 of the overall management server 20 that has received the update data transmission request executes a process for providing incident update information and contact information (step S3-2). Here, the overall control unit 21 provides incident data received from another in-company management server 10 from the previous time to the present time. Specifically, the information providing unit 214 of the overall control unit 21 controls the incident overall attribute data 251 with the date and time from the previous (yesterday) wake-up call time to the current (current day) wake-up call time as the registration date. Search is performed in the storage unit 25. When this incident general attribute data 251 is extracted, the information providing unit 214 includes the incident general attribute data 251 excluding the incident general attribute data 251 including the organization code and DB number included in the update data transmission request. Is identified.

Further, the information providing unit 214 extracts incident general document data 252 having the date and time from the previous morning call time to the current morning call time as the update registration date and time in the overall data storage unit 25. The information providing unit 214 extracts the incident general document data 252 that does not include the general identifier of the incident general attribute data 251 including the organization code and DB number included in the update data transmission request.

  Next, the information providing unit 214 extracts contact content data having the current date as the contact date from the contact data storage unit 24. Then, the information providing unit 214 transmits the extracted contact content data and the update providing data including the general identifier, the document type, and the document content of the extracted incident general document data 252 to the in-company management server 10. Further, when the incident general attribute data 251 can be specified, the information providing unit 214 includes data regarding the general identifier, the classification item, and the importance of the incident general attribute data 251 in the update provision data.

  Next, the control unit 11 of the in-company management server 10 executes an incident information update process and a contact information update process (step S3-3). Specifically, the wake-up call processing unit 114 of the overall control unit 21 temporarily records the communication content data of the update providing data in the memory of the control unit 11. Further, when the update providing data includes data relating to the incident identifier, the classification item, and the importance, the wake-up call processing means 114 generates incident attribute data 131 including these, and the incident data storage unit 13 To record. Furthermore, the wake-up call processing means 114 includes the current time at this time as the registered date and time in the incident attribute data 131.

  Then, the wake-up call processing unit 114 generates incident document data 132 including the general identifier and document type included in the update providing data, and records the incident document data 132 in the incident data storage unit 13. Furthermore, the wake-up call processing means 114 includes the current time at this time as the update registration date and time in the incident document data 132, and includes the access restriction of “none”. This completes the wake-up call process.

(Browsing process)
The in-house incident information manager browses the newly updated incident information. In this case, the client terminal acquires initial screen data from the in-company management server 10 and displays the initial screen on the display according to the operation of the administrator.

  Here, when the new arrival information browsing button on the initial screen is selected, the client terminal transmits a new arrival information acquisition request to the in-company management server 10. The control unit 11 of the in-company management server 10 extracts incident attribute data 131 having the current date or the previous day as the registration date. Furthermore, the control unit 11 extracts incident document data 132 having the current date or the previous day as the update registration date. The control unit 11 extracts only the incident document data 132 in which the access restriction flag is not recorded from the extracted incident document data 132. Further, contact content data temporarily recorded in the memory of the control unit 11 is extracted. And the control part 11 produces | generates the new arrival information browsing screen data containing the extracted incident attribute data 131 and incident document data 132, and contact content data, and transmits to a client terminal. The client terminal displays a new arrival information browsing screen on the display. The administrator can grasp the incident information and communication items registered from the client terminal in the other in-house management server 10 by browsing this new arrival information browsing screen. Thus, the browsing process ends.

According to this embodiment, the following effects can be obtained.
-In this embodiment, the control part 11 of the in-house management server 10 registers the incident information acquired from the client terminal (step S2-1), and there exists an original rule (in the case of "YES" in step S2-3) ) Executes a rule conversion process (step S2-4). Then, when executing the notification process (step S2-6), the control unit 11 of the in-house management server 10 converts the incident attribute data 131 into a local value instead of the local value. Include common values in report data. For this reason, the incident information obtained by converting the local value set based on the unique rule into the common value set based on the overall rule is transmitted to the overall management server 20. Therefore, the overall management server 20 can uniformly manage the incident information registered in each in-company management server 10 with different unique rules.

  -In this embodiment, the control part 11 of the management server 10 in a company compares the value of each item of report condition data with the common value after conversion, and satisfy | fills report conditions (in step S2-5 " In the case of “YES”, a notification process for transmitting the notification data to the overall management server 20 is executed (step S2-6). The overall control unit 21 of the overall management server 20 executes registration processing in the overall data storage unit 25 (step S2-7). Therefore, the overall management server 20 can acquire incident information from each in-company management server 10 according to a certain standard based on the overall rules. Therefore, even when there is no report instruction from each in-company management server 10 (in the case of “NO” in step S2-2), the overall management server 20 automatically outputs incident information that satisfies a preset notification condition. Can be acquired and managed.

  In this embodiment, the in-company management server 10 cannot write from external devices including the overall management server 20. When the current time is the wake-up call time, the control unit 11 of the in-house management server 10 executes update data transmission request processing (step S3-1). Upon receiving this update data transmission request, the overall control unit 21 of the overall management server 20 executes a process for providing incident update information (step S3-2), and the control unit 11 of the in-house management server 10 updates the incident information. And the update process of contact information is performed (step S3-3). Therefore, a client terminal connected to the in-house management server 10 can access the in-house management server 10 and acquire registered incident information without accessing the overall management server 20. . Accordingly, the load on the overall management server 20 can be reduced.

  In the present embodiment, in the connection setting process when the in-company management server 10 accesses the central management server 20 for the first time, the central control unit 21 of the central management server 20 executes a wake-up call time setting process (step S1-2). In this case, the overall control unit 21 extracts each wake-up call time from the call time data 230 recorded in the call time data storage unit 23. Then, the connection data determination processing unit 211 newly sets a time at which the processing load does not increase with respect to the already registered call time in a pre-stored time zone (in the present embodiment, 6:00 to 8:00). Determine the correct call time. For this reason, since the call time at which each in-company management server 10 accesses the overall management server 20 can be changed, the load when the overall management server 20 accesses the overall management server can be reduced.

Moreover, you may change the said embodiment as follows.
In the wake-up call process of the above embodiment, when the update providing data is acquired, the control unit 11 of the in-house management server 10 performs the incident information update process and the contact information update process (step S3-3). In this case, the setting value included in the update providing data may be converted into a setting value based on the unique rule, and the incident information update process may be executed using the converted value. Specifically, as shown in FIG. 7, when the current time is the wake-up call time, the control unit 11 of the in-house management server 10 performs the update data transmission request process in the same manner as in step S3-1. Execute (Step S4-1). Next, the overall control unit 21 of the overall management server 20 that has received the update data transmission request executes a process for providing incident update information and contact information in the same manner as in step S3-2 (step S4-2).

And the control part 11 of the management server 10 in a company judges whether there exists an original rule similarly to said step S2-3. Here, when there is a unique rule (in the case of “YES” in Step S4-3), the control unit 11 executes a conversion process based on this unique rule (Step S4-4). Specifically, the rule conversion unit 113 of the control unit 11 extracts correspondence data 140 including each value (common value) of the update providing data corresponding to each corresponding item identifier from the rule correspondence data storage unit 14. Then, the rule conversion unit 113 identifies the local value of the correspondence data 140 corresponding to each extracted common value, and stores it as the value of the incident attribute data 131. And the control part 11 of the management server 10 in a company performs the update process of incident information and the update process of contact information (step S4-5). In this case, if the item included in the update providing data includes a common value that can be converted using the correspondence data 140, the control unit 11 of the in-house management server 10 converts the converted local value into the incident attribute data 131. Can be stored as Therefore, an administrator who grasps incident information via a client terminal connected to the in-company management server 10 follows incident rules registered in other in-company management servers 10 according to his own rules. It can be grasped by setting value.

  In the wake-up call process of the above embodiment, in the correspondence data 140, the local value based on the unique rule and the common value based on the overall rule are associated with the corresponding item identifier. In this case, the correspondence data 140 may be data in which terms used in the organization are associated with terms used in the controlling company. Specifically, in the correspondence data 140, an identifier for identifying “term” is recorded as a correspondence item identifier, and an organization term used in the organization is associated with a common term used in the headquarters. The data is stored in the corresponding data storage unit 14. The control unit 11 of the in-company management server 10 may convert the term rules in the notification process (step S2-6). Specifically, when the notification process is performed, the rule conversion unit 113 of the control unit 11 compares the word / phrase of the document content included in the notification data with the organizational term of the identifier that identifies “term” as the corresponding item identifier. The common term of the corresponding data 140 including the matching phrase is extracted, and the document content replaced with this term is included in the notification data.

In the embodiment described above, the communication content notified to the in-company management server 10 is acquired by the overall management server 20 from the overall client terminal. Instead of this, the overall management server 20 may generate contact contents according to the incident information acquired from the in-company management server 10. For example, when a large number of similar incidents occur or when a serious incident occurs, a communication content that calls attention to this may be created. Specifically, contact creation data associating the contact content with the contact content generation condition for generating the contact content is stored in the overall management server 20. The contact content generation conditions include, for example, a plurality of keywords, keywords and the number of appearances, and the like. The overall control unit 21 of the overall management server 20 specifies the overall identifier of the incident information received from the in-house management server 10 within a predetermined period at a predetermined time before the time zone in which the wake-up call time is performed. . Specifically, the overall control unit 21 specifies the overall identifier of the incident information received from the previous day to the current day from the registration date and time of the incident overall attribute data 251. The overall control unit 21 specifies incident overall document data 252 including the specified overall identifier and the document type of “report”. The overall control unit 21 compares each document content of the identified incident overall document data 252 with the communication content generation condition. For example, when the contact content generation condition is a plurality of keywords, it is searched whether or not these keywords are included in each document content. Then, when there is the incident integrated document data 252 with the corresponding document content, the communication content associated with the communication content generation condition is specified. When the communication content generation condition is a keyword and the number of appearances, the overall control unit 21 counts the number of incident integrated document data 252 of the document content including the same keyword and compares it with the number of appearances. When the number of appearances is exceeded, the overall control unit 21 specifies the contact content associated with the contact content generation condition. Then, the overall control unit 21 includes data relating to the identified contact contents in the contact data having the current date as the contact date. As a result, the overall management server 20 can automatically generate contact information corresponding to the incident information acquired from the in-company management server 10 and provide it to the in-company management server 10.

Explanatory drawing explaining the structure of the system in embodiment. It is explanatory drawing explaining the data structure of the data storage part which an in-company management server has, (a) is a connection data storage part, (b) is an incident data storage part, (c) is a rule corresponding | compatible data storage part. It is explanatory drawing explaining the data structure of the data storage part which an integrated management server has, (a) is an organization management data storage part, (b) is a call time data storage part, (c) is an integrated data storage part. The flowchart for demonstrating the process sequence of a connection setting process. The flowchart for demonstrating the process sequence of incident report processing. The flowchart for demonstrating the process sequence of a wake-up call process. The flowchart for demonstrating the process sequence of the wake-up call process in the example of a change.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... In-company management server, 11 ... Control part, 12 ... Connection data storage part, 13 ... Incident data storage part, 14 ... Rule corresponding | compatible data storage part, 15 ... Notification condition data storage part, 20 ... General management server, 21 ... General control unit, 22 ... organization management data storage unit, 23 ... call time data storage unit, 24 ... contact data storage unit, 25 ... general data storage unit, 26 ... correspondence support requirement data storage unit, 110 ... connection means, 111 ... Setting processing means 112 ... Incident reporting means 113 ... Rule conversion means 114 ... Wake-up call processing means 120 ... Connection data 131 ... Incident attribute data 132 ... Incident document data 140 ... Corresponding data 210 ... Access handling processing Means 211... Connection data determination processing means 212. Incident information registration means 213. Response support processing unit, 214 ... information providing unit, 220 ... tissue management data 230 ... call time data, 251 ... incident overall attribute data, 252 ... incident overall document data.

Claims (5)

Incident data storage means for storing incident information;
A rule correspondence data storage means for storing correspondence information between the unique rule and the general rule, and a local server provided with a local control means connected to the client terminal;
An information management system having overall data storage means for storing incident information, and an overall management server provided with overall control means for connecting to the local server,
The local control means includes
When acquiring incident information from the client terminal, incident information recording means for recording this incident information as management registration information in the incident data storage means;
When the management registration information is recorded in the incident data storage means, the setting value set based on the unique rule included in the management registration information is used using the correspondence information in the rule correspondence data storage means. A reporting means for converting the setting information based on the overall rule and transmitting the management registration information including the converted incident information to the overall management server,
2. The information management system according to claim 1, wherein the overall control means comprises overall information recording means for storing the management registration information in the overall data storage means when the management registration information is acquired from the local server. The local control unit is connected to a report condition storage unit that stores a report condition for transmitting incident information to the overall management server,
The reporting means, after converting the setting value based on the overall rule, compares the converted setting value with the value of the notification condition, and if the converted setting value satisfies the notification condition, the management registration The information management system according to claim 1, wherein the information is transmitted to the overall management server. The local control means further includes an information updating means for making a transmission request for incident information to the overall management server at every predetermined call time and storing the incident information acquired in response thereto in the incident data storage means. ,
2. The information processing means according to claim 1, wherein the overall control means further comprises information distribution means for transmitting incident information recorded in the overall data storage means to the local server in response to a request from the local server. 2. The information management system according to 2.   When the incident information is acquired from the overall management server, the information update unit uses the correspondence information in the rule correspondence data storage unit to set a setting value based on the overall rule included in the incident information. 4. The information management system according to claim 3, wherein the incident information is converted into a set value based on the information and the converted incident information is stored in the incident data storage means. Incident data storage means for storing incident information;
A rule correspondence data storage means for storing correspondence information between the unique rule and the general rule, and a local server provided with a local control means connected to the client terminal;
An information management method in a system having overall data storage means for storing incident information, and an overall management server provided with overall control means for connecting to the local server,
The local control means;
When the incident information is acquired from the client terminal, the incident information recording step of recording the incident information as management registration information in the incident data storage means,
When the management registration information is recorded in the incident data storage means, the setting value set based on the unique rule included in the management registration information is used using the correspondence information in the rule correspondence data storage means. , Converting to a setting value based on the overall rule, and performing a reporting step of transmitting management registration information including the converted incident information to the overall management server,
When the management control information is acquired from the local server, the overall control means executes an overall information recording step of storing the management registration information in the overall data storage means.

Images