Embed Size (px)
Citation preview
Dr.ing. Jan Tore Pedersen
ARKTRANS – What is it?� A multimodal framework architecture for transport� An official national framework endorsed by the
Parliament� Managed by ITS Norway as a commission from the
Ministry of Transport and transport authorities� A generic framework - independent of transport mode,
technology, and organisation� A framework to support transport policy:
• Intermodal transport (co-modality)• Interoperability
4 FP projectsInterPortInfoLog
5 FP projectsIntermodal Portal Door-2-Door
National projectsIntra, InfratransTransdata
TRIMConceptual information model for intermodal freight transport
ARKTRANSNational
framework architecture for
multimodal transport
Multimodalfreight transport
National projectsIBIS, MultiRIT, UNI HPI,… (many more)
5 FP projectsDoor-2-Door
THEMIS Traffic andtransport
Multimodal passenger transport
Contributions from�Research Council �Public Road Administration�Coastal Administration�Avinor (national air adm)�National Rail Administration�State Railways�Professional bodies�Service providers�ICT companies�Others
All transport modesPassenger and freight
transport
The ARKTRANS history and strategy
6 FP projectsMarNISFreightWiseEFFORTS
EU regionalViking
National projectsARKMIN, Vardø VTS, VITSAR, eFarled, INTRANS, … (more)
Other frameworks and standardsKAREN/FRAMETRIDENT, TransModelISO and CENUS National Architecture
7 FP projectsSmartFreightROSATTE
Driving Force in 2001
� Harmonisation between transport modes (road, railway, sea, air) is necessary• Transport is an intermodal matter• Same requirements (same users, same services, same information, etc.)• Same shortcomings/challenges (dangerous goods, management of intermodal
interfaces, etc.) � Harmonisation between freight and passenger transport is desirable
• The same transport means are used, on the same transport networks, and between the same endpoints
• Similarities with respect to preparation and planning and fleet management• Similarities with respect to the need for assistance and control services on-board the
transport means, traffic information needs, etc.
The work on ARKTRANS has proved that such harmonisation is feasible
Result: The ARKTRANS - Project
� Contractor: • The Norwegian Public Road Administration
� Technical manager/project leader: • SINTEF
� Founding• The Norwegian Public Road Administration• The Norwegian Coastal Administration• The Norwegian Civil Aviation Administration• The Norwegian National Rail Administration• The Norwegian State Railways• The Research Council of Norway
� User reference group
Framework Requirements
� Support multimodality (co-modality)� Be stable and easy to refine and expand� Be future-oriented (independent of current solutions)� Provide a total picture (include freight and passenger
transport)� Facilitate hiding of complexity (abstraction,
simplification)� Focus on interoperability (not on inner parts of systems)� Independent of technology
Independent of Local Ways
� Different regions and organisations have different solutions
� Some core responsibilities will always be present
� Support local differences through focusing on these responsibilities
Common
to all
Common
to all
C
A
B
B
A Common
to all
C
Responsibility centric frameworkA role represents unique set of responsibilities
Reference Model
On-board Support and Control
Transport Service Management
Transport S
ector Support
Transport DemandTransportation Network
Management
Emergency Management
Transportation Network Utilisation
Transportation Network Infrastructure Management
Regulation Enforcement
Transport Policy
Reference Model
On-board Support and Control
Transport Service Management
Transport S
ector Support
Transport DemandTransportation Network
Management
Emergency Management
Transportation Network Utilisation
Transportation Network Infrastructure Management
Regulation Enforcement
Metinfo
Towing service
EOS
SSN++NSWPSW
ENC
LRIT
AIS
PCS
Vessels, those in distress incl.
MRCC, Pollution response, MAS
Clearance, Enforcement
Nautical services,VTM
Reference Model
On-board Support and Control
Transport Service Management
Transport S
ector Support
Transport DemandTransportation Network
Management
Emergency Management
Transportation Network Utilisation
Transportation Network Infrastructure Management
Regulation Enforcement
Cargo
Freight transportmanagement
Infrastructure conditioninformation
Reference Model
On-board Support and Control
Transport Service Management
Transport S
ector Support
Transport DemandTransportation Network
Management
Emergency Management
Transportation Network Utilisation
Transportation Network Infrastructure Management
Regulation Enforcement
Cargo
Freight distributionmanagement
FreightVehicles
Traffic managementtowards individual vehicles
The Approach
Referencemodel
Functionalviewpoint
Informationviewpoint
Technical implementation
Overall conceptual
aspects
Logical aspects
Technicalaspects
Roles
Processviewpoint
• Top-down approach� Different abstraction or
complexity levels� Different viewpoints
• Technology independent
� For each responsibility domain of the Reference Model• Roles with responsibilities (one role belongs to just one domain)
� For each Role• Tasks that contributes to the fulfilment of the responsibilities
� Processes define how to fulfil responsibilities• How tasks are interact/collaborate (information exchange)
� Information elements
Roles
� Uses roles instead of stakeholders
� Represent unique sets of responsibilities
� Independent of organisation and local or regional ways of doing things
Stakeholder 1
Role A
Responsibility
Stakeholder 2
Stakeholder 3
Role B
Role D
Responsibility
Responsibility
Role C
Responsibility
Example FFFFFF
Transport Regulator
Transport Service Provider
Transportation Network Manager
Transport demandDefines the need for transport defined in
a Transport Execution PlanTransport follow up transport
Regulation EnforcementDevelops regulatory framework.
Ensures legal behaviour
Transport Service ManagementPublishes services.(Routes, cargo types, etc)
Executes transportBased on Transport Execution Plan.
Reports transport status
Transportation Network UtilisationProvides information about the current
and foreseen traffic situation
Transport User
Processes
Plan CompleteExecute
Select transport chainOrganise transport
Issue transport instructionsMonitor (detect deviations)
Issue proof of deliveryHandle invoices and payments
Handle claims
Traffic ManagerTransport Serv ice Prov iderTransport User Transport Regulator
Hazardious goods management
TEP
Planning NTS
Transport serv icemarketing
Order managementTEPNTS
Transport operationmonitoring
TES
TEP
TOS
TIS
NTS
TEP
Statistics and management/ Information administration
Taxes and customsmanagement
TEP
Statistics
STA
Transport serv icedemand definition
Bookingmanagement
TEP
Transport taskcontrol
TES
TIS
Transport tasktermination
STA
Transport networkutilisation
NTS
TOS
Com
plet
ion
Exe
cutio
nP
lan
nin
g
TSD
Example FFFFFF
Transport Regulator
Transport Service Provider
TransportationNetwork Manager
Transport User
Transport service
Service Area
Company
ServiceGoods Type
ServiceCharge
ServiceLoad Unit Type
EnvironmentalPerformance
IDService Category
DescriptionValid From
Valid ToIDSceduled?
Duration if notDecription
Detail
Service point(s)
TEP
Transport Item (s)
Origin andDestination Addresses
ServiceTerms
ServiceTiming
Consignment
Remarks
Contract
Unit Item
IDReady for execution
Transport service providerTransport user
IDCustomer reference
Delivery requirements# Transport items
Notify PartyReceiverSender
DeviationInformation
TES
Transport ItemID
Operation StatusStatus Time
TEP IDTime Stamp
Condition
TIS
Transport Item
StatusStatus timeTime stampDescription
Location
NTSNetwork
Condition
TrafficInformationIncident
Weather
Location Statistics
Estimated event start timeEstimeted ending time
Information SourceStatus
Reported time
ConditionDescription
Temperature
StatusInformation
TOS
Location
Transport Means IDStatus available ?
Time stamp
Actiual arrivelActual departureEstimated arrival
Estimated departure
Special remarksTime stamp
TEP
Transport Item (s)
Origin andDestination Addresses
ServiceTerms
ServiceTiming
Consignment
Remarks
Contract
Unit Item
IDReady for execution
Transport service providerTransport user
IDCustomer reference
Delivery requirements# Transport items
Notify PartyReceiverSender
Information elementsfor information exchange with
authorities
class Data Elements
Cargo o/v
+ CrewEffectItem
+ DGInfo
+ DutiableCrewEffects
+ GeneralDescriptionOfCargo
+ GerenralDescriptionOfDG
+ NumberOfPersonsOnBoard
+ Stores
+ StoresItem
Class and Certificates
+ ISMCertificate
+ ISSCertificateStatus
+ SaftetyManagmentCertificate
+ Certificate
+ CertificateCodeType
+ ClassAndCertificates
+ DeclarationOfHealthInfo
+ FlagRegistration
+ GasFreeCertificate
+ RegistrationCertificate
+ ShipClass
Crew Data
+ CrewOverview
+ CrewData
+ CrewMemberData
+ OnBoardDutyCodeType
+ OnBoardDutyCodeType_EPC2
+ OnBoardDutyType
+ ShortCrewMemberData
Dangerous Cargo Data
+ EmergencyDescription
+ DGSafetyDataSheet
+ PackingGroupType
+ PollutionCodeType
+ UNClassType
+ UNNumberType
General Cargo Data
+ ContainsDangerousGoods
+ BulkCargoHandling
+ CargoData
+ CargoItem
+ CargoItemOrigin
+ CargoStatisticsData
+ CargoType
+ GoodsType
+ LocationCodeType
+ NonCargoType
+ OnBoardLocationType
+ SpecialCargoDetails
+ TransportUnitInfo
Passenger Data
+ AssistanceRequests
+ ExtendedPassengerMemberData
+ PassengerData
+ SimplifiedPassengerMemberData
Security
+ CurrentShipSecurityLevel
+ ISPSAble
+ ISSCInformation
+ OtherSecurityInformation
+ SecurityInfoShipToShip
+ SecurityLevelInPort
+ SecurityLevelsInPreviousPorts
+ ShipToShipActivity
Core Data
+ ReportPosition
+ ReportPositionFix
+ ReportTime
+ Amount
+ CargoLocation
+ CertificateStatusType
+ ContainerLocation
+ ContectInfo
+ CoordinateType
+ CountryCode
+ FeederLocation
+ GenderType
+ IdDocumentType
+ Location
+ NameType
+ OtherLocation
+ Party
+ PersonIdDocumentType
+ Port
+ QuantityType
+ QuantityUnitType
+ ROROlocation
+ TankerLocation
+ ebXML Core Components
Clearance Status
+ ClearanceStatus
+ ClearanceStatusType
Port Entry/Departure Notifications (PEN/PDN)
Port Entry/Departure Profiles (PEP/PDP)
The MultiRIT project:Multimodal
information elementsfor travel information
pkg Conceptual Models (CIM)
CostFramework
+ PricingRules
+ Product
+ ProductOwner
+ ProductRetailer
+ TransportItemCategory
+ UsageRules
(from Conceptual Information Models (CIM))
Journey
+ Conditions
+ RoadJourneySegment
+ TransferSegment
+ AlertConditions
+ Changabi lityConditions
+ Journey
+ JourneySegment
+ PriceInfo
+ PTJourneySegment
+ TravelDocument
(from Conceptual Information Models (CIM))
Misc
+ Area
+ GeoLocation
+ GeoReference
+ Location
+ Point
+ RoadProperty
+ Contact
+ LocalTime
+ TransportMeans
+ TransportServiceProvider
(from Conceptual Information Models (CIM))
Preferences
+ Agreement
+ AmbientPreferences
+ EnvironmentalPreferences
+ Preference
+ TransportItem
+ Accessibil ityPreferences
+ BusinessRelation
+ FoodPreferences
+ OptimisingCriteria
+ PaymentPreferences
+ PlacementPreferences
+ PreferenceProfile
+ ProductPortefolio
+ TransferPreferences
+ TransportDemand
+ TransportModePreferences
+ TransportPreferencesRank
+ TransportUser
+ ServicePreferences
(from Conceptual Information Models (CIM))
Serv iceAndDev iation
+ Accessibili ty
+ Deviation
+ Restriction
+ Service
(from Conceptual Information Models (CIM))
Terminal
+ StopPoint
+ Terminal
+ TerminalAccessPoint
+ Transfer
(from Conceptual Information Models (CIM))
Trav elDataTypes
+ AccessType
+ Address
+ AlertType
+ AmbientCategory
+ BDBReferenceType
+ Changeabil ityType
+ LocationName
+ NVDBreferenceType
+ OptimizeCriteria
+ PlacementType
+ RequiredType
+ RoadPropertyType
+ RoutePreferenceType
+ SegmentType
+ TransferFrom
+ TransferType
+ FoodType
+ PreferenceRestrictionType
+ TransportType
+ IATAlocations
+ AreaCodeType
+ CombinationType
+ CountyCodeType
+ DirectionType
+ LanguageType
+ NodeType
+ QualityType
+ SeverityType
+ TerminalType
+ TransportModeType
+ Publ icTransportType
+ TerminalReference
+ LineReference
+ TripReference
+ DescriptionType
+ AccessibilityTypes
+ DeviationTypes
+ NotUsed
+ RestrictionTypes
+ ServiceTypes
(from Conceptual Information Models (CIM))
TripPattern
+ LegPattern
+ Line
+ StopPattern
+ StopPatternInfo
+ TimeSchedulePattern
(from Conceptual Information Models (CIM))
TripTimeTable
+ Arrival
+ CombinedService
+ Date
+ Departure
+ Leg
+ Remark
+ TerminalStop
+ Timetable
+ StopSequence
+ Trip
(from Conceptual Information Models (CIM))
Service Oriented Architecture (SOA)
Summing Up� ARKTRANS
• Has proven its value in Norwegian and EU projects• Provides a simplified and structured specification of the transport
sector by means of� A top-down approach� Formal methods � Generic specifications
• Harmonised specification of the transport sector across � Transport modes� Transport types (freight or person transport)� Local ways of doing things
• A “tool” for � Common understanding� Interoperability between systems� Discussions and specifications when new concepts and solutions are to
be defined
Reduces Complexity
Harmonised specifications for:�All transport modes�Freight and person transport�All transport services (and related transport operations)
���
����������� ���
����
������
�����������������
������
����������������
���
������
����������������
� ��
������
����������������
���
���������� ���
����
������
�����������������
������
���������
�������
���
������
����������������
� ��
������
���������
������
������ ��
�������
������
