Logistics use cases

[RaggedStaff]

Platform POST's a list of Shipments to Logistics platform & expects a response including Route information for all shipments

A Shipment is a breakdown (or sum-up) of Ordered Products. - "A group of ordered items that have to be shipped together."

E.G. A Hub accepts 10 Customer Orders, from 4 Suppliers
Hub raises 4 Purchase Orders (1 for each supplier) each comprising of parts of multiple Customer Orders
Each Supplier has 1 shipment to the Hub
The Hub then recombines these 4 shipments into 10 shipments to deliver to the Customers (1 Shipment -- n:n -- 1 Order)
The Hub then requires a route to deliver the 10 shipments (Customer Orders)

[RaggedStaff]

For a Shipment:

We need:

• Origin (1 and only 1) -- time (window) & physical place
• Destination (1 & only 1) -- time (window) & physical place
• Products included in the Shipment (including a link to the OrderLine, maybe with a full/partial fulfilment indicator)
• Shipment dimensions (size, weight, volume?)
• Constraints (e.g. min/max temp, frozen etc..) - properties from Product (see Implement logistics data #70 ) - let's add humidity requirement

[RaggedStaff]

@Alcoz to review other ontologies & report back 17th Oct.

[Alcoz]

@RaggedStaff @simonLouvet @lecoqlibre

Regarding our use-case and the needs of representing vehicule and logistic services, I would propose the schema above as a first draft that could be implemented easily in the ontology and could answer logistic use-case required for our demo in two weeks. I found other existing ontologies that could fit, but there are not maintained anymore or there are maybe too complex for start but I recorded them in a doc that we could use afterwards.

I would like your comment to know if it can fit to the use-case of everyone in a first place

[simonLouvet]

physicalProduct can have several stocks which are transported by different shippemnt it seems to me. a stock can even be divided into several for transport. I can't see how to link shippment and stock other than to say that a shipment carries a quantity of physical product. I think it's a shame that refrigerated and freeze are managed by specific attributes rather than a texonomy.

[Alcoz]

@simonLouvet

physicalProduct can have several stocks which are transported by different shippemnt it seems to me. a stock can even be divided into several for transport. I can't see how to link shippment and stock other than to say that a shipment carries a quantity of physical product.

I'm not okay with the fact that a physical product have several stocks. For me, a physical product is the real transposition of a product and it can be at one place and have one stock. If a subpart of physical product is moved, then it leads to two physical product with two stocks (one of the moved part, and one of the staying part).

I think it's a shame that refrigerated and freeze are managed by specific attributes rather than a texonomy.

I think you right, however we implemented this at first when we added the missing properties for logistics to describe supplied product information. So do we modify the ontology to add this kind of information in the taxonomy on the next update or are we doing this afterwards ? I ok with both but I need an answer of the group

[Alcoz]

About Vehicule and Physical Place description, disponibility time interval would be interesting to have to know when vehicule are available and physical place are opened to receive or delivering order

[simonLouvet]

I'm not okay with the fact that a physical product have several stocks. For me, a physical product is the real transposition of a product and it can be at one place and have one stock. If a subpart of physical product is moved, then it leads to two physical product with two stocks (one of the moved part, and one of the staying part).

the ontology schema specifies that the physical product is constituedBy 0 to many realStock
https://docs.dfc-standard.org/dfc-standard-documentation/semantic-specifications/business-ontology

[Alcoz]

That strange about my comprehesion but ok, so yes the Shipment should be connected to a Stock

[RaggedStaff]

In the call today we agreed:

1. Shipment will link to RealStock
2. We will keep the simple booleans for Refrigerated & Frozen on Vehicle for now. Until we have valid Use Cases, we don't think it's necessary to make this more complex.
3. @Alcoz will finish reviewing other logistics ontologies & feedback on any recommended improvements/links.

@simonLouvet - can you confirm if this will work for you, for now ?

[Alcoz]

I discussed with @simonLouvet and he reminded me that it would be interesting/necessary to have the opening time of physical place and/or the avaibility time of the vehicle. With all the information gathered I will propose a revised diagrams and will need feedback.

[Alcoz]

I updated the schema :

• The Shipment is linked to the Stock
• I add the class schema.org#OpeningHoursSpecification (https://schema.org/OpeningHoursSpecification) linked to PhysicalPlace with isOpenedDuring and Vehicle with isAvailableDuring. Not sure about the name of the properties, I would be interested of having feedback. On the class https://schema.org/LocalBusiness, they call the property OpeningHoursSpecification that is linked to a concept OpeningHoursSpecification, which is not really interesting in my opinion.

And, an other question, are you ok with reusing a class from schema.org ?

@simonLouvet @RaggedStaff @lecoqlibre

[RaggedStaff]

* I add the class `schema.org#OpeningHoursSpecification` (https://schema.org/OpeningHoursSpecification) linked to PhysicalPlace with `isOpenedDuring` and `Vehicle` with `isAvailableDuring`. Not sure about the name of the properties, I would be interested of having feedback. 

I agree with you naming suggestions @Alcoz , I think perhaps isOpenDuring would be better English (present tense, not past)? I'm always slightly confused about tenses on concepts.

An alternative would be isOpenForDuration (& then I guess isAvailableForDuration) but I don't think that quite captures it.

And, an other question, are you ok with reusing a class from schema.org ?

Yes, fine for me.

[Alcoz]

I will add IsOpenDuring following your suggestion