Hello Dileep, Jonathan
I've the same approach than Jonathan and basically service ordering drives service inventory state (except with TMF640 use)
Suppose you want to create a new service (ServiceSpec Xx) in inactive mode.
You trigger a Service order (641) with an item 1 with action add & serviceSpec= Xx & service.state=inactive
Your SOM acknowledges this (Service Order #100 is created) and proceed --> Service #45 is created.
In TMF 638 you'll will see Service #45 in state inactive and in RelatedServiceOrderItem you can see that ServiceOrder #100 - Item1 was used to create the service
Later you want to active this service
You trigger another Service Order with an item 1 with action change & service.id=45 & service= active
Your SOM acknowledges this (Service Order #101 is created) and proceed --> Service #45 is changed.
In TMF 638 you'll will see Service #45 in state active and in RelatedServiceOrderItem you can see that ServiceOrder #100 - Item1 was used to create the service and ServiceOrder #101 - Item1 was used to modify the service (state).
Note that you have also TMF640 to directly create/modify your service via REST operation directly on the service and in this case the requester indicate wished state directly in the POST/PATCH.... but this is a different story.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------
Original Message:
Sent: Jan 10, 2022 02:12
From: dileep narla
Subject: TMF 638 service state machine diagram
Hi Jonathan,
Yes, even my initial understanding was also same as you mentioned. But in TMF 638, Service model has attribute "RelatedServiceOrderItem" which is of type 'List' and is optional field. This makes confusion whether this attribute described wrong or was it introduced for some other purpose with respect to TMF641.
Hi @Ludovic Robert, can you please provide your insights on this ?
If the relation is missing from inventory object to corresponding order object, how to proceed further ?
------------------------------
dileep narla
Oracle Corporation
Original Message:
Sent: Jan 09, 2022 04:18
From: Jonathan Goldberg
Subject: TMF 638 service state machine diagram
Typically, the actions (create/change/delete) will come from the order - take a look at TMF641 (Service Order Management), where you should see that each contained service order item has an action attribute. The actions are not stored on the service inventory itself, but there should be a relationship from inventory object to the corresponding order object that created/updated the inventory object.
Hope it helps - maybe @Ludovic Robert will have additional insights.
------------------------------
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: Jan 07, 2022 05:08
From: dileep narla
Subject: TMF 638 service state machine diagram
Hi All,
I see that TMF 638 V4 spec state machine diagram showing create/change/delete actions along with Service life cycle states (ex: feasibilityChecked/designed/active/inactive). What are these create/change/delete actions ? Are these from Order management system, if so do POST/PATCH requests expect these actions from Order management system ? Sample POST request doesn't show these actions. Can you please help me understand these.
Thanks,
Dileep
------------------------------
dileep narla
Oracle Corporation
------------------------------