• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Logistic Service Profiles for Interoperability
 

Logistic Service Profiles for Interoperability

on

  • 280 views

 

Statistics

Views

Total Views
280
Views on SlideShare
276
Embed Views
4

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 4

http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Logistic Service Profiles for Interoperability Logistic Service Profiles for Interoperability Presentation Transcript

    • IMPROVING SECURITY THROUGH VISIBILITYTechnical implementation and standardization needs in system based supervision
    • Premises■ Improve interaction between actors in a supply chain■ Complete supply chain visibility■ Improved risk analysis by increased quality in information■ Profiles for logistic services ● This presentation will make an special focus in this last pointName • Institution • Conference/Event • Date
    • Introduction■ Current situation in logistics ● Current integration efforts are too time consuming and are mostly performed in the context of framework contracts. ● Many actors, many “languages”, many IT-Systems ● Data ownership? Data availability?■ Future expected situation ● Logistic service profiles to model logistic services ● Global overview of information’s flow in dynamic logistic supply chain ● Data extracted from owners -> reliability ● Data availability according to your processes and profiles ● Common interfaces and data model to facilitate interoperability (standardization)Name • Institution • Conference/Event • Date
    • Introduction■ Data pipeline (Data sharing and data capturing in the CASSANDRA architecture)Name • Institution • Conference/Event • Date
    • Introduction■ An ideal/future world: ● Common interfaces for supply chain visibility ● Common Data model as a common language ● Technological State of the Art■ Build it on the top of the CASSANDRA’s architecture ● Specify a set of interfaces for a common data pipeline ● Data pipeline offer direct information from involved stakeholders ● Currently designing how to share information, and which information to share ● Actors expose their logistic services modeled with profiles■ How to achieve this? Profiles are the key of this presentationATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Modeling with profiles■ What do we want to model with profiles? ● Actor’s activities/services ● As customers or as providers of services ● Specific actor’s configuration for each service■ What is a Profile? DHL as a Provider for Transport of Goods from Madrid to Paris Company Role Activity Parameter ParameterName • Institution • Conference/Event • Date
    • Modeling with profiles■ So, you have different options to configure your profiles regarding services (transport, storage) and parameters (places, goods, etc). ● Talkin the same language for interoperability.■ Common data model ● Core reference model: ● Activities, objects, relations, etc. Concepts: transport, storage, trucks, place of acceptance .... ● Logical inferences: road transport needs a vehicle and a place for acceptance and delivery (configuration parameters) ● Specific models ● Truck’s companies in France model: ● Not allowed goods of more than 20.000KG ● Spanish’s legislation: ● Containers of type “SEC” can transport dangerous goods■ Now we have profiles to expose activities using the same language. But, how to implement it?ATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Using profiles■ Which models are you going to use for your profiles? Specific communities implements specific models: ● CASSANDRA community ● Or just create your own community...ATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Using profiles ● Behind profiles: complex ontologies and semantic models ● But actors does not need to know about this complexity ● User friendly methodology to configure your profiles. ● No need to be an expert on IT-Technologies ● Just expose your business activities in a common (comprehensible) language Other configuration options are possible: type of cargo, transport mean, dates, etc…ATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Using profiles■ Now we have profiles that configures, easily, actor’s activities■ Data models to use the same language (to configure)■ Communities to “pack” data models■ But... What about interoperability? We have profiles using a common language, How could they collaborate?ATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Profiles matching■ Profiles have an specific role that determinates if the profile is requesting or offering a service■ Semantic matching between customer and provider profiles that make compatible the operationATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Profiles matching■ The common data model determinate compatibility between concepts. ● Places compatibility is one of the “big issues” ● Madrid belongs to Europe (semantic techniques) Cat S.A as a customer for Transport of Boxes from Madrid to Paris DHL as a Provider for Transport of Goods through EuropeATOS – Dashboards/ITLivingLab Meeting – Julio - Madrid
    • Profiles matching■ Incompatible profiles ● Special difficulties for compatibility about places ● The data model specifies that boxes beyond to goods concept Cat S.A as a customer for Storage of Boxes in Istanbum DHL as a Provider for Transport of Goods through EuropeName • Institution • Conference/Event • Date
    • Profiles matching■ Implementation of compatibility between profiles ● Again, the options are controlled from the data models of your environment/communityName • Institution • Conference/Event • Date
    • Profiles matching■ Profiles also configure information for execution ● How to invoke the activity? ● Service’s endpoint (protocol, path, port) ● Business requirements ● Document/Interface to interchange data ● XML, XSD, EDI message ● Document/interface implementation guideline ● Ex: according to “common framework for transport v0.3” about transport orders. Include information about detailed informationName • Institution • Conference/Event • Date
    • Profiles matching■ Finally, thanks to the compatibility between profiles: ● Operations can be executed ● Data is shared (horizontally) between actors in a common language ● Great opportunity for OpenLinkedData ● Data is captured (vertically) between actors and customs in a common language ● Data Quality ● Data reliabilityName • Institution • Conference/Event • Date
    • ■ Data sharing between profiles. Acsesible by other communities Business Customs Customs Business Dashboard Dashboard Dashboard Dashboard CASSANDRA 1 CASSANDRA 2 Profile Profile 1 2 Same Object Data Sharing data synchronized ExportName • Institution • Conference/Event • Date
    • Summary■ We configure profiles to model business in a common understandable language easy to use■ Communities could determinate the data models to be used■ Expose your specific activities that could interoperate with other actors. ● Profiles also include information for execution■ Expose (to customs) a data capture interface to allow the access of the information (during a process) ● Regarding your configured profiles.Name • Institution • Conference/Event • Date
    • Conclusions■ Expected impact ● Business: dynamic logistic chains with sustainability increase ● Business: facilitate the introduction of new users participating in a supply chain■ IT systems: transaction - versus business document oriented system■ Interoperability Implementation Guides: based on profiles, including external requirements■ Compliance: declaration systems (including Single Window applications) versus improved risk analysis based on monitoring (piggy backing)Name • Institution • Conference/Event • Date
    • ContactThank you for your attention. Any questions? Jose Gato Luis <jose.gato@atosresearch.eu> Wout Hofman <wout.hofman@tno.nl>