JP5350905B2 - Child acceptance facility risk management system, method and program thereof - Google Patents

Description

The present invention relates to a child reception facility risk management system, a method and a program thereof, and more particularly to a child reception facility risk management system, a method and a program for managing a risk that threatens child safety.

  The illness and death of children such as infants are steadily decreasing as medical technology advances. As morbidity and mortality due to illness have decreased, the proportion of injuries and deaths due to child accidents has increased, and the prevention of accidents has received increasing attention. In response to this trend, risk / safety management such as accidents and hygiene in the main facilities that accept infants and children, such as nurseries and kindergartens, has become the primary concern of parents. However, child safety and risk management in nursery schools and kindergartens depended on the experience and skills of child education and childcare professionals such as kindergarten teachers and nursery teachers, as well as the experience and skills of the institutional management group. Therefore, there is no established system for risk management or techniques for evaluating risk causes.

  On the other hand, there is an occupational health and safety management system OHSAS (Occupational Health and Safety Assessment Series) 18001 as a method for occupational health and safety management of workers in facilities and organizations. This is an occupational safety and health management system standard established by an international consortium in which various organizations (for example, Lloyd, SGS, and Japanese Standards Association) that have been certified on an international scale participated. As a technique for implementing such an occupational safety and health management system OHSAS18001, there is an “occupational safety and health management system, its method and program” invented by the present inventor (see Patent Document 1), and is in the public construction industry. Has been put to practical use.

JP 2006-059332 A

  The prior art occupational safety and health management system manages and evaluates risks such as injury to workers working at construction sites, and is not applicable to children such as infants and children in child reception facilities. In addition, children and infants have unique characteristics such as unexpected behavior and emotional instability, and there are many problems in risk (safety) management of children such as children and infants. For example, children often do not have enough physical strength, body, hands, intelligence, and mental development and growth, and as a result, there are equipment and facilities that have no problems when used by adults, with certain age groups and attributes It can be very dangerous for children. In addition, children are relatively safe when they are in an area where managers such as nursery teachers can reach, but there is a problem that the risk is extremely increased if they leave the area. The risk management of infants with various problems like this is ultimately dependent on the experience and skills of child education and childcare professionals such as kindergarten teachers and nursery teachers.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a child reception facility risk management system, a method and a program for easily managing and evaluating a child risk in a child reception facility.

In order to solve the above-mentioned problems, the child reception facility risk management system (device) according to the first invention is
A risk information master table that includes at least one event under management of the child acceptance facility (for example, an event / education unit (one frame) such as work, gymnastics, etc.) and at least one risk information associated with the event; A storage unit for storing;
An acquisition unit that acquires facility event data including at least one event (for example, educational units such as work and gymnastics, or timetables including these time units, or event units such as athletic meet, outdoor play, pool play, and excursions) When,
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk identifying unit that extracts risk information related to the facility event data; and
A risk output unit that outputs risk management data including risk information extracted by the risk identification unit;
It is characterized by having.
The child acceptance facility (or institution, corporation, group, company, organization, etc.) is a facility that provides education / childcare services to children such as infants and toddlers. For example, a nursery school, a nursery school, a kindergarten, an elementary school, a cram school, Junior high school, high school, free school, sports classes such as swimming and gymnastics.
The risk information includes, for example, chairs and desks that cause a stumbling as a danger source, floors that cause a fall, things that cause a collision, vehicles and carts that cause a hit, play equipment that causes a fall , Tools that cause cuts, children themselves, etc. Alternatively, as the risk information, information in which danger information including a hazard factor (danger source) and an accident type classification (occurrence state) for each event is defined may be used.
The facility event data is, for example, a timetable including educational units such as work and gymnastics, or an event unit such as athletic meet, outdoor play, pool play, and excursion.

The child acceptance facility risk management system according to the second invention is
The risk information included in the risk information master table includes risk evaluation data indicating the degree of influence of each risk information,
Risk output data including the degree of influence of each risk information (the severity of the result, the possibility of occurrence, the frequency of occurrence of actions that may cause the risk, and the overall risk evaluation value considering these) Output risk management data that further includes
It is characterized by that.

The child acceptance facility risk management system according to the third invention is
The facility event data is a timetable or event schedule in which a plurality of events are defined in time series,
The risk output unit outputs a timetable or event schedule including at least a part of the risk management data;
It is characterized by that.

The child acceptance facility risk management system according to the fourth invention is:
The risk information includes at least one facility information (large playground equipment, swing, slide, iron bar, climbing pole, pond, pool, garden, classroom, toilet, gym, gymnasium, playground, scissors, cutter, sword, etc. Tools, etc.), and accident occurrence status related to each facility information,
The risk identification unit
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, the accident event related to the at least one facility information and each facility information is considered and related to the facility event data Extracting risk information,
It is characterized by that.

A child acceptance facility risk management system according to the fifth invention is:
The storage unit further stores a management area master table describing at least one management area information;
The risk identification unit
With reference to the risk information master table and the management area master table, based on the facility event data acquired by the acquisition unit, considering the management area information, to extract the risk information related to the facility event data,
It is characterized by that.
Preferably, the risk identification unit is
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, to extract the risk information related to the facility event data,
With reference to the management area master table, at least a part of the risk information is changed based on the management area information.

The child acceptance facility risk management system according to the sixth invention is:
The storage unit
Entrance / exit information that describes at least one entrance / exit information (pool, facility garden (garden), classroom, nursery room, nursery room, toilet, entrance / exit of the entire facility, and traffic restrictions such as locks, bars and partitions) Store more master tables,
The risk identification unit
With reference to the risk information master table and the entrance / exit information master table, based on the facility event data acquired by the acquisition unit, considering the entrance / exit information, extract risk information related to the facility event data,
It is characterized by that.
Preferably, the risk identification unit is
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, to extract the risk information related to the facility event data,
With reference to the gateway information master table, at least part of the risk information is changed based on the gateway information.

The child acceptance facility risk management system according to the seventh invention is
The storage unit
Children describing child information including the number of children accepted by the child acceptance facility and / or attributes (age, nature, disease, constitution, degree of development, emotional stability, presence or absence of disability, gender, etc.) Store more information master tables,
The risk identification unit
With reference to the risk information master table and the child information master table, based on the facility event data acquired by the acquisition unit, considering the child information, to extract the risk information related to the facility event data,
It is characterized by that.
Preferably, the risk identification unit is
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, to extract the risk information related to the facility event data,
With reference to the child information master table, at least a part of the risk information is changed based on the number of children and / or attributes of the children.

The child acceptance facility risk management system according to the eighth invention is:
The acquisition unit further acquires, from a kindergarten information management server, child information describing child information including the number of children accepted by the child reception facility and / or attributes (preferably history information thereof),
The storage unit
From the child information acquired by the acquisition unit, build a child information master table in the storage unit,
The risk identification unit
With reference to the risk information master table and the child information master table, based on the facility event data acquired by the acquisition unit, considering the child information, to extract the risk information related to the facility event data,
It is characterized by that.

A child acceptance facility risk management system according to the ninth invention
The storage unit
A facility personnel master table describing facility personnel information including the number and / or attributes (age, experience, level of childcare / education skills, gender, etc.) of the child receiving facility personnel;
The risk identification unit
With reference to the risk information master table and the facility personnel master table, based on the facility event data acquired by the acquisition unit, considering the facility personnel information, to extract risk information related to the facility event data,
It is characterized by that.
Preferably, the risk identification unit is
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, to extract the risk information related to the facility event data,
With reference to the facility personnel master table, at least a part of the risk information is changed based on the facility personnel information.

The child acceptance facility risk management system according to the tenth invention is
The storage unit further stores a countermeasure information master table including at least one countermeasure information associated with each risk information and preventing or reducing at least a part of the risk information;
The child reception facility risk management system includes:
With reference to the countermeasure information master table, it further includes a case countermeasure identifying unit that identifies countermeasure information related to each risk information,
The risk output unit outputs risk assessment data further including identified countermeasure information that prevents or reduces at least a part of the extracted risk information;
It is characterized by that.

The child acceptance facility risk management system according to the eleventh invention is
The storage unit further stores a case information master table including at least one near-miss / accident case information associated with each risk information;
The child reception facility risk management system includes:
With reference to the case information master table, it further includes a case countermeasure identifying unit for identifying near-miss / accident case information (near-hat case information and / or accident case information) related to each risk information,
The risk output unit is
Output risk assessment data that further includes the extracted risk information and the identified near-miss case information.
It is characterized by that.

The child acceptance facility risk management system according to the twelfth invention is
The storage unit
Further storing a compliance information master table describing compliance information including at least one standard item to be complied with among laws, standards, and rules applicable to the child receiving facility;
The child reception facility risk management system includes:
With reference to the compliance information master table, further comprising a compliance determination unit that determines whether or not a standard item to be compliant is satisfied,
The risk output unit is
If the criteria item is not satisfied, output risk assessment data further including that,
It is characterized by that.
Preferably, the criterion items are ranked in severity, and the risk output unit outputs risk evaluation data including only the determination result of ranking having high severity.

  As described above, the solution of the present invention has been described as a system (apparatus). However, the present invention can also be realized as a method, a program, and a storage medium storing the program, which are substantially equivalent to these. It should be understood that these are included in the scope of the invention. Each step of the following methods and programs uses an arithmetic processing unit such as a CPU or DSP as needed for data processing. The input data, processed / generated data, etc. It is stored in a storage device such as an HDD or a memory.

