1 / 14

ARKTRANS The Norwegian System Architecture Framework for Multimodal Transport Systems

ARKTRANS The Norwegian System Architecture Framework for Multimodal Transport Systems. Marit Natvig SINTEF Telecom and Informatics. The ARKTRANS project. Phase1: September 2000 – September 2001 Phase 2 : January 2002 – December 2004 Participants

Download Presentation

ARKTRANS The Norwegian System Architecture Framework for Multimodal Transport Systems

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. ARKTRANSThe Norwegian System Architecture Framework for Multimodal Transport Systems Marit NatvigSINTEF Telecom and Informatics

  2. The ARKTRANS project • Phase1: September 2000 – September 2001 • Phase 2 : January 2002 – December 2004 • Participants • The Norwegian Public Road Administration (contractor) • The Norwegian Coast Administration • The Norwegian Civil Aviation Administration • The Norwegian National Rail Administration • The Norwegian State Railways • Telenor F&U • Ergo Solution • Transportbedriftenes Landsforening (professional body) • The SINTEF Group (technical manager/project leader) • User reference groups • Brings further the work done in the ARKMIN project

  3. Overall background • Harmonisation between transport modes (road, railway, sea, air) • Transport is an inter modal matter • Same users, services, information, requirements etc. • Same shortcomings (dangerous goods, management of inter modal interfaces, etc.) • Harmonisation between freight and passenger transport • Same transport means, transport networks, and endpoints

  4. Background:Problems related to information flow • The same information is requested by authorities, service users, service providers, transport users, etc. However: • Information cannot be transferred electronically between actors • The same information must be registered manually several times • Faults are introduces • Dangerous cargo in not handled according to the regulations • Cargo cannot be tracked on its way in the transport chain • Transport chains are not managed in a coordinated way (status, ETA, etc.)

  5. Background:Problems related to efficiency and security • Lack of services or information that can improve safety or efficiency, or the available information is not utilised when transport is planned and accomplished • Availability of dynamic information must be improved • The utilisation of the transport networks must be improved • Information must be provided and presented in a way that fits the user • Route and traffic information for several transport modes must be combined and made available • Several actors are involved in freight as well as personal transport. However, the coordination is not as well as wished • Same needs with respect to fleet management and planning • Same needs with respect to on-board assistance and control

  6. System Framework Architecture - Content Conceptual level Reference Model Why? Roles Logical level Functional Model Information Model What? Technical Level Physical Model Communication Model How? • Multiple aspects and levels of abstraction • Structured methodology/formal specification • Build on existing results/best practise • Gradual/iterative development based on demonstrator outcomes/Input from user reference groups

  7. System Framework Architecture - Content ARKTRANS Reference Model Transport Demand Management Transport Service Management Terminal Management Management Transport Network On-board assistance & control

  8. System Framework Architecture - Content Conceptual level Reference Model Why? Roles Logical level Functional Model Information Model What? Technical Level Physical Model Communication Model How? • Functional models for each area in the reference model

  9. Example of System Framework Architecture Content : Top level of functional model for Transport Network Management Styring av transportinfrastruktur Transport Network Management Trafikk-avvikling Traffic management Forvaltning av transport- Infrastrukturen Transport network maintenance and planning Sikkerhet og miljøforhold Safety and environmental issues Håndhevelse av Regelverk Regulation enforecment Betalings-formidling Payment services

  10. Example of System Framework Architecture Content : Functional model for Traffic Management Traffic Management Traffic Control Incident Management Traffic Monitoring Traffic data manage-ment Traffic assess-ment Traffic condition monitoring Demand manage-ment Equipment and infrastr. mangement Route and navigation guidance Detection and identi-fication of incident Actions handling incident Preliminary version Decomposition not completed Traffic information establishment Traffic information administration Obstructions/flowting objects Met./oceanographic conditions Regulations and recommendations Pilot booking Sailing conditions Traffic situation Arrival administration

  11. System Framework Architecture - Content Conceptual level Reference Model Why? Roles Logical level Functional Model Information Model What? Technical Level Physical Model Communication Model How? • Information Model based on TRIM • Defines the information required by the defined functionality

  12. Example of System Framework Architecture Content : Met./oceanographic information model Ice_condition Visibility Method_used Location Water_level_zone ice thickness Horizontal visibility EquipmentID Location code Created date ice type Visibility integration time Equipment type Location name Expired date Ice condition integration time Link to description Accuracy Range Method Delay Offset SeaCurrent Description Current direction Current speed Fairway_object Current depth Average from Average to Current integration time Tide_gauge Metocean_condition Timestamp Meteorological_statement Valid from Name Timestamp Statement text Gauge status Calc timestamp Statement type Description Wave Water_level Wave mean direction Wave peak direction Total water level Swell direction Tidal water level Windsea direction Surge Direction convention Water level integration time Significant wave height Max wave height Wind Water_condition Swell height Air_condition Wind sea height Wind direction Sea temperature Wave mean period Wind speed Air temperature Salinity Wave peak period Gust direction Humidity Salinity integration time Swell period Gust velocity Air pressure Sea temp integration time Wind sea period Wind height Pressure tendency Depth Wave integration time Wind integration time Air temp integration time Avarage from Max wave hight integration time Gust integration time Humidity integration time Avarage to

  13. System Framework Architecture - Content Conceptual level Reference Model Why? Roles Logical level Functional Model Information Model What? Technical Level Physical Model Communication Model How? • Communication model that defines messages and communication solutions • Messages defined by the means of elements from the information model

  14. Example: Exchange of met./oceanographic messages Manual observations Radar measurements Buoy measurements • ARKTRANS Meteorological Message • Location information (named, area, point, …) • Method used information (calculation/observation, equipment used, source, etc.) • Meteorological info (wave, current, water layer, etc.) Calculated prognosis based on models The user may request information of a specific type (calculation, observation, …) The user will receive the same message format in all cases The message describes how the data is generated

More Related