Extension of Coding CEVNI Signs and Marking for European Waterways
This paper presents a new method of coding for signs and marking, which is based on the extension of signs and marking described in Annexes 7 and 8 of the European Code for Inland Waterways (CEVNI). Being members of three European expert groups, we have proposed these new codes of waterway signs and marking and recommend them for cases where they can be efficiently used. The main goal is to enable the use of these codes in databases, GIS systems and Web applications for efficient maintenance of waterway information. In addition, they will also contribute to international data exchange for creating standardised electronic messages described by ERI and NtS working groups. The intention is not to amend the existing coding from the Inland ECDIS Standard, which was developed for creation of Electronic Navigation Charts (ENCs). For example, the use of these new codes is tested through the Web GIS application for presentation of inland waterway signs and marking on the Danube River in Croatia. The application examples concern automatically generated reports on the position, characteristics and functioning of different waterway signs and river navigation marking located on the digital map.
Sharing Data among Users through Dynamic Web Applications for the River Information System
The aim of the Croatian national joint project as part of the CROatian River Infor-mation Services (CRORIS) is to develop a specialized information system for sur-veillance of the Croatian segment of the Danube River (i.e., River IS). In this paper, emphasis is placed on sharing relevant and timely information among different River IS user groups as well as on efficient data management provided by this in-formation system. For this purpose, a use case diagram of the Unified Modeling Language (UML) was created to represent the hierarchies of user groups and differ-ent applications accessed by a particular group. As an example, the Web application architecture for automatic generation of maps, diagrams and reports of water level data is shown. Application architecture is based on the three-tier client-server archi-tecture for the Web. The eXtensible Markup Language (XML) based approach using modern object technologies was applied. For presentation of the time series dia-grams, the Scalable Vector Graphic (SVG) documents were created. The concrete application example involves presentation of daily average water level data in the form of the time series diagram for the monitoring station selected on the map.
Marine and Hydrokinetic Technology Development Risk Management Framework
Over the past decade, the global marine and hydrokinetic (MHK) industry has suffered a number of serious technological and commercial setbacks. To help reduce the risks of industry failures and advance the development of new technologies, the U.S. Department of Energy (DOE) and the National Renewable Energy Laboratory (NREL) developed an MHK Risk Management Framework. By addressing uncertainties, the MHK Risk Management Framework increases the likelihood of successful development of an MHK technology. It covers projects of any technical readiness level (TRL) or technical performance level (TPL) and all risk types (e.g. technological risk, regulatory risk, commercial risk) over the development cycle. This framework is intended for the development and deployment of a single MHK technology—not for multiple device deployments within a plant. This risk framework is intended to meet DOE’s risk management expectations for the MHK technology research and development efforts of the Water Power Program (see Appendix A). It also provides an overview of other relevant risk management tools and documentation.1 This framework emphasizes design and risk reviews as formal gates to ensure risks are managed throughout the technology development cycle. Section 1 presents the recommended technology development cycle, Sections 2 and 3 present tools to assess themore » TRL and TPL of the project, respectively. Section 4 presents a risk management process with design and risk reviews for actively managing risk within the project, and Section 5 presents a detailed description of a risk registry to collect the risk management information into one living document. Section 6 presents recommendations for collecting and using lessons learned throughout the development process.« less