Open APIs

Expand all | Collapse all

TMF620 | Product offer modelling for device variants

  • 1.  TMF620 | Product offer modelling for device variants

    TM Forum Member
    Posted Jul 20, 2021 09:52
    Dear TM Forum,

    We are looking for your guidance about the product offer modelling for the device variants.
    It is a very common use case to define multiple variants of a mobile device, based on some properties like color, storage etc.

    What is the TMF recommended modelling for these variants?

    ------------------------------
    Amita Kuvalekar
    Sterlite Technologies Limited
    ------------------------------


  • 2.  RE: TMF620 | Product offer modelling for device variants

    Posted Jul 21, 2021 10:08
    Hi,

    I hope this may help you to model you product offering ..

    Page 42 of TMF620 Product Catalog Management API REST Specification R19.0.0
    productSpecCharacteristic

    A list of product specification characteristics
    (ProductSpecificationCharacteristic [*]). A characteristic quality or distinctive
    feature of a ProductSpecification. The characteristic can be take on a
    discrete value, such as color, can take on a range of values, (for example,
    sensitivity of 100-240 mV), or can be derived from a formula (for example,
    usage time (hrs) = 30 - talk time *3). Certain characteristics, such as color,
    may be configured during the ordering or some other process.

    Thanks,
    Hanumantha Marikanti.
    Director Saralam Technologies & Open API enthusiast.


    ------------------------------
    Hanumantha Marikanti
    Saralam Technologies
    ------------------------------



  • 3.  RE: TMF620 | Product offer modelling for device variants

    TM Forum Member
    Posted Jul 22, 2021 17:01
    The ODA Transformation Guide Collaboration Project is putting the finishing touches on a Product Modelling guide focused on common commercial-centric modelling patterns, especially Product Offerings.  There are some examples that describe device modelling.  Not surprisingly, there is no one "right" way to model but I hope that we can align on common patterns that are fit for a particular use case or solution constraints.

    The guide, IG1261, should be published in August. Would welcome feedback on the guide once it becomes available.

    ------------------------------
    Greg Herringer
    IBM Corporation
    ------------------------------