For example, the child acceptance facility risk management method according to the thirteenth aspect of the present invention, which is realized as a method,
A risk information master table that includes at least one event under management of the child acceptance facility (for example, an event / education unit (one frame) such as work, gymnastics, etc.) and at least one risk information associated with the event; A storage step of storing in the storage means;
Facility event data including at least one event using a computing means (for example, an educational unit such as work or gymnastics, or a timetable including these time units, or an event unit such as an athletic meet, outdoor play, pool play, or excursion) ) Get step,
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk specifying step of extracting risk information related to the facility event data;
A risk output step of outputting risk management data including risk information extracted in the risk identification step;
It is characterized by having.

For example, a program for causing a computer to execute the child acceptance facility risk management method according to the fourteenth aspect of the present invention that realizes the present invention as a program,
A risk information master table that includes at least one event under management of the child acceptance facility (for example, an event / education unit (one frame) such as work, gymnastics, etc.) and at least one risk information associated with the event; A storage step of storing in the storage means;
Acquisition step of acquiring facility event data including at least one event (for example, an educational unit such as work or gymnastics, or a timetable including these time units, or an event unit such as an athletic meet, outdoor play, pool play, or excursion) When,
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk specifying step of extracting risk information related to the facility event data;
A risk output step of outputting risk management data including risk information extracted in the risk identification step;
It is characterized by having.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to manage and evaluate easily the risk which a child receives in a child acceptance facility.

FIG. 1 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to Embodiment 1 of the present invention. FIG. 2 is a diagram showing a risk information master table stored in the storage unit of the system shown in FIG. FIG. 3 is a flowchart showing an example of processing executed in the system shown in FIG. FIG. 4 is a diagram showing an example of facility event data acquired by the system shown in FIG. FIG. 5 is a diagram showing a timetable including risk management data output by the system shown in FIG. FIG. 6 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to the second embodiment of the present invention. FIG. 7 is a flowchart showing an example of processing executed in the system shown in FIG. FIG. 8 is a flowchart showing an example of processing executed by the system shown in FIG. FIG. 9 is a diagram showing a timetable including risk management data output by the system shown in FIG. FIG. 10 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to Embodiment 3 of the present invention. FIG. 11 is a flowchart illustrating an example of processing executed by the system illustrated in FIG. 12 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 13: is a block diagram which shows the outline | summary of the child acceptance facility risk management system (CAFRMS) by Embodiment 4 of this invention. FIG. 14 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. FIG. 15 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 16: is a block diagram which shows the outline | summary of the child acceptance facility risk management system (CAFRMS) by Embodiment 5 of this invention. FIG. 17 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. FIG. 18 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 19 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to Embodiment 6 of the present invention. FIG. 20 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. FIG. 21 is a diagram illustrating a part of the countermeasure information master table. FIG. 22 is a diagram illustrating a part of the case information master table. FIG. 23 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 24 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 25 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to the seventh embodiment of the present invention. FIG. 26 is a diagram illustrating a part of the compliance information master table. FIG. 27 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. FIG. 28 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. FIG. 29 is a diagram showing a part of the in-garden (caregiver) safety management sheet including the risk management data output on the screen by the system shown in FIG. FIG. 30 is a diagram showing a part of the safety management sheet for parents including the risk management data output on the screen by the system shown in FIG. FIG. 31 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to the eighth embodiment of the present invention. FIG. 32 is a flowchart illustrating an example of processing executed by the system illustrated in FIG.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<Embodiment 1>
FIG. 1 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to Embodiment 1 of the present invention. In this embodiment, the kindergarten which is a typical educational facility where infants attend is assumed as the child receiving facility. The same applies to the following embodiments. As shown in the figure, the child reception facility risk management system 100 includes a control unit (CPU) 110, an input unit 120, an output unit 130, a communication unit 140, a storage unit 150, and a display unit 160. The storage unit 150 includes at least one event (for example, an event / education unit (one frame) such as work, gymnastics, etc.) under the control of the child reception facility, and at least one risk information associated with the event. Stores a risk information master table RMT. The control unit 110 includes an acquisition unit 111, a risk identification unit 112, and a risk output unit 113. The acquisition unit 111 is a communication unit using a keyboard KBD connected to the input unit 120 or a facility management support server FMSS connected to the input unit 120 or a terminal PC1 connected to the server FMSS. Via 140, facility event data including at least one event (eg, educational units such as work, gymnastics, or timetables including these time units, or event units such as athletic events, outdoor play, pool play, excursions) To get. The acquisition unit 111 may acquire facility event data from the terminal PC2, the mobile terminal PDA1, and the mobile phone terminal MS1. The risk identifying unit 112 refers to the risk information master table RMT and extracts risk information related to the facility event data based on the facility event data acquired by the acquiring unit 111. The extracted risk information is stored in the storage unit 150 as intermediate data. The risk output unit 113 outputs risk management data including risk information extracted by the risk specifying unit 112 via the output unit 130. The risk output unit 113 may display (output) the risk management data on the display unit 160. Alternatively, the risk output unit 113 may output the risk management data to the external devices such as the terminal PC2, the mobile terminal PDA1, and the mobile phone terminal MS1 via the communication unit 140, and display them on these terminals. In this way, the generated information and intermediate data and acquired data are transmitted to the outside, displayed on the display unit, and the generated information and intermediate data and acquired data are stored in the storage unit. It should be noted that other actual modes described later are possible as well. The child reception facility risk management system 100 is a computer such as a general-purpose computer, a special-purpose computer, a server, or a PC, or a functional unit and a processing procedure (method) of the system are realized (executed) on the computer. It is preferable to build a child acceptance facility risk management system on the computer by holding the program module to be stored in the CPU or storage unit of the computer or by reading it from an external server or storage. The same applies to the embodiment.

  FIG. 2 is a diagram showing a risk information master table stored in the storage unit of the system shown in FIG. As shown in the figure, the risk information master table RMT includes at least one event EV under the management of the child reception facility, and at least one risk information RI associated with the event. The event R1e is a “craft” that is one frame of a childcare service performed in a kindergarten or a nursery school, and a plurality of risk information related to the event “craft” is associated with this event. The risk information associated with the work includes, for example, a risk information element R11r. This includes the danger source “scissors for infants”, risk occurrence status (accident occurrence status) “cutting hands”, and possible risk factors “carelessness, lack of guidance from facilities and parents” Yes. Furthermore, risk assessment data / risk impact is associated with each event. More specifically, each risk information element is associated with a risk evaluation data element. For example, a risk evaluation data element R11i is associated with the risk information element R11r. The risk evaluation data element R11i includes the risk severity 3, the possibility of an accident (risk) 2 occurring, the frequency 3 of the work involving risk, the evaluation value = 18 (severity x possibility x frequency), the rank = C (AA for evaluation value 100 or more, 50 = <A <100, 30 = <B <50, 10 = <C <30, D for less than 10 is described). Similarly, the event R2e is “outside play”, and is associated with a risk information element R21r and the like. In the risk information element R21r, a danger source “slide”, a risk occurrence state “a fracture due to a drop”, and a risk occurrence factor “carelessness, insufficient guidance” are described. The system extracts (identifies) the most appropriate risk information element from this table based on the acquired information (facility event data), and preferably further extracts risk assessment data elements corresponding to the extracted risk information element (Identify. As will be described in detail later, more detailed information or additional information of the event is acquired by the acquisition unit, or the risk information master table RMT is customized (modified) to correspond to the facility environment. Therefore, it is possible to appropriately evaluate the risk at the time of providing the education service / childcare service at the facility. When detailed data or a customized table cannot be prepared, it is preferable to use, as risk assessment data, risk assessment comprehensive data R1iT, which is an overall (average) risk assessment of the risk information (that is, the event). It is. The total or average value of each item of the risk evaluation data element can be described in the risk evaluation comprehensive data R1iT. In the case of event R1e (craft), the total evaluation value of risk is 55, the average evaluation value (ave) is 11, and the rank indicating the risk (influence) of the event is A. Similarly, in the event R2e (outside play), the risk evaluation value total 69, the evaluation value average (ave) is 17, and the rank indicating the risk (impact) is A.

  FIG. 3 is a flowchart showing an example of processing executed in the system shown in FIG. It is assumed that various data (for example, risk information master table RMT) required in advance are stored in the storage unit 150. As shown in the figure, in step S11, the acquisition unit 111 acquires facility event data including at least one event. Next, in step S12, the risk specifying unit 112 refers to the risk information master table RMT, and extracts risk information related to the facility event data based on the facility event data acquired in step S11. Subsequently, in step S <b> 13, the risk output unit 113 outputs risk management data including risk information extracted by the risk specifying unit 112 to the display unit 160. When there are a plurality of events included in the facility event data (for example, when timetable information is acquired), step S12 is repeated by the number of events.

  FIG. 4 is a diagram showing an example of facility event data acquired by the system shown in FIG. For facility event data, it is possible to use various types of information such as event schedules and daily action tables, but timetables in which multiple events are defined in time series can be used as acquired data as they are. Therefore, it is preferable to use timetable information. As shown in the figure, the facility event data in this example is a kindergarten timetable TTB in which a plurality of events are defined in time series. The present system can appropriately perform risk assessment by acquiring such a rough timetable as facility event data and using the risk information master table RMT shown in FIG.

  FIG. 5 is a diagram showing a timetable including risk management data output by the system shown in FIG. For convenience of drawing, the part after Thursday is omitted. The timetable TTB1 shown in FIG. 5 uses the information of the timetable TTB of FIG. 4 as input data, identifies and extracts risk information with reference to the risk information master table RMT shown in FIG. Edited and output in the format included in the timetable. As shown in FIG. 5, in the morning Moma on Monday, the risk information of the event (childcare / education unit) “work” to be held at the facility “risk source element, occurrence status, generation factor, risk evaluation value (critical) , Possibility, frequency, evaluation value, risk rank). Similarly, a frame M2 for lunch on Monday, a frame M3 for outdoor play on Monday, a frame M4 for park play on Tuesday, a song frame M5 for Wednesday morning, and the like are displayed. For convenience of drawing and explanation, although not shown in FIG. 2, data such as “park play”, “song”, “lunch”, etc. are held in the risk information master table RMT as events. Incidentally, in the example of FIG. 5, since there is no event corresponding to the event “Tanabata Production” in the risk information master table RMT, risk management data cannot be output for the event, but in such an inconvenient case. A corresponding technique is described in embodiment 2. As described above, according to the present embodiment, if it is a child acceptance facility, it is possible to simply output appropriate risk management information simply by diverting “timetable information” prepared at most facilities, It will be possible to properly manage and evaluate children's risks in facility operation.

