Hi,
All 3 API play a role in the orchestration of service orders.
A typical service order orchestration would work as follows.
A TMF641 Service order contains one or more services potentially with relationships between them that help in deciding on the sequence of events.
The services in the TMF641 order are typically Customer Facing Services.
The first stage of the service orchestration is the order validation.
The service order will first go through a syntactical validation (conformance validation of the POST message according to a supperset of the rules defined in TMF641B).
This step is followed by a semantic validation using the TMF633 ServiceSpecification, semantic validation differs for the different actions defined on the service order items, but typically includes checks if all mandatory characteristics are provided and if the values provided are in line with specification.
If anything is not inline with the specification a stateChanged notification "Rejected" is sent.
If all is well, the CFS are now created in the inventory using TMF638. The stage is ended by sending a stateChanged notification "Acknowledged".
The second stage of the service orchestration is the service design. This stage might start immediately or can be delayed by the requestedStartDate.
It starts by decomposing the CFSs in the required RFSs, followed by allocating the supporting resources. The RFS are now also created in the inventory using TMF638.
The third stage is service activation. As soon as the resources are available TMF640 is called for each RFS.
I hope this scenario gives some clarity on this subject.
------------------------------
Koen Peeters
Ciminko Luxembourg
------------------------------
Original Message:
Sent: Jan 28, 2021 07:22
From: Bhanu Sirigiri
Subject: Positioning of TMF640
Hi,
I've got query on positioning and need of 640 after reading of 640-Service Activation, 641-Service Order, 638 - Service Inventory management. Can the API community share the guidelines defined while defining APIs ? That'll help.
1. 641 has "Activate" as target state for Service which does provide option of Activation/Configuration. This is same functionality as of 640. So, Is 640 subset of 641 ?
2. If answer to qn-1 is No , What are guidelines in selection of 641/640 ? i.e. In which scenarios should they use. I would like to present 2 scenarios of B2B world. Customer wants to add a new location for getting new products, Other is In-life change i.e. Customer wants to make changes to multiple RFSs to achieve a business outcome
Thanks in advance.
------------------------------
Bhanu Sirigiri
BT Group plc
------------------------------