- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Experts,
I am currently working on the Product Catalog in SOMT focusing on Telecommunication module. I want to create a brand-new Product Model and then Product Category and so on..I want to make sure CMDB and CI's are accounted for and auto maps when product ordering takes place.
What is the best practice and steps i need to follow to configure? I am using OOB design, however, have to create a particular product model relates to products.
Apology if the question is confusing!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @D Trivedi,
Not confusing at all, this is a common design question. A build order that has worked well, staying OOB:
1. Specifications first (design time). In the Product Catalog, create the Resource Specifications, then the Resource-Facing Service Specs (RFSS), then the Customer-Facing Service Spec (CFSS), then the Product Specification with its characteristics. Each product specification maps to one service specification.
2. Product Model. Create it under Customer Service > Products > Product Models (needs the Model Management plugin and model_manager role). Pick the right model type (Service for most telecom services, Hardware for CPE) and set the CI class it should create, so CIs are consistent and assurance tools recognise them. Reuse an existing model where possible rather than creating one per offering.
3. Link the Product Specification to that Product Model, so the sold product and install base items created at fulfilment line up with the model and CI class.
4. Product Offering + Category. Create the offering (price, terms) on top of the specification and place it in your catalog category. Bundles reference component offerings.
5. Fulfilment. When the order is approved, product inventory and the install base item hierarchy (product > CFS > RFS > resource) are created from the specification via flows. Check the OOB fulfilment flow on your release to see where the model / CI class is used when creating CIs, and decide which CI relationships you need between levels (needed for service impact and alerts to reach the customer).
6. Test end to end with one offering: quote > order > fulfil, then confirm sold product, install base items and CIs (with relationships) were created as expected.
A couple of questions to point you more precisely:
- Which release and SOMT / Product Catalog plugin versions are you on?
- Is the new model for a service (e.g. broadband, SD-WAN) or for physical equipment?
- Is CSM/assurance (Proactive Customer Service Operations, Event Management) in scope? That decides how much CI relationship modelling you need.
If this helps, please mark it helpful, and accept it as the solution if it resolves your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @D Trivedi,
Not confusing at all, this is a common design question. A build order that has worked well, staying OOB:
1. Specifications first (design time). In the Product Catalog, create the Resource Specifications, then the Resource-Facing Service Specs (RFSS), then the Customer-Facing Service Spec (CFSS), then the Product Specification with its characteristics. Each product specification maps to one service specification.
2. Product Model. Create it under Customer Service > Products > Product Models (needs the Model Management plugin and model_manager role). Pick the right model type (Service for most telecom services, Hardware for CPE) and set the CI class it should create, so CIs are consistent and assurance tools recognise them. Reuse an existing model where possible rather than creating one per offering.
3. Link the Product Specification to that Product Model, so the sold product and install base items created at fulfilment line up with the model and CI class.
4. Product Offering + Category. Create the offering (price, terms) on top of the specification and place it in your catalog category. Bundles reference component offerings.
5. Fulfilment. When the order is approved, product inventory and the install base item hierarchy (product > CFS > RFS > resource) are created from the specification via flows. Check the OOB fulfilment flow on your release to see where the model / CI class is used when creating CIs, and decide which CI relationships you need between levels (needed for service impact and alerts to reach the customer).
6. Test end to end with one offering: quote > order > fulfil, then confirm sold product, install base items and CIs (with relationships) were created as expected.
A couple of questions to point you more precisely:
- Which release and SOMT / Product Catalog plugin versions are you on?
- Is the new model for a service (e.g. broadband, SD-WAN) or for physical equipment?
- Is CSM/assurance (Proactive Customer Service Operations, Event Management) in scope? That decides how much CI relationship modelling you need.
If this helps, please mark it helpful, and accept it as the solution if it resolves your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Thank you, @Kailash Bhange Much appreciated.
1. I am on Australia release.
2. Product Model will consist of both Service as well as physical equipment. Also, what is the best product model option for services like warranty, maintenance etc..?
3. Proactive CSO is not in scope, only TSM, SOMT, FSMT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
@D Trivedi
Was the information given helpful for you, can you please let me know if you are still looking for any help.
Thanks!