<Embodiment 2>
FIG. 6 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to the second embodiment of the present invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 200 includes a control unit (CPU) 210, an input unit 220, an output unit 230, a communication unit 240, a storage unit 250, and a display unit 260. Have The control unit 210 includes an acquisition unit 211, a risk identification unit 212, a risk output unit 213, and a morpheme analysis unit 214. The CAFRMS 200 in FIG. 6 has substantially the same configuration and function as the CAFRMS 100 shown in FIG. 1, and functional units having the same names as those in FIG. 1 should be understood to have the same functions unless otherwise specified. . In this embodiment, the morphological analysis unit 214 newly provided in the control unit 210 is different from the management area master table MR and synonym dictionary data SDD newly included in the storage unit 250. The management area master table MR is information (area is defined as “management area information”) of the area (the area is defined as “management area”) in which the child receiving facility provides education / childcare services to the child. Is described. In the present embodiment, the risk identification unit 212 refers to the risk information master table RMT and the management area master table MR, and takes into account the management area information based on the facility event data acquired by the acquisition section 211, and the facility event data Extract risk information related to.

  When the risk information cannot be extracted only by the acquired “raw text data of the event” (that is, when there is no item corresponding to [event] described in the text data), the morphological analysis unit 214 extracts the word from the text data. cut. Specifically, the morphological analysis unit 214 cuts out some words from text data indicating an event included in the facility event data. The risk identification unit 212 calls the synonym dictionary data SDD, and extracts synonyms and synonyms corresponding to the words cut out by the morphological analysis unit 214 from the text data. The risk specifying unit 212 replaces the event with the extracted synonym and synonym, and refers to the risk information master table RMT and the management area master table MR again, and includes “an event replaced with a synonym and synonym”. Based on the facility event data, risk information related to the facility event data is extracted in consideration of the management area information. With this configuration, it is possible to appropriately evaluate and manage risk information in response to fluctuations in the expression of the facility manager describing the event and various expressions and descriptions.

The management area information described in the management area master table MR is illustrated.
[Management Area] | [Management Area Information] | [Event Association]
Classroom ｜ Management level: High, regular management ｜ Work, lunch, song nursery school ｜ Management level: High, regular management ｜ Gymnastics, physical education, event toilet ｜ Management level: Medium and regular management ｜ Auditorium during events ｜ Management Level: High, regular management ｜ Event garden ｜ Management level: Medium, regular management ｜ Outdoor playground (inside the park) ｜ Management level: Medium, regular management ｜ Athletic field practice (inside the park)
Ground (outside of the park) ｜ Management level: low, out of management ｜ Athletic meet practice (athletic meet facility)
Park (outside of the park) ｜ Management level: Low, unmanaged ｜ External facilities for park play (museums, etc.) ｜ Management level: Low, unmanaged ｜ External facility tour

  When the management area master table MR including the management area information as described above is used as the basic data for risk management evaluation, it becomes possible to perform risk evaluation and management more appropriately. Especially for infants in kindergarten and nursery school where safety management is significantly reduced, such as when they are unable to defend themselves against suspicious individuals and there is no person to supervise, they immediately start running toward what they are interested in. In this case, there are appropriate managers (kindergarten teachers, nursery teachers, etc.) “closed spaces of appropriate size in the facility” (typically “classrooms with teachers who are specialists in childcare and education”). Then the risk is greatly reduced. Even if it is not a closed space, it can be said that the gardens and auditoriums in the facility are significantly less risky than outside the facility due to the placement of teachers and guards at the entrance and entrance of the main gate etc. . The management area master table MR makes it possible to more appropriately evaluate and manage a child's risk based on the newly introduced concept of “management area”. For example, when the management level is “high”, “medium”, “low”, the risk evaluation values are weighted numerical values (coefficients) such as “1.0”, “1.2”, “1.5”, etc. assign. The risk evaluation value of each identified and extracted event is multiplied by a “weighting value” having a corresponding event association, and the result of the multiplication can be used as a risk evaluation value for more appropriate risk evaluation. It becomes possible.

  FIG. 7 is a flowchart showing an example of processing executed in the system shown in FIG. Note that although it is assumed that various data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, etc.) necessary in advance are stored in the storage unit 250, this flowchart. Then, the management area master table MR is not used (an example in which MR is used will be described later with reference to FIG. 8). As shown in the figure, in step S21, the acquisition unit 211 acquires facility event data including at least one event. Next, in step S22, the risk identification unit 212 refers to the risk information master table RMT and tries to extract risk information related to the facility event data based on the facility event data. Subsequently, in step S23, the risk identification unit 212 determines whether risk information has been extracted. If it is determined that the risk information cannot be extracted, in step S24, the risk identification unit 212 performs a morphological analysis on the event included in the facility event data, cuts out a word, and extracts the event with a synonym or synonym of the word. The process proceeds to step S22. Finally, in step S27, the risk output unit 113 outputs risk management data including risk information extracted by the risk specifying unit 112 to the display unit 160. When there are a plurality of events included in the facility event data (for example, when timetable information is acquired), steps S22 and S23 (S24 in some cases) are repeated by the number of events.

  FIG. 8 is a flowchart showing an example of processing executed by the system shown in FIG. Note that it is assumed that the storage unit 250 stores various pieces of necessary data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, etc.). In this flowchart, more appropriate risk evaluation / management is performed using the management area master table MR. Steps S21 to S24 and S27 in FIG. 8 are the same processes as those in FIG. 7 and will not be described. Only steps S25 and S26 which are different steps will be described. In step S25, the risk specifying unit 212 refers to the management area master table MR, searches for management area information of an item corresponding to the event, and specifies a weighting value for the management area information. In step S26, the risk specifying unit 212 multiplies each numerical value of the risk information extracted in step S22 by the “weighting numerical value” specified in step S25, and replaces each numerical value with the calculation result. Finally, in step S27, the risk output unit 213 outputs risk management data including risk information extracted by the risk specifying unit 212 to the display unit 260. The steps corresponding to the number of events are repeated as in the process of FIG.

  FIG. 9 is a diagram showing a timetable including risk management data output by the system shown in FIG. That is, the evaluation value is customized according to the management area in which the event is executed, and the risk management data of the event “Tanabata Production” that cannot be evaluated because the corresponding event is not in the storage unit is output. . For convenience of drawing, the part after Thursday is omitted. The timetable TTB2 shown in FIG. 5 uses the information of the timetable TTB in FIG. 4 as input data, identifies and extracts risk information with reference to the risk information master table RMT shown in FIG. Edited and output in the included format. As shown in FIG. 9, since the frames M21, M22, M25, and the like are educational units performed in a classroom that is considered to be a safe facility area that is relatively well managed, the weighting value is 1. Evaluation values similar to those of the corresponding frames M1, M2 and M5 are described. The “outside event play” of the top M23 is an educational unit performed in the open area “garden”, so the management level is “medium” and the weighting value is 1.2. Each evaluation value is replaced with a value multiplied by 2. In addition, “event park play” of the top M24 is an educational unit performed in an unmanaged open area “park” outside the facility, so the management level is low, and the weighting value is 1.5. Each evaluation value is replaced with a numerical value obtained by multiplying each extracted evaluation value by 1.5. As described above, in this embodiment, by introducing the concept of the management area, it is possible to more appropriately evaluate and manage the risk of the child.

  Further, since the event name corresponding to the event “Tanabata production” of the frame M26 does not exist in the table RMT, the morphological analysis unit 214 extracts the word “production” from the text “Tanabata production”. Since the synonym dictionary data has an entry “synonym for production = craft”, the synonym dictionary data SDD is used to extract the “skill” synonym of “production” and appropriately identify the risk management information of top M26. It is possible to extract. This is the same for other events. For example, in the synonym dictionary data, if there is an entry of “music, synonym of musical instrument = song”, the risk management data of the music related event is output appropriately, Music-related educational units can be properly risk-managed and managed. As described above, according to this embodiment, if the facility is a child acceptance facility, it is possible to simply output the appropriate risk management information for the timetable simply by diverting the “timetable information” prepared at most facilities. It is possible to appropriately manage and evaluate the risks of children in facility operation. The storage unit 250 of FIG. 6 includes synonym and synonym dictionary data SDD including synonym words and idioms, and the control unit 210 further includes a morpheme analysis unit 214 that can extract words. Yes. When there is no item whose event included in the acquired facility event data matches the risk information master table RMT, the system 200 (more specifically, the risk specifying unit 212) calls the synonym dictionary data, and synonyms and synonyms. , And the risk information master table RMT is referenced to search for a match with these synonyms and synonyms. With this configuration, it is possible to output risk management data for most events without being affected by fluctuations in notation such as a timetable and various expressions and descriptions.

