Hi Rosalin,
I don't know if this relevant for you, but I will give you my view on this.
The attribute to use for your use case is productOfferingTerm. A Term is basically a named duration.
Named durations can easily be used in calculations involving time. Calculating a expectedCompletionDate is definitely one of the calculation using an "expectedDeliveryDelay".
Common other date related calculations could involve minContractDuration used during termination processes. or indeed various SLA timers like maximumResponseTime, maximumRestorationTime, ...
I hope this helps and is still relevant.
Regards
------------------------------
Koen Peeters
Ciminko SA
------------------------------
Original Message:
Sent: Feb 16, 2026 09:49
From: Rosalin Panda
Subject: Best practice for modeling Fulfillment Lead Time in TMF620 to support TMF622 Expected Completion Dates
Dear Community,
Do you have any suggestion for us.
regards,
Rosalin
------------------------------
Rosalin Panda
Deutsche Telekom AG
Original Message:
Sent: Jan 27, 2026 09:35
From: Rosalin Panda
Subject: Best practice for modeling Fulfillment Lead Time in TMF620 to support TMF622 Expected Completion Dates
Hi everyone,
I am looking for the standard way to define "Fulfillment Time" at the Catalog level (TMF620) so that it can be used by an Order Management System to calculate the expectedCompletionDate in TMF622.
Since there isn't a native "leadTime" attribute in the Product Specification, is it recommended to use a ProductSpecCharacteristic (e.g., "delivery_days"), or should this be handled via an SLA entity reference within the ProductOffering? I would appreciate seeing how others have mapped catalog-driven fulfillment durations to the ordering process.
Thanks.
Rosalin
------------------------------
Rosalin Panda
Deutsche Telekom AG
------------------------------