Vol.5 No.2 2012

41/66

Research paper : Information sharing platform to assist rescue activities in huge disasters (I. Noda)−115−Synthesiology - English edition Vol.5 No.2 (2012) and various disaster information systems have been constructed by the central government, prefectures, and local municipalities. However, we rarely hear that such systems functioned as expected during the 2011 earthquake. The reasons why such disaster information systems could not be utilized may be because they were designed as closed and unalterable systems dedicated to disaster prevention. As with other disaster measures, the information system must have case-by-case flexibility.The viewpoints important in designing the disaster information system that can overcome such difficulties are case-by-case flexibility and lifecycle. Since there are many phenomena that occur during a disaster, it is virtually impossible to predict all events and to incorporate the information processing functions into a system. In fact, in the hearings of the local governments after the Great East Japan Earthquake,[5] it became clear that the prior disaster prevention plan had to be altered in various ways. On the other hand, the activities of information volunteers functioned effectively, as will be explained in chapter 5. The characteristic of the activities by these volunteers was the case-by-case flexibility where the system was built according to the situation and real requirements. Of course, it is not practical to build a disaster information system entirely after an event occurs, but it is necessary to leave room to incorporate such case-by-case flexibility when designing the system. The viewpoint of lifecycle is the way of looking at the timescale difference of the day-to-day advancement of information technology versus the once-in-a-hundred or once-in-a-thousand year disaster. This means that rather than packing as much state-of-the-art technologies into the system as possible, the disaster information system must be designed by paying attention to the fact that technologies will become obsolete with passage of time and will be succeeded by newer technologies.To establish a method for designing a disaster information system that incorporates the above two viewpoints, a concept of “data-centered ad hoc system building” is adopted in this paper. With this approach, the following three points form the design policy for building the information system. Open system: the design policy where each information system is built assuming usage of individual functions of the system separately and the system being able to be linked with other systems. This responds to the case-by-case flexibility and the lifecycle viewpoints. Universal data format and protocol standard: the design policy for simplifying the linkages of the functions and for creating common linkage parts to enable easy replacement and succession of the system. This responds to the case-by-case flexibility and the lifecycle viewpoints. Downward scalabilityNote 1): the design policy that allows the system to operate on any type of information device or at any sized infrastructure. This responds to the case-by-case flexibility viewpoint.As the core technologies to realize such a design policy, we introduce the disaster mitigation information platform that is the basic design of the system, the mitigation information sharing protocol (MISP) that is its core, and the database (DaRuMa). The relationships of the viewpoints, design policy, and core technologies are shown in Fig. 1.The paper will be organized as follows. In chapter 2, the mitigation information sharing platform and its protocol database will be explained. In chapter 3, the design policy of the proposed platform will be discussed from the viewpoints of disaster prevention and mitigation. In chapter 4, the verification system of the proposed platform and examples of actual operating systems will be introduced. In chapter 5, case studies during the Great East Japan Earthquake will be taken up to discuss the effectiveness and the problems of the above design policy.2 Design philosophy of the mitigation information sharing platform and its implementationIn this chapter, I will explain the design philosophy of the mitigation information sharing platform[6][7] that is the framework for sharing the disaster information proposed in this paper, the mitigation information sharing protocol (MISP) that is the center of its implementation, and the database for rescue utility management (DaRuMa).2.1 Mitigation information sharing platform by data-centered module linkageThe framework of disaster information sharing is, as shown in Fig. 2, the linkages of the various disaster information systems (these will be called modules) operated by different organizations through the mediation by database. Here, this framework is called the mitigation information sharing platform.Fig. 1 Relationships of the viewpoints, design policy, and core technology of the disaster information systemDownward scalabilityOpen systemLifecycle (subch. 3.1) Case-by-case (subch. 3.2)Universal data format protocolMitigation information sharing platform (subch. 2.1)MISP(subch. 2.2)DaRuMa(subch. 2.3)Data-centered ad hoc system linkage

※このページを正しく表示するにはFlashPlayer9以上が必要です