Hi Florian
One approach might be to have the t-shirt size at the Product level, i.e. commercial. So your product specification would have characteristic spec
size (say), with list of spec values S, M, L, XL.
And you could then build commercial offerings to match these size values, each one with different price.
In the decomposition to Service, you would map the product size into the specific service compute characteristics.
Of course this assumes you want to hide the compute characteristics in the commercial layer.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Oct 29, 2021 12:11
From: Florian Kammermann
Subject: TMF633 T-Shirt size
Hi Dear tmforum
We try to model T-Shirt Size with TMF633
What is T-Shirt Size:
For example, we have a Service Specification which is "compute and memory".
This Service has the T-Shirt Sizes:
- S: 1 cpu / 128MB
- M 2 cpu / 256MB
- L 4 cpu / 512MB
- XL 8 cpu / 1024MB
We struggle to apply this to the TMF633 open API spec.
The following opportunities:
- use featureSpecification as T-Shirt Size and then express cpu/memory as featureSpecCharacteristic
- use specCharacteristic for expressing T-Shirt Size, then use also specCharacteristic to express cpu / memory. Express the relation between T-Shirt Size and cpu / memory with charSpecRelationship.
How would you model T-Shirt Size with TMF633?
------------------------------
Florian Kammermann
Swisscom AG
------------------------------