Information About Synchronizing Data across Order Items from Different Orders

In Order Management Plus, assets are not affected when you synchronize data across Order Items from different Orders.

This is important in a scenario where there might be two flows, such as a new flow and a MACD, running in parallel for the same assets and their corresponding inventory items, and assetization occurs early in the new flow.

Consider the following scenario:

A service provider has an implementation of Hybrid Access Networks service. In this service, customer access is organized through a mix of 4G, 5G, and ADSL fixed line access. 4G and 5G are provided by the service provider and ADSL is provided by a third party. 4G and 5G provisioning is extremely fast. However, it might take weeks for the third party to provision ADSL. Hybrid Access Networks are fully functional after 4G and 5G are provisioned, so the service provider wants to start billing and assetizing at that point without waiting for ADSL provisioning. The service provider wants to use staged assetization to force the provisioning of the whole service in the middle of the new service provisioning. After that, ADSL will undergo provisioning at its own pace.

If a customer’s router is faulty, the service provider can use a MACD scenario for a router change to ship a new router to the customer. The 4G SIM card is embedded in the router, so the 4G router should be updated. This scenario can occur while the new process is still in progress and the ADSL is being provisioned. In fact, it is likely the first router will fail. Therefore, you can have the new process and the MACD process running at the same time. The new process is likely to finish after the MACD process.

As Order Management Plus processes freeze characteristic values in the orders, the new serial number of the SIM card is overridden by the old number during the new process assetization. To prevent this, the auto task synchronizes characteristics between concurrent processes across the same asset. This autotask acquires a lock on an account and determines if there are any processes running for the same assets as the current process. If any processes started later, the auto task copies the characteristic values from the upstream and downstream orders associated with the process to the upstream and downstream orders of the current process. This task is associated with an Order Item for a commercial order and is the last task in the flow.

The auto task takes the assetized order items from commercial and first-level decomposition order items in the current orchestration plan, finds the latest order items in subsequent MACD orders, and copies characteristics and attribute values to the current order items.