Open APIs

Expand all | Collapse all

TMF 633 :Lifecycle for service specification

  • 1.  TMF 633 :Lifecycle for service specification

    TM Forum Member
    Posted 23 days ago
    Edited by Rati Mehrotra 23 days ago
    Hi All,

    We are looking at the TMF 633 v4 document and have few queries around the lifecycle transitions in regards to service specification. Below is the lifecycle diagram from 633 v4 document.
    Few queries below on the state transitions
    1.  Should there be a state transition from Instudy→ Rejected : There could be a use case where specification study is done and found not suitable. Rather than moving it to "inDesign" and then "inTest" phase for rejecting it, the specification can  be rejected after "inStudy" phase itself.
    2. Should there be a state transition from Active->inTest/Design phase:  Active state is defined as "When a catalog element is in a "Active" status it means, it has been validated and tested, but it is still not available for customers" .  Does "Active" mean a "soft-launch" where s some Business validations will  be done on the particular specification. Is it possible that in the business testing,  some issue are identified which results in probably redesigning and retesting? Should we follow the entire lifecycle again in such scenarios and mark the current specification as "Retired"?
    3. Should there be a state transition from  intest → Launched :  Can there be a use case for moving directly from "inTest" to "Launched" where there is no "soft-launch" required?
    Thanks,
    Rati
    @Uma Lakshman

    ------------------------------
    Rati Mehrotra
    Telstra Corporation
    ------------------------------


  • 2.  RE: TMF 633 :Lifecycle for service specification

    TM Forum Member
    Posted 23 days ago
    Dear Rati,

    Unfortunately i could not find too much document about lifecycle management in TMF documents. I believe TMF lifecycle flow can be inspiring but you have not to restrict yourself on it and feel free to extend the class to meet your business need. Also you can have my opinion on your queries in the following:

    1. I think it make sense. Generally i think there should be also a delete state that is different with retired and rejected.
    2. We also have the same transition in our lifecycle manager. Specially this requirement raised by our business and the asked to be able to move a service from pre-launch (active) to inDesign.
    3. I think it's not necessary. Because currently you are able to move from inTest to Active to Launch. you can pass active state quickly :) No need to change your model and flow and put unnecessary complexity.


    ------------------------------
    Arash Zolfaghari
    Tecnotree
    ------------------------------



  • 3.  RE: TMF 633 :Lifecycle for service specification

    TM Forum Member
    Posted 20 days ago
    Thanks for your  response @Arash Zolfaghari

    ------------------------------
    Rati Mehrotra
    Telstra Corporation
    ------------------------------