1 / 9

Development and use of ” State-of-the-Art” project databases

Development and use of ” State-of-the-Art” project databases. Why How Examples Conclusions. Development of new systems or products should/must be based on existing knowledge , technology and user needs in order to save time and money develop broadly accepted solution

makani
Download Presentation

Development and use of ” State-of-the-Art” project databases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Development and use of”State-of-the-Art” project databases Why How Examples Conclusions

  2. Development of new systems or products should/must be based on existing knowledge, technology anduser needs in order to save time and money develop broadly accepted solution Comply with international standards and requirements or: Not invent more wheels Why ”State-of-the-Art”

  3. Basic question What is the actual ”ART” The art can be defined in several ways By a specified task Ex: The contingency situation along the Norwegian coastline (Sea-IT) Multi hazard warning in the Indian sea (Study for NORAD) By a specified area or domain. Ex.: Information systems for safe and efficient waterborne transport (Waterman, EU project) By a objectives and deliverables in a specific project. Ex.: Overview of technology, results from other projects, existing system, user needs, IPR, rules and regulations etc. (MarNIS, EU project) and others….

  4. Simulation Nav. aid Regulations Info-system Remote pilotage Fairway Pilotage Resources Rail Air Piracy Current Risk eval. WEB Navigation Decision support VTMIS/RIS AIS Drift ECS Weather ETIS Vessel ECDIS Traffic Oil spill Contingency Waves Forecast AIS Environment VTS Water level MIO ETIS SAR Int. bodies Pilotage Legislation Traffic Remote Contingency Long range Fairway Logistics Coast Guard Ports Hand over MMI Cargo LCA Vessel movement ETA Presentation DGPS EuroRep HAZMAT Tech.. Management Navigation AIS Automation Satellite Info Services Comm. ETA ETA ETA AIS AIS Tracking Fleet management Purpose Cargo Vessel Intermodality Terminals Ports Interoperability Data base link NCA Vessel Reporting MMI ECDIS ETIS Ecdis for VTS Standards VTMIS/RIS Risk evaluation VTS Regulations Training Remote training Integration Support system Land Partners Data models System architecture Sea Reporting Navigation plans IMO Int. bodies Broadcasting Standards Platform MMI Path prediction IALA. Leisure crafts Tech. Requirements Standards Communication AIS General use Standards Demands Object classes Price Weight Work. groups Integrate info Users Funding Green tax Standards User groups VTMIS/RIS Test bed, VTMIS 2000 The Challenge Domain Safe Efficient Waterborne transport Technology Infrastructure

  5. Step 1: “State-of-the-art” Knowledge data base Step 2: “Art” definitions Step 3: Analysis of theinformation Step 4: Collect user requirementsand additional information Step 10: Update “State-of-the-art” Step 5: Final analysis Step 6: Summary of “State-of-the-art” Step 9: Testing, implementing and operating new system Step 8: Develop new systems Step 7: Recommendations andguidance Systematic approach(The WATERMAN approach) WATERMAN Framework

  6. To establish and maintain a database as a tool to develop a joint initial and continued understanding of State of the Art in relation to project objectives and activities; To update the project database with the research results to facilitate a viable tool for all actors in the project; To develop a general approach for collecting and processing user and stakeholder requirements to ensure a best possible focus in the project activities in relation to all defined objectives. Objectives for a project data baseThe MARNIS project

  7. MARNIS Information storage and Retrieval system - MISaR User interface for input and search Project Database (metadata) Information storage

  8. DeepWater (Maritime IKT) Norwegian competence USCG requirements ARKTRANS (Architecture for transport) System architectureClassificationProject and system information Hazard Warning (Tsunami warning South-East Asia)Norwegian competanceRegionalrequirements MarNIS (Maritime Navigation and Information Services) ”State-of-the-art” Project requirements Web interfacefor registration and search Development of ”State-of-the-art” project databases WATERMAN (Waterborne transport)Systematic approach Projects, User requirements Sea-IT (Dynamic contingency information)Documents (technical, policy), Public opinion (media) DEMO DEMO DEMO DEMO

  9. Conclusion • Define and agree apon the ”ART” • Use a systematic approach to collect and systemize information • Develop (or use) interactive tools for registration and use of information • Establish system for updates and reuse of the information Thank you for your attention

More Related