TM Forum Community

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

Hi Jan

Firstly, welcome to TM Forum. Wishing you every success in making the most of TMF assets.

For your specific question, when creating an information model, we need to account for things that are common to all items in a specific class of entity. A physical resource, represents a tangible "thing" (customer equipment, network element, etc.), and the corresponding specification defines those "thing"s in a resource catalog. It is fair to say that physical resources are generally purchased from suppliers, and so the sku (or equivalent) becomes a common attribute to all physical resources.

Hope it helps

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

Hi Jan

Firstly, welcome to TM Forum. Wishing you every success in making the most of TMF assets.

For your specific question, when creating an information model, we need to account for things that are common to all items in a specific class of entity. A physical resource, represents a tangible "thing" (customer equipment, network element, etc.), and the corresponding specification defines those "thing"s in a resource catalog. It is fair to say that physical resources are generally purchased from suppliers, and so the sku (or equivalent) becomes a common attribute to all physical resources.

Hope it helps

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

Hello Jan,

Please allow me to add additional context to the excellent explanation Jonathan has given. 
Physical resources (and Logical resources) are modelled using the Resource Spec Entity in the model. These Resource Specs need to have a  Product Spec. In the example you have provided Router is a Resource Spec (Physical) and needs to have a  Product Spec (Internet Service).
The Make & Model, Serial ID etc are attributes or characteristics of the Router Resource Spec and in the instance purchased by the customer, these values are  filled in during the selling or fulfillment process.

Hope this helps. 

Hi Jan

Firstly, welcome to TM Forum. Wishing you every success in making the most of TMF assets.

For your specific question, when creating an information model, we need to account for things that are common to all items in a specific class of entity. A physical resource, represents a tangible "thing" (customer equipment, network element, etc.), and the corresponding specification defines those "thing"s in a resource catalog. It is fair to say that physical resources are generally purchased from suppliers, and so the sku (or equivalent) becomes a common attribute to all physical resources.

Hope it helps

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

Hello Jag,

thanks a lot for joining this conversation.

Does this mean that for me to be able to instantiate a `Router` (defined by ResourceSpec in TMF 634) into a `Resource` (defined in TMF639), I need `ProductSpec`? Which TMF is this?

And to make it more complicated -- how does the `ResourceCandidate` come into play?

Thanks and have a great day.

------------------------------
Jan Stastny
CETIN

Original Message:
Sent: Dec 07, 2023 06:51
From: Sri-Jagadish (Jag) Baddukonda
Subject: TMF634 - sku as attribute vs characteristic

Hello Jan,

Please allow me to add additional context to the excellent explanation Jonathan has given. 
Physical resources (and Logical resources) are modelled using the Resource Spec Entity in the model. These Resource Specs need to have a  Product Spec. In the example you have provided Router is a Resource Spec (Physical) and needs to have a  Product Spec (Internet Service).
The Make & Model, Serial ID etc are attributes or characteristics of the Router Resource Spec and in the instance purchased by the customer, these values are  filled in during the selling or fulfillment process.

Hope this helps. 

------------------------------
Sri-Jagadish (Jag) Baddukonda
Bell Canada

Original Message:
Sent: Dec 07, 2023 02:21
From: Jan Stastny
Subject: TMF634 - sku as attribute vs characteristic

------------------------------
Jan Stastny
CETIN

Original Message:
Sent: Dec 06, 2023 15:08
From: Jonathan Goldberg
Subject: TMF634 - sku as attribute vs characteristic

Hi Jan

Firstly, welcome to TM Forum. Wishing you every success in making the most of TMF assets.

For your specific question, when creating an information model, we need to account for things that are common to all items in a specific class of entity. A physical resource, represents a tangible "thing" (customer equipment, network element, etc.), and the corresponding specification defines those "thing"s in a resource catalog. It is fair to say that physical resources are generally purchased from suppliers, and so the sku (or equivalent) becomes a common attribute to all physical resources.

Hope it helps

------------------------------
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: Dec 06, 2023 10:38
From: Jan Stastny
Subject: TMF634 - sku as attribute vs characteristic

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

#OpenDigitalArchitecture

------------------------------
Jan Stastny
CETIN
------------------------------

If it is is a CPE it need not be instantiated  via 639.

If it is UNI or a CE / PE router, then yes. 

But in the Product model they should  be modelled as an RS with the appropriate relationships to the other entities like PS and RFSS (if necessary).

These is a very good document (IG1233)on modelling guidelines written by Dave Milham and a few others. 

Regards,

Jag

------------------------------
Sri-Jagadish (Jag) Baddukonda
Bell Canada

Original Message:
Sent: Dec 07, 2023 11:00
From: Jan Stastny
Subject: TMF634 - sku as attribute vs characteristic

Hello Jag,

thanks a lot for joining this conversation.

Does this mean that for me to be able to instantiate a `Router` (defined by ResourceSpec in TMF 634) into a `Resource` (defined in TMF639), I need `ProductSpec`? Which TMF is this?

And to make it more complicated -- how does the `ResourceCandidate` come into play?

Thanks and have a great day.

------------------------------
Jan Stastny
CETIN

Original Message:
Sent: Dec 07, 2023 06:51
From: Sri-Jagadish (Jag) Baddukonda
Subject: TMF634 - sku as attribute vs characteristic

Hello Jan,

Please allow me to add additional context to the excellent explanation Jonathan has given. 
Physical resources (and Logical resources) are modelled using the Resource Spec Entity in the model. These Resource Specs need to have a  Product Spec. In the example you have provided Router is a Resource Spec (Physical) and needs to have a  Product Spec (Internet Service).
The Make & Model, Serial ID etc are attributes or characteristics of the Router Resource Spec and in the instance purchased by the customer, these values are  filled in during the selling or fulfillment process.

Hope this helps. 

------------------------------
Sri-Jagadish (Jag) Baddukonda
Bell Canada

Original Message:
Sent: Dec 07, 2023 02:21
From: Jan Stastny
Subject: TMF634 - sku as attribute vs characteristic

------------------------------
Jan Stastny
CETIN

Original Message:
Sent: Dec 06, 2023 15:08
From: Jonathan Goldberg
Subject: TMF634 - sku as attribute vs characteristic

Hi Jan

Firstly, welcome to TM Forum. Wishing you every success in making the most of TMF assets.

For your specific question, when creating an information model, we need to account for things that are common to all items in a specific class of entity. A physical resource, represents a tangible "thing" (customer equipment, network element, etc.), and the corresponding specification defines those "thing"s in a resource catalog. It is fair to say that physical resources are generally purchased from suppliers, and so the sku (or equivalent) becomes a common attribute to all physical resources.

Hope it helps

------------------------------
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: Dec 06, 2023 10:38
From: Jan Stastny
Subject: TMF634 - sku as attribute vs characteristic

Hello,

We are new to TMF and are trying to digest the whole concept of the ODA.

We are wondering, why for example the `sku` on `PhysicalResourceSpecification` is represented as direct attribute TMF634_ResourceCatalog/TMF634-ResourceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF634_ResourceCatalog instead of using the `ResourceSpecificationCharacteristicValue` and the related schema.

Thanks a lot for all the inputs!

#OpenDigitalArchitecture

------------------------------
Jan Stastny
CETIN
------------------------------