<Embodiment 3>
FIG. 10 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to Embodiment 3 of the present invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 300 includes a control unit (CPU) 310, an input unit 320, an output unit 330, a communication unit 340, a storage unit 350, and a display unit 360. Have The control unit 310 includes an acquisition unit 311, a risk identification unit 312, a risk output unit 313, and a morpheme analysis unit 314. The CAFRMS 300 in FIG. 10 has substantially the same configuration and function as the CAFRMS 100 and 200 shown in FIGS. 1 and 6, and functional units having the same names as those in FIGS. 1 and 6 are the same unless otherwise specified. It should be understood as having a function. In this embodiment, the function of the risk specifying unit 312 provided in the control unit 310 is different from the entrance / exit information master table DW newly included in the storage unit 350. The entrance / exit information master table DW means at least one entrance / exit information (pool, facility garden (garden), classroom, nursery room, child room, toilet, facility, etc.) in the facility where the child receiving facility provides education / childcare services to children. Entry / exit and the status of traffic restrictions such as locks, bars and partitions). The risk specifying unit 312 refers to the risk information master table RMT and the entrance / exit information master table DW, and considers the entrance / exit information based on the facility event data acquired by the acquisition unit 311 to obtain risk information related to the facility event data. Extract. Specifically, the risk specifying unit 312 refers to the risk information master table RMT, extracts risk information related to the facility event data based on the facility event data acquired by the acquiring unit 311, and performs the entrance / exit information master table DW. Referring to FIG. 4, at least a part of the risk information is changed based on the entrance / exit information. In order to extract risk information in consideration of “entrance / exit information” described in the entrance / exit information master table DW, the risk information provided for each event is further subdivided according to the contents of “entrance / exit information”. can do. However, in this case, it is necessary to set the risk information items in a number corresponding to “type of event” × “type of entrance / exit information”, and it takes a relatively long time to prepare a premise table. As a simple method for solving this, there is a technique in which risk information is extracted once according to each event, and each numerical value included in the risk information is multiplied by a weighting numerical value corresponding to “entrance / exit information”. . This makes it possible to easily reflect the factors of the entrance / exit information in the risk information. In the present embodiment, the latter simple method will be specifically described.

The entrance / exit information described in the entrance / exit information master table DW is illustrated.
[Target location] ｜ [Exit information] ｜ [Event association]
The whole facility ｜ There is a boundary, entrance / exit management by guards ｜ Crafts, lunch boxes, singing classrooms ｜ There are boundaries, entrance / exit management by teachers ｜ Crafts, bento boxes, song nursery school , Event toilet ｜ There is no boundary, no entrance / exit management ｜ Audience hall during the event ｜ There is a boundary, entrance / exit management by the teacher ｜ Event garden ｜ There is a boundary, entrance / exit management by the teacher | ｜ Athletic meet practice park (outside of the park) ｜ No borders, no entrance / exit management ｜ Park play facilities (museums, etc.) ｜ There are borders, no entrance / exit management

  When the entrance / exit information master table DW including the entrance / exit information as described above is used as risk management evaluation basic data, it becomes possible to perform risk assessment / management more appropriately. In particular, the kindergarten where safety is significantly reduced, such as being unable to defend against suspicious persons entering from the entrance and exiting on their own, if they are unable to defend themselves and there is no supervisor, In the case of an infant at a nursery school, the risk is greatly reduced in a space (typically "kindergarten or nursery school with access control by guards") controlled by appropriate managers (kindergarten teachers, nursery teachers, etc.) Is done. In order to enter the area, classrooms in the facility go through the “classroom entrance” and receive entrance / exit management by the teacher. Therefore, in order to get in and out of the park, it is necessary to pass through a two-stage gate such as “gate to the facility guarded by the guard” and “gate to the classroom managed by the teacher”. It can be considered that the “classroom” is the safest and most well managed. The weighting value is 0.8. Next, it is necessary to pass through the "gate to the facility guarded by the guard", and the place other than the space where the gate such as the classroom is located in the entire facility (inside the park) is relatively safe and managed. You may think it is perfect. Let this weighting value be 1.

  “Park (outside of the park)” is a public space where there are many places that do not have boundaries, and entrance / exit management is not performed at gates or the like, and third parties and suspicious persons may approach. There is also a risk that the infant may deviate from the permitted range. However, general parks have many open spaces and are relatively easy for teachers to reach. Taking this into consideration, the weighting value is set to 1.2. “External facilities (museums, etc.)” have boundaries, and entry / exit management is performed by third parties at gates, etc., but entry / exit management by teachers at the kindergarten side is not possible. In addition, the external facilities are large spaces with many blind spots, and there is a high risk that the infant will deviate from the reach of the teacher's eyes. Considering this, the weighting value is set to 1.5. The entrance / exit information master table DW makes it possible to more appropriately evaluate and manage the risk of children based on the newly introduced concept of “entrance / exit information”.

  FIG. 11 is a flowchart illustrating an example of processing executed by the system illustrated in FIG. It is assumed that various data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, entrance / exit information master table DW, etc.) necessary in advance are stored in the storage unit 350. . In this flowchart, more appropriate risk evaluation / management is performed using the entrance / exit information master table DW. Steps S31 to S34 and S37 in FIG. 11 are the same processes as those in FIG. 8 and will not be described. Only steps S35 and S36 which are different steps will be described. In step S35, the risk specifying unit 312 refers to the entrance / exit information master table DW, searches for entrance / exit information of an item corresponding to the event, and specifies a weighting value of the entrance / exit information. In step S36, the risk specifying unit 312 multiplies each numerical value of the risk information extracted in step S32 by the “weighting numerical value” specified in step S35, and replaces each original numerical value with the calculation result. Finally, in step S <b> 37, the risk output unit 313 outputs risk management data including risk information extracted by the risk specifying unit 312 and reflecting the child information with a weighted numerical value to the display unit 360. The steps corresponding to the number of events are repeated as in the process of FIG. If the processes in steps S25 and S26 of FIG. 8 described in the second embodiment are performed in parallel, more appropriate risk evaluation / management reflecting the management area information can be performed.

  12 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M31 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The frame M32 multiplies the numerical value portion (risk evaluation value) of the “risk information” displayed on the frame M31 by the “weighting value” of the gateway information identified with reference to the “gateway information master table DW”. It is output as one frame of the timetable. As described above, according to this configuration, it is possible to perform more appropriate risk evaluation / management using not only the facility event data but also the entrance / exit information.

<Embodiment 4>
FIG. 13: is a block diagram which shows the outline | summary of the child acceptance facility risk management system (CAFRMS) by Embodiment 4 of this invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 400 includes a control unit (CPU) 410, an input unit 420, an output unit 430, a communication unit 440, a storage unit 450, and a display unit 460. Have The control unit 410 includes an acquisition unit 411, a risk identification unit 412, a risk output unit 413, and a morpheme analysis unit 414. The CAFRMS 400 in FIG. 13 has substantially the same configuration and function as the CAFRMS 100, 200, and 300 shown in FIGS. 1, 6, and 10, and has the same name as those in FIGS. Unless otherwise stated, it should be understood that the parts have similar functions. In this embodiment, the function of the risk specifying unit 412 provided in the control unit 410 and the child information master table CI newly included in the storage unit 450 are different. The child information master table CI is the number and / or attributes (age, nature, chronicity, constitution, degree of development, emotional stability, presence or absence of disability, gender, etc.) It describes child information including. The risk specifying unit 412 refers to the risk information master table RMT and the child information master table CI, and based on the facility event data acquired by the acquiring unit 411, considers the child information and displays risk information related to the facility event data. Extract. In order to extract risk information in consideration of the “child information” described in the child information master table CI, the risk information provided for each event is further subdivided according to the content of the “child information”. can do. However, in this case, it is necessary to set the risk information items by the number corresponding to “type of event” × “type of child information”, and it takes a relatively long time to prepare a premise table. As a simple method for solving this, there is a technique in which risk information is extracted once according to an event, and each numerical value included in the risk information is multiplied by a “weighting numerical value” corresponding to the child information. This makes it possible to easily reflect the factor of the child information in the risk information. In the present embodiment, the latter simple method will be specifically described.

The child information described in the child information master table CI is illustrated.
[Child Information Item] | [Weighting Value] | [Event Association] | [Mask]
Number of children over 500 ｜ 1.3 ｜ All events ｜ * (Disabled)
Number of children 250 and under 500 | 1.2 | All events | * (Disabled)
Number of children 100 and under 250 | 1.1 | All events | (valid)
Number of children 50 to less than 100 ｜ 1.0 ｜ All events ｜ * (Disabled)
Age 0-3 years old ｜ 1.5 ｜ All Events ｜ * (Disabled)
Age 4-6 years old ｜ 1.1 ｜ All events ｜ (valid)
Age 7-9 years old ｜ 1.0 ｜ All Events ｜ * (Disabled)
Age over 10 ｜ 0.8 ｜ All Events ｜ * (Disabled)
Child with chronic illness (degree: heavy) | 1.3 | All events | * (Invalid)
Child with chronic disease (degree: medium) | 1.2 | All events | * (invalid)
Child with chronic illness (degree: light) | 1.1 | All events | * (Invalid)
Children who need special care ｜ 1.5 ｜ Park play ｜ (valid)
Children who need special care ｜ 1.2 ｜ Events other than park play ｜ * (Invalid)
Child with food allergy ｜ 1.2 ｜ Lunch ｜ (Effective)

  Each item has its weighting value set as described above, taking into account its impact on the risk, but the user resets (changes) it to an arbitrary value in consideration of the situation of children at each facility ( Customization). As described above, when the child information master table CI including child information is used as basic risk management evaluation data, it is possible to more appropriately perform risk evaluation and management in consideration of the number and attributes of children. As described above, the user can enter “asterisk *” in the “mask field” to invalidate the item and exclude it from the search target of the risk specifying unit 412 so as to make it invisible. In such exclusive selection processing, a radio button is used to form one selection group with a plurality of items, and by selecting one of the radio buttons, the corresponding item is enabled and other items are disabled. It is preferable to employ an interface that allows automatic selection processing. On the contrary, an item whose “mask field” is blank is valid and becomes a search target of the risk identification unit 412. In the above child information example, the number of children is 100 or more and less than 250, the age is 3-6 years old, the child who needs special care, the child with food allergy is effective, and in the case of the applicable event, the weighting of each Multiply the risk assessment value by a numerical value. The child information master table CI may be created by manually inputting the above-mentioned table. For example, as child data preliminary data to be described in the child information master table CI, information on each infant (allergy information, etc.) is provided. The child information master table CI can be constructed by storing in the storage unit or reading from another child information database (not shown) and using the statistical information.

As described above, the weighting values of the child information (age, number of children, etc.) related to all events are reflected in the evaluation values of all events. The specific calculation in this case is as follows.
Evaluation value of the event “craft” considering child information = evaluation value of the event “craft” × (weight number of children 100 to less than 250 [1.1]) × (weight value of children aged 4-6 years [1] .1])
The weighting value of the item of food allergy is reflected only in the event “Lunch”. The specific calculation in this case is as follows.
Evaluation value of event “Lunch” considering child information = Evaluation value of event “Lunch” × (Weighted number of children from 100 to less than 250 [1.1]) × (Weighted number of children aged 4-6 years [1 .1]) x (weighting value for children with food allergies [1.2])

  FIG. 14 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. The storage unit 450 stores various necessary data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, entrance / exit information master table DW, child information master table CI). It is assumed that In this flowchart, more appropriate risk evaluation / management is performed using the child information master table CI. Steps S41 to S44 and S47 in FIG. 14 are the same processes as those in FIG. 11 and will not be described. Only steps S45 and S46, which are different steps, will be described. In step S45, the risk specifying unit 412 refers to the child information master table CI, searches for child information of an item corresponding to the event, and specifies a weighting value (a plurality may exist) of the child information. To do. In step S46, the risk specifying unit 412 multiplies each numerical value of the risk information extracted in step S42 by the “weighted numerical value” specified in step S45, and replaces the original numerical value with the calculation result. Finally, in step S47, the risk output unit 413 outputs risk management data including risk information extracted by the risk specifying unit 412 and reflecting the child information with the weighted numerical value to the display unit 460. The steps corresponding to the number of events are repeated in the same manner as the processing in FIGS. If the processes in steps S25 and S26 of FIG. 8 described in the second embodiment are performed in parallel, more appropriate risk evaluation / management reflecting the management area information can be performed. Further, if the processes of steps S35 and S36 of FIG. 11 described in the third embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the entrance / exit information.

  FIG. 15 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M41 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The frame M42 multiplies the numerical value part (risk evaluation value) of the “risk information” displayed on the frame M41 by the “weighting numerical values” of a plurality of pieces of child information specified with reference to the “child information master table CI”. The result is output as one frame of the timetable. As described above, according to this configuration, it is possible to perform more appropriate risk assessment / management using not only the facility event data but also child information having various attributes.

  The child information master table CI is the number of children accepted by the child acceptance facility, its attributes, such as age, nature, prevalence of allergic diseases, constitution, development, emotional stability, presence or absence of disability, its degree, gender, etc. In addition, the number of children having each attribute and the history information thereof may be included, but the overall personal information of each child may be configured in a comprehensive format. For example, the age of each child, health checkup results, gender, constitution, degree of development, emotional stability, presence or absence of disability, and the degree of all these history information (when numerical values or contents of items are changed, added, deleted The “total child information” describing the time and the like (detailed contents thereof) is stored in the child information master table CI. Then, “statistical information” in a form suitable for use in the present system as described in “paragraph 0045” is extracted by a statistical method from “general child information” stored in the child information master table CI. It is preferable to use it as reference data for the risk identification unit 412 (described in detail later as Embodiment 8). Maintaining detailed and comprehensive child information and history information in this way will contribute to the analysis of the subsequent risk assessment in the event of an accident or near-miss incident.

<Embodiment 5>
FIG. 16: is a block diagram which shows the outline | summary of the child acceptance facility risk management system (CAFRMS) by Embodiment 5 of this invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 500 includes a control unit (CPU) 510, an input unit 520, an output unit 530, a communication unit 540, a storage unit 550, and a display unit 560. Have The control unit 510 includes an acquisition unit 511, a risk identification unit 512, a risk output unit 513, and a morpheme analysis unit 514. The CAFRMS 500 in FIG. 16 has substantially the same configuration and function as the CAFRMS 100, 200, 300, and 400 shown in FIGS. 1, 6, 10, and 13, and FIGS. It should be understood that functional parts having names similar to those have similar functions unless otherwise specified. In the present embodiment, the function of the risk specifying unit 512 provided in the control unit 510 is different from the facility personnel master table HRI newly included in the storage unit 550. Facility Personnel Master Table HRI is a person who provides services such as education, childcare, and meals to children at child reception facilities (typically, kindergarten teachers, elementary school teachers, childcare staff, school lunch staff, nursing staff) Etc.) and / or facility personnel information including attributes (age, experience, level of childcare / education skills, gender, etc.). The risk identifying unit 512 refers to the risk information master table RMT and the facility personnel master table HRI, and takes into account facility personnel information based on the facility event data acquired by the acquiring unit 511, and the risk information related to the facility event data To extract. In order to extract risk information in consideration of “facility personnel information” described in the facility personnel master table HRI, the risk information provided for each event is further subdivided according to the contents of the “facility personnel information”. Can respond. However, in this case, it is necessary to set the risk information items in the number corresponding to “type of event” x “type of facility personnel information”, and it is relatively troublesome to prepare and construct the prerequisite table. It takes. As a simple method for solving this, there is a method in which risk information is extracted once according to an event, and each numerical value included in the risk information is multiplied by a weighting numerical value corresponding to facility personnel information. As a result, the factor of the facility personnel information can be easily reflected in the risk information. In the present embodiment, the latter simple method will be specifically described.

The facility personnel information described in the facility personnel master table HRI is illustrated.
[Facility Personnel Information Item] | [Weighting Value] | [Event Association] | [Mask]
More than 10 years of experience 50% or more ｜ 0.7 ｜ All Events ｜ * (Disabled)
Over 5 years experience 50% or more ｜ 1.0 ｜ All events ｜ (valid)
Less than 3 years of experience 50% or more ｜ 1.3 ｜ All Events ｜ * (Invalid)
Less than 10 children per teacher ｜ 0.8 ｜ All Events ｜ * (Disabled)
Number of children per teacher 10 or more and less than 25 | 1.1 | All Events | (Valid)
Over 25 children per teacher ｜ 1.2 ｜ All Events ｜ * (Disabled)
Teacher with more than 10 years of experience ｜ 0.8 ｜ Gymnastics ｜ (Valid)
Teacher with less than 2 years of experience ｜ 1.2 ｜ Music ｜ (valid)
Cooking staff with less than 2 years of experience ｜ 1.2 ｜ Lunch ｜ (Effective)

  Each item has its weighting value set as described above, taking into account its impact on the risk, but the user should reset it to any value in consideration of the situation of the personnel at each facility (customization) Is possible. As described above, when the facility personnel master table HRI including facility personnel information is used as basic data for risk management evaluation, it is possible to perform more appropriate risk evaluation and management in consideration of the number and attributes of facility personnel. As described above, the user can enter “asterisk *” in the “mask field” to invalidate the item and exclude it from the search target of the risk identification unit 512 to make it invisible. On the contrary, an item whose “mask field” is blank is valid and is a search target of the risk identification unit 512. In the above example of facility personnel information, the items of more than 50% experience, 50% or more, number of children per teacher 10 to less than 25, experience 10 years or more, less than 2 years experience, less than 2 years cooking staff items In the case of a relevant event, the risk evaluation value is multiplied by the respective weighting value. Items [more than 5 years of experience over 50%] and [number of children per teacher 10 to less than 25] correspond to all events, so to speak, it is information indicating the personnel attributes of the entire organization of the facility. Is reflected in the risk assessment of the event. On the other hand, the items [Teacher with more than 10 years of experience], [Teacher with less than 2 years of experience], and [Cooking staff with less than 2 years of experience] correspond only to the specific events [Gymnastics], [Music], [Lunch] Therefore, the number of personnel and their attributes that are somehow related to the event will be reflected in the risk assessment.

As described above, the weighting values of facility personnel information related to all events are reflected in the evaluation values of all events. The specific calculation in this case is as follows.
Evaluation value of event "craft" considering facility personnel information = evaluation value of event "craft" x (weighted value [1.0] with a ratio of 5 years or more of experience over 50%) x (10 or more children per teacher) Weighted value less than 25 [1.2])
The weighted value of the item [Teacher over 10 years of experience] is reflected only in the event “Gymnastics”. In the specific calculation in this case, the risk evaluation value is reduced in consideration of the skills of experienced teachers as follows.
Evaluation value of the event “Gymnastics” in consideration of facility personnel information = Evaluation value of the event “Gymnastics” x (weighted value [1.0] with a ratio of 5% or more for experience over 5 years) x (10 or more children per teacher) Weighted value less than 25 [1.2]) × (weighted value of [teacher over 10 years of experience] [0.8])

  FIG. 17 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. The storage unit 550 stores various data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, entrance / exit information master table DW, child information master table CI, facility personnel master table HRI). Etc.) is stored. In this flowchart, more appropriate risk evaluation / management is performed using the facility personnel master table HRI. Steps S51 to S54 and S57 in FIG. 17 are the same processes as those in FIG. 14 and will not be described. Only steps S55 and S56, which are different steps, will be described. In step S55, the risk identification unit 512 refers to the facility personnel master table HRI, searches for facility personnel information of an item corresponding to the event, and weights numerical values of the facility personnel information (a plurality may exist). Is identified. In step S56, the risk specifying unit 512 multiplies each numerical value of the risk information extracted in step S52 by the “weighting numerical value” specified in step S55, and replaces each original numerical value with the calculation result. Finally, in step S57, the risk output unit 513 outputs the risk management data including the risk information extracted by the risk specifying unit 512 and reflecting the facility personnel information with the weighted numerical value to the display unit 560. The steps corresponding to the number of events are repeated in the same manner as the processing in FIGS. If the processes in steps S25 and S26 of FIG. 8 described in the second embodiment are performed in parallel, more appropriate risk evaluation / management reflecting the management area information can be performed. Further, if the processes of steps S35 and S36 of FIG. 11 described in the third embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the entrance / exit information. Furthermore, if the processes of steps S45 and S46 of FIG. 14 described in the fourth embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the child information.

  FIG. 18 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M51 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The top M52 multiplies the numerical value portion (risk evaluation value) of the “risk information” displayed on the top M51 by the “weighting numerical value” of a plurality of facility personnel information specified with reference to the “facility personnel master table HRI”. The result is output as one frame of the timetable. As described above, according to this configuration, it is possible to perform more appropriate risk evaluation / management using not only facility event data but also facility personnel information having various attributes.

<Embodiment 6>
FIG. 19 is a block diagram showing an outline of a child acceptance facility risk management system (CAFRMS) according to Embodiment 6 of the present invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 600 includes a control unit (CPU) 610, an input unit 620, an output unit 630, a communication unit 640, a storage unit 650, and a display unit 660. Have The control unit 610 includes an acquisition unit 611, a risk identification unit 612, a risk output unit 613, a morpheme analysis unit 614, and a case countermeasure identification unit 615. The CAFRMS 600 in FIG. 19 has substantially the same configuration and function as the CAFRMS 100, 200, 300, 400, 500 shown in FIGS. 1, 6, 10, 13, and 16, and FIGS. It should be understood that functional parts having names similar to those in FIGS. 10, 13, and 16 have similar functions unless otherwise specified. In this embodiment, the function of the risk output unit 613 provided in the control unit 610, the case countermeasure specifying unit 615 newly provided in the control unit 610, the countermeasure information master table SI and the case information newly included in the storage unit 650 Different from the master table CEI. The countermeasure information master table SI describes (includes) at least one countermeasure information that is associated with each risk information and prevents or reduces at least a part of the risk information. The case information master table CEI describes (including) at least one near-miss / accident case information (including not only near-miss but also minor accidents and serious accidents) associated with each risk information.

  The case countermeasure identification unit 615 identifies countermeasure information related to each risk information with reference to the countermeasure information master table SI. The risk output unit 613 outputs risk evaluation data further including the extracted risk information and the specified countermeasure information. Further, the case countermeasure specifying unit 615 specifies near-miss case information related to each risk information with reference to the case information master table CEI. The risk output unit 613 outputs risk evaluation data further including the extracted risk information and the identified near-miss case information. This makes it possible to present countermeasure information and near-miss / accident case information to the user along with the risk, and present risk management information in an easy-to-understand manner to the facility teachers, parents, infants, children, etc. It becomes possible to do.

  FIG. 20 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. The storage unit 650 stores various data (eg, risk information master table RMT, management area master table MR, synonym dictionary data SDD, entrance / exit information master table DW, child information master table CI, facility personnel master table HRI). It is assumed that a countermeasure information master table SI, a case information master table CEI, etc.) are stored. In this flowchart, more appropriate risk evaluation / management is performed using the countermeasure information master table SI and the case information master table CEI. Steps S61 to S64 in FIG. 20 are the same processes as those in FIG. 17 and will not be described. Only steps S65 to S67, which are different steps, will be described. In step S65, the case countermeasure identifying unit 615 refers to the countermeasure information master table SI and identifies countermeasure information (a plurality may exist) related to each risk information. Next, in step S66, the case countermeasure identifying unit 615 identifies near-miss / accident case information related to each risk information with reference to the case information master table CEI. Finally, in step S67, the risk output unit 613 outputs risk management data including the identified “measure information” and “case information” together with the extracted risk information. The steps corresponding to the number of events are repeated in the same manner as the processing in FIGS. 8, 11, 14, and 17. If the processes in steps S25 and S26 of FIG. 8 described in the second embodiment are performed in parallel, more appropriate risk evaluation / management reflecting the management area information can be performed. Further, if the processes of steps S35 and S36 of FIG. 11 described in the third embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the entrance / exit information. Furthermore, if the processes of steps S45 and S46 of FIG. 14 described in the fourth embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the child information. Similarly, if the processes in steps S55 and S56 of FIG. 17 described in the fifth embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the facility personnel information.

  FIG. 21 is a diagram illustrating a part of the countermeasure information master table. As shown in the figure, in the countermeasure information master table SI, items of risk mitigation measures for reducing or eliminating the risk are described in association with the risk information. FIG. 22 is a diagram illustrating a part of the case information master table. As shown in the figure, the case information master table CEI describes at least one near-miss case information associated with each risk information.

  FIG. 23 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M61 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The frame M62 specifies countermeasure information corresponding to the “risk information” displayed on the frame M61 and displays it together. As described above, according to this configuration, it is possible to perform more appropriate risk evaluation / management using not only facility event data but also countermeasure information corresponding to various risk information items.

  FIG. 24 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M61 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The frame M63 specifies near-miss / accident case information corresponding to the “risk information” displayed on the frame M61 and displays it together. As described above, according to this configuration, it is possible to perform more appropriate risk evaluation / management using not only facility event data but also near-miss case information corresponding to various risk information items.

<Embodiment 7>
FIG. 25 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to the seventh embodiment of the present invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 700 includes a control unit (CPU) 710, an input unit 720, an output unit 730, a communication unit 740, a storage unit 750, and a display unit 760. Have The control unit 710 includes an acquisition unit 711, a risk identification unit 712, a risk output unit 713, a morpheme analysis unit 714, a case countermeasure identification unit 715, and a compliance identification unit 716. 25 has substantially the same configuration and function as the CAFRMS 100, 200, 300, 400, 500, and 600 shown in FIGS. 1, 6, 10, 13, 16, and 19. FIG. It should be understood that functional units having names similar to those in FIGS. 6, 10, 13, 16, and 19 have similar functions unless otherwise specified. In this embodiment, the function of the risk output unit 713 provided in the control unit 710, the compliance determination unit 716 newly provided in the control unit 710, and the compliance information master table CMT newly included in the storage unit 750 are different. The compliance information master table CMT is associated with at least one event and applies to the child acceptance facility (including ministerial ordinances, ordinances, enforcement regulations, etc.), standards, rules (local governments, organizations, organizations, child acceptance facilities themselves) It describes compliance information including at least one standard item to be complied with (including management manual, guideline, management standard, management rule, etc.).

  The compliance determination unit 616 refers to the compliance information master table CMT to determine whether or not the reference items to be compliant are satisfied. For example, with reference to the compliance information master table CMT for each event, it is determined whether or not the criteria item to be complied with is satisfied. The risk output unit 713 outputs the determination result of the reference item. For example, when the reference item is not satisfied, the risk output unit 713 outputs risk evaluation data further including that fact. This makes it possible to present the compliance status and violation status to the user together with the risk, and presents risk management information in an easy-to-understand manner to the facility teachers, parents, infants, children, etc. It becomes possible.

  FIG. 26 is a diagram illustrating a part of the compliance information master table. As shown in the figure, the compliance information master table CMT describes items of compliance information associated with each event. Initially, if all are not set, when the risk information is output by this system, all compliance information is displayed as not set for warning to the user. Therefore, the user needs to appropriately set the information in the compliance information master table CMT in advance based on the situation of his / her child receiving facility. In the compliance information master table CMT in FIG. 26, since some items are not set, the compliance information items CMT1 and CMT2 are highlighted to indicate to the user that an action is required for the items. Yes. The compliance information master table CMT lists items that seem to be related to most facilities, but items that are not related to one's own facility are listed in the third field as in the compliance information item CMT3. It is also possible to set a mask (exclude setting) by entering * (asterisk). An item with a mask is handled as if the item does not exist on the system side. In addition, if there is a deadline setting such as 6 months or an expiration date (mode period expiration date), the timer (not shown) provided in the system is used to check for expiration or expiration, and if the expiration date or Those that have passed have a function of updating the corresponding item of the compliance information master table CMT to “non-conforming”. Alternatively, it also has a function of outputting a warning text together with the risk assessment to warn the user at any number of days before expiration or due date (a few weeks ago, a month before).

  FIG. 27 is a flowchart illustrating an example of processing executed in the system illustrated in FIG. The storage unit 750 stores various data (for example, risk information master table RMT, management area master table MR, synonym dictionary data SDD, entrance / exit information master table DW, child information master table CI, facility personnel master table HRI). It is assumed that a countermeasure information master table SI, a case information master table CEI, a compliance information master table CMT, etc.) are stored. In this flowchart, more appropriate risk evaluation / management is performed using the compliance information master table CMT. Steps S71 to S74 in FIG. 27 are the same processes as those in FIG. 20 and will not be described. Only steps S75 and S76, which are different steps, will be described. In step S75, the compliance determination unit 616 refers to the “compliance information master table CMT” to identify “compliance information” of the item corresponding to the event, and the “compliance information” item conforms to the standard. It is determined whether or not. Finally, in step S76, the risk output unit 713 outputs risk management data including the extracted risk information and the identified “compliance information” that does not conform to the standard. Here, all compliance determination results (compliance compliance status) may be output. However, since the display becomes complicated, only nonconformity (including unset) is included in the risk evaluation and output. The steps corresponding to the number of events are repeated in the same manner as the processing in FIGS. 8, 11, 14, 17, and 20. If the processes in steps S25 and S26 of FIG. 8 described in the second embodiment are performed in parallel, more appropriate risk evaluation / management reflecting the management area information can be performed. Further, if the processes of steps S35 and S36 of FIG. 11 described in the third embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the entrance / exit information. Furthermore, if the processes of steps S45 and S46 of FIG. 14 described in the fourth embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the child information. Similarly, if the processes in steps S55 and S56 of FIG. 17 described in the fifth embodiment are performed in parallel, it is possible to perform more appropriate risk evaluation / management that further reflects the facility personnel information. Further, if the processing of steps S65 and S66 of FIG. 20 described in the embodiment 6 is performed in parallel, more appropriate risk evaluation / management that further reflects countermeasure information and case information can be performed.

  FIG. 28 is a diagram showing one frame of a timetable including risk management data output by the system shown in FIG. The frame M71 refers to the risk information master table RMT and outputs “risk information” extracted based on the acquired facility event data as one frame of the timetable. The frame M72 specifies compliance information corresponding to the “event” and “risk information” displayed on the frame M71 and displays them together. As described above, according to this configuration, it is possible to perform more appropriate risk assessment and management using “compliance information” corresponding to various items of risk information as well as facility event data. . In particular, compliance compliance of organizations and organizations (eg compliance with laws and regulations) is very important for risk management of organizations and organizations, and this embodiment makes it possible to easily check such compliance compliance. To do.

  FIG. 29 is a diagram showing a part of the in-garden (caregiver) safety management sheet including the risk management data output on the screen by the system shown in FIG. As shown in the figure, the in-house safety management sheet TRS is provided in the form of a timetable, and it is possible to grasp the risk cases (accidents, near-miss cases, etc.) that should be noted when the educational unit is implemented immediately when the childcare teacher sees it. Is possible. In addition, nursery teachers can add risk cases encountered in daily educational settings and points they have noticed to the in-park safety management sheet TRS, or simply report risk cases by filling in check boxes. System. The park safety management sheet TRS is convenient to display on the display unit when data is input as described above, but it can also be used after being output to a printer and printed. This kind of in-house safety management sheet TRS is regularly provided to educational service providers (kindergarten teachers, nursery school teachers, elementary school teachers, etc.), and education service providers are educated and instructed to manage the safety of children. It is important to ensure that

  FIG. 30 is a diagram showing a part of the safety management sheet for parents including the risk management data output on the screen by the system shown in FIG. As shown in the figure, the parental safety management sheet TRS is provided in the form of a timetable, and as soon as the guardian sees, there are risk cases (accidents, It is possible to grasp near-miss cases). The parent / guardian is given the safety management sheet TRS for the parent / guardian, who can view the risk management status of the nursery school by viewing it, and further point out the points to be aware of in the life of the nursery school. It is possible to educate within. For example, in the message box MSG1, the message “Checked items are examples that have occurred in our kindergarten. Parents are also grateful for the guidance and attention of their children.” It is. By sharing risk cases in this way, risk problems and improvements are highlighted, so accidents and near-miss cases and the safety management status of educational facilities are more proactive than concealment. It is important to disclose to the side. The guardian safety management sheet TRS also has a function of displaying the compliance information windows CMPW1, 2 and the like and transmitting the compliance status of the nursery school to the guardian.

  The park safety management sheet TRS and the guardian safety management sheet TRS can store history information at the time of change or output together with a time stamp in a storage unit. By doing this, in the event of a serious accident later, it will be confirmed where the risk management problem occurred, or whether it was said that the legal risk management duty was fulfilled. It becomes possible. Further, the park safety management sheet TRS and the guardian safety management sheet TRS include a risk information master table RMT, a management area master table MR, an entrance / exit information master table DW, a child information master table CI, a facility personnel master table HRI, countermeasures Information that can be extracted from the information master table SI, the case information master table CEI, and the compliance information master table CMT can be included as long as it is effective for safety management. It is also possible to include facility personnel information.

<Embodiment 8>
FIG. 31 is a block diagram showing an outline of a child reception facility risk management system (CAFRMS) according to the eighth embodiment of the present invention. As shown in the figure, the child acceptance facility risk management system (CAFRMS) 800 includes a control unit (CPU) 810, an input unit 820, an output unit 830, a communication unit 840, a storage unit 850, and a display unit 860. Have The control unit 810 includes an acquisition unit 811, a risk identification unit 812, a risk output unit 813, a morpheme analysis unit 814, a case countermeasure identification unit 815, and a compliance identification unit 816. The CAFRMS 800 in FIG. 31 has substantially the same configuration and function as the CAFRMS 100, 200, 300, 400, 500, 600, and 700 shown in FIGS. 1, 6, 10, 13, 16, 19, and 25. The functional units having the same names as those in FIGS. 1, 6, 10, 13, 16, 19, and 25 should be understood to have the same functions unless otherwise specified. In this embodiment, the function of the acquisition unit 811 provided in the control unit 810, the contents of the child information master table CI-X included in the storage unit 850, and the child information management newly connected locally to the system 800 The server KIMS and the terminal PC3 connected to the KIMS are different.

  The kindergarten information management server KIMS stores the number of children accepted by the child acceptance facility, the attributes, and n child chart information items (child information items) CKE1, CKE2, CKE3, CKE,. It has a medical record information database CKDB and is always updated with the latest data. Since the child chart information item generally includes health information (however, it is not always necessary to include the health information), it is referred to as a “child chart information item” for convenience. Children's chart information items are allocated to each kindergarten, and the name, age, sex, health checkup information such as height and weight of the kindergarten, illness information, injury / illness information, chronic illness, allergy status and physical measurement findings It describes comprehensive and detailed child information including physical examination information, injuries, information on the course of illness, instruction contents, childcare contents, etc. The child chart information item managed and updated by the kindergarten (child) information management server KIMS is a data item that can be taken out, and after being downloaded to the terminal PC 3 through appropriate authentication processing, for example, It can be stored in an external storage device (USB memory, storage chip, IC card, etc.) and provided to the guardian. For example, according to the kindergarten information management server KIMS, when a parent graduates from a kindergarten, the guardian receives an external storage medium storing child chart information items related to his / her child, and stores the child information stored in the child information in the elementary school It is possible to register with an information management server (not shown) and to continuously manage the child information continuously even if the child receiving facility where the child attends changes.

  The acquiring unit 811 receives, from the child medical record information database CKDB of the kindergarten information management server KIMS via the communication unit 840, the number of children accepted by the child receiving facility, attributes, and n child medical record information items (including these history information). Child information items) CKE1, CKE2, CKE3, CKE ..., CKEn are further acquired. The storage unit 850 constructs a child information master table CI-X in the storage unit 850 from the n child chart information items (child information items) CKE1, CKE2, CKE3, CKE,..., CKEn acquired from the acquisition unit 811. The child information master table CI-X includes n child medical record information items (child information items) CKE1, CKE2, CKE3, CKE..., CKEn, and a child medical record extracted from these child medical record information items by a statistical method. Statistical information KSI is stored. The risk identifying unit 812 refers to the risk information master table RMT and the child information master table CI-X, and takes into account the child information based on the facility event data acquired by the acquiring unit 811. Extract information. The child information master table CI-X that is referred to by the risk identification unit 812 is often appropriate to use the child chart statistical information KSI. However, depending on the contents to be referenced, the child chart information that is an individual entry. The items CKE1, CKE2, CKE3, CKE ..., CKEn can be directly referred to, or the risk identification unit 812 can calculate the statistical method from the child chart information item (total number of children, number of children by class, age group of the whole facility) Calculate the number of children, calculate the number of children by class and by age zone, calculate the number of allergic children, calculate the attribute information for each class that performs the event (for example, extract and count allergic children in the Sakura group, accident cases in the violet group) The child information necessary for extraction and counting) may be extracted and used each time.

  FIG. 32 is a flowchart illustrating an example of processing executed by the system illustrated in FIG. In this flowchart, the child information master table CI-X is constructed using the child information management server KIMS which is an external system, and more appropriate risk evaluation and management are performed. Steps S81 and S84 in FIG. 32 are the same processes as those in FIG. 2 and will not be described. Only steps S82 and S83, which are different steps, will be described. In step S82, the acquisition unit 811 acquires a child chart information item from the kindergarten management server KIMS, and constructs a child information master table CI-X. Next, in step S83, the risk specifying unit 812 refers to the risk information master table RMT and the child information master table CI-X, relates to the facility event data based on the facility event data in consideration of the child information. Extract risk information. The evaluation value of the risk information is preferably calculated by “weighting value” as in the other embodiments. In addition, more appropriate risk assessment and management is performed by using other factors (management area information, facility personnel information, etc.) used in other embodiments and further reflecting those other factors with weighted numerical values. It is also possible.

  According to each embodiment of the present invention, it is possible to perform numerical evaluation as well as qualitative evaluation of risk in consideration of various information in risk management of a child receiving facility. If such a child acceptance facility risk management system is configured as an ASP and the risk information of many child acceptance facilities such as kindergartens, nursery schools, and elementary schools can be accumulated, more risk examples and countermeasure examples can be referred to. Appropriate risk management (risk reduction activities) and risk assessment will be possible. In addition, by acquiring risk management evaluation data of many facilities, it is possible to make a relative evaluation of the degree of management of the risk management of each facility.

  Although the present invention has been described based on the drawings and examples, it should be noted that those skilled in the art can easily make various modifications and corrections based on the present disclosure. Therefore, it should be noted that these variations and modifications are included in the scope of the present invention. For example, functions included in each unit, each step, and the like can be rearranged so as not to be logically contradictory, and a plurality of means, steps, and the like can be combined into one or divided. In the embodiment, an example of a facility that accepts an infant such as a kindergarten or a nursery school has been described. However, it should be noted that the present invention can be applied to a facility that accepts not only an infant but also all children. Note that the risk evaluation values and risk rankings shown in each embodiment are for convenience, and can be corrected, changed, and updated according to the user environment and social evaluation.

  The park safety management sheet TRS and the guardian safety management sheet TRS can store history information at the time of change and output together with a time stamp in the storage unit, but the risk information master table RMT, the management area The master table MR, the entrance / exit information master table DW, the child information master table CI, the facility personnel master table HRI, the countermeasure information master table SI, the case information master table CEI, the compliance information master table CMT, etc. are changed regardless of the embodiment. It is preferable to store the history information in the storage unit every time it is updated. By storing history information in this way, it becomes possible to reconfirm and examine safety management problems and management status regularly or after some risk case occurs.

100, 200, 300, 400, 500, 600, 700, 800 Child acceptance facility risk management system 110 Control unit 111 Acquisition unit 112 Risk identification unit 113 Risk output unit 120 Input unit 130 Output unit 140 Communication unit 150 Storage unit 160 Display unit 210 control unit 211 acquisition unit 212 risk identification unit 213 risk output unit 214 morpheme analysis unit 220 input unit 230 output unit 240 communication unit 250 storage unit 260 display unit 310 control unit 311 acquisition unit 312 risk identification unit 313 risk output unit 314 morpheme analysis Unit 320 input unit 330 output unit 340 communication unit 350 storage unit 360 display unit 410 control unit 411 acquisition unit 412 risk identification unit 413 risk output unit 414 morpheme analysis unit 420 input unit 430 output unit 440 communication unit 450 storage unit 460 display unit 510 Control unit 11 acquisition unit 512 risk identification unit 513 risk output unit 514 morpheme analysis unit 520 input unit 530 output unit 540 communication unit 550 storage unit 560 display unit 610 control unit 611 acquisition unit 612 risk identification unit 613 risk output unit 614 morpheme analysis unit 615 Countermeasure identification unit 620 Input unit 630 Output unit 640 Communication unit 650 Storage unit 660 Display unit 710 Control unit 711 Acquisition unit 712 Risk identification unit 713 Risk output unit 714 Morphological analysis unit 715 Case countermeasure identification unit 716 Compliance determination unit 720 Input unit 730 Output Unit 740 communication unit 750 storage unit 760 display unit 810 control unit 811 acquisition unit 812 risk identification unit 813 risk output unit 814 morpheme analysis unit 815 case countermeasure identification unit 816 compliance determination unit 820 input unit 830 output unit 840 communication unit 850 Memory unit 860 Display unit KIMS Child information management server CKDB Child chart information database CEI Case information master table CI, CI-X Child information master table CMT Compliance information master table CMT1, CMT2, CMT3 Compliance information item DW Gateway information master table EV Event FMSS Facility management support server HRI Facility personnel master table KBD Keyboard M1-M5 Top M21-M26 Top M31 Top M32 Top M41 Top M42 Top M51 Top M52 Top M61 Top M62 Top M63 Top M71 Top M72 Top MR Management area master table MS1 Mobile phone terminal NET network PC1, PC2, PC3 terminal PDA1 mobile terminal R11i risk assessment data element R11r risk information Element R1e Event R1iT Risk assessment comprehensive data R21r Risk information element R2e Event RI Risk information RMT Risk information master table RMT Table RMT Risk information master table SDD Synonym dictionary data SI Countermeasure information master tables TTB, TTB1, TTB2 Timetable

Claims (14)

A child acceptance facility risk management system,
A storage unit for storing a risk information master table including at least one event under the control of the child reception facility and at least one risk information associated with the event;
An acquisition unit for acquiring facility event data including at least one event;
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk identifying unit that extracts risk information related to the facility event data; and
A risk output unit that outputs risk management data including risk information extracted by the risk identification unit;
A child acceptance facility risk management system characterized by comprising: In the child acceptance facility risk management system according to claim 1,
The risk information included in the risk information master table includes risk evaluation data indicating the degree of influence of each risk information,
The risk output unit outputs risk management data further including risk evaluation data including an influence degree of each risk information;
A child acceptance facility risk management system. In the child acceptance facility risk management system according to claim 1 or 2,
The facility event data is a timetable or event schedule in which a plurality of events are defined in time series,
The risk output unit outputs a timetable or event schedule including at least a part of the risk management data;
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 3,
The risk information includes at least one facility information and an accident occurrence state related to each facility information,
The risk identification unit
With reference to the risk information master table, based on the facility event data acquired by the acquisition unit, the accident event related to the at least one facility information and each facility information is considered and related to the facility event data Extracting risk information,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 4,
The storage unit further stores a management area master table describing at least one management area information;
The risk identification unit
With reference to the risk information master table and the management area master table, based on the facility event data acquired by the acquisition unit, considering the management area information, to extract the risk information related to the facility event data,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 5,
The storage unit
Further storing an entry / exit information master table describing at least one entry / exit information,
The risk identification unit
With reference to the risk information master table and the entrance / exit information master table, based on the facility event data acquired by the acquisition unit, considering the entrance / exit information, extract risk information related to the facility event data,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 6,
The storage unit
Further storing a child information master table describing child information including the number and / or attributes of the children accepted by the child receiving facility;
The risk identification unit
With reference to the risk information master table and the child information master table, based on the facility event data acquired by the acquisition unit, considering the child information, to extract the risk information related to the facility event data,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 6,
The acquisition unit further acquires, from a kindergarten information management server, child information describing the number of children accepted by the child reception facility and / or child information including attributes,
The storage unit
From the child information acquired by the acquisition unit, build a child information master table in the storage unit,
The risk identification unit
With reference to the risk information master table and the child information master table, based on the facility event data acquired by the acquisition unit, considering the child information, to extract the risk information related to the facility event data,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 8,
The storage unit
A facility personnel master table describing facility personnel information including the number and / or attributes of the child receiving facility personnel;
The risk identification unit
With reference to the risk information master table and the facility personnel master table, based on the facility event data acquired by the acquisition unit, considering the facility personnel information, to extract the risk information related to the facility event data,
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 9,
The storage unit further stores a countermeasure information master table including at least one countermeasure information associated with each risk information and preventing or reducing at least a part of the risk information;
The child reception facility risk management system includes:
With reference to the countermeasure information master table, it further includes a case countermeasure identifying unit that identifies countermeasure information related to each risk information,
The risk output unit outputs risk assessment data further including identified countermeasure information that prevents or reduces at least a part of the extracted risk information;
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 10,
The storage unit further stores a case information master table including at least one near-miss / accident case information associated with each risk information;
The child reception facility risk management system includes:
With reference to the case information master table, it further includes a case countermeasure identifying unit for identifying near-miss / accident case information related to each risk information,
The risk output unit is
Output risk assessment data that further includes the extracted risk information and the identified near-miss case information.
A child acceptance facility risk management system. In the child acceptance facility risk management system according to any one of claims 1 to 11,
The storage unit
Further storing a compliance information master table describing compliance information including at least one standard item to be complied with among laws, standards, and rules applicable to the child receiving facility;
The child reception facility risk management system includes:
With reference to the compliance information master table, further comprising a compliance determination unit that determines whether or not a standard item to be compliant is satisfied,
The risk output unit is
If the criteria item is not satisfied, output risk assessment data further including that,
A child acceptance facility risk management system. A child acceptance facility risk management method comprising:
A storage step of storing in the storage means a risk information master table including at least one event under the control of the child reception facility and at least one risk information associated with the event;
An acquisition step of acquiring facility event data including at least one event using a computing means;
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk specifying step of extracting risk information related to the facility event data;
A risk output step of outputting risk management data including risk information extracted in the risk identification step;
A child reception facility risk management method characterized by comprising: A program for causing a computer to execute a child acceptance facility risk management method,
A storage step of storing in the storage means a risk information master table including at least one event under the control of the child reception facility and at least one risk information associated with the event;
An acquisition step of acquiring facility event data including at least one event;
Referring to the risk information master table, based on the facility event data acquired by the acquisition unit, a risk specifying step of extracting risk information related to the facility event data;
A risk output step of outputting risk management data including risk information extracted in the risk identification step;
The program characterized by having.

Images