Name
Supplier Cancels Order
Description
This process provides us with the ability to cancel an order belonging to you.
Related B2B Services
Preceded by
Succeeded by
Pre-conditions
We notify you of our intent to cancel an order belonging to you. The order will have reached the state and substate of Acknowledged/Accepted but not the state Service Given.
Post-Conditions
You receive our notification and action as required.
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 1 | Send an Intent to Cancel order notification. | Chorus |
| 2 |
Receivethenotification,respondusinganAmendOrderResponse. If you reject the cancellation, refer to alternate flow. |
Customer |
| 3 | Receive the Amend Order Request, cancel the order and send a Closed Cancelled notification. | Chorus |
| 4 | Receive notification and action as required. | Customer |
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 1 | Send notification to advise of Customer options. | Chorus |
| 2 | Send Amend Order Request to agree to an option. | Customer |
| 3 | Action agreed option, send notification to advise. | Chorus |
The following use cases support this business process.
Click on the links to view the XML samples.
> Supplier Cancels Order - Customer Accepts Request
In this example your order cannot be fulfilled and needs to be cancelled. We advise you by sending:
You accept the cancellation using AmendOrderRequest: ANSWER.
We action the cancellation and advise you by sending:
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
|
AmendOrderNotification: INTENT_TO_CANCEL
|
|
|
AmendOrderRequest: ANSWER
|
AmendOrderRequest: ANSWER
|
|
AmendOrderNotification: CLOSED_CANCELLED
|
> Supplier Cancels Order - No intact available on site
In this example your order cannot be fulfilled and needs to be cancelled. The order has been submitted as an intact however the installer has identified that there is no intact available on site. As this order was submitted via B2B, we request that you submit a new Connect Additional ONT order via your B2B. We advise you by sending:
You accept the cancellation using AmendOrderRequest: ANSWER.
We action the cancellation and advise you by sending:
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
|
AmendOrderNotification: INTENT_TO_CANCEL
|
|
|
AmendOrderRequest: ANSWER
|
AmendOrderRequest: ANSWER
|
|
AmendOrderNotification: CLOSED_CANCELLED
|
|
| Customer Creates Order - Connect Additional ONT | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Supplier Cancels Order - Customer Rejects Request
In this example your order cannot be fulfilled and needs to be cancelled. We advise you by sending:
You reject the cancellation using an:
We acknowledge your response using:
The next steps in the process will be determined by the order and reason we asked to cancel it, for example,wemayuseanAmendOrderNotification: MANUAL_INTERACTIONtoprovideyouwithfurther information.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
|
AmendOrderNotification: INTENT_TO_CANCEL
|
|
|
AmendOrderRequest: ANSWER
|
AmendOrderRequest: ANSWER
|
|
AmendOrderNotification: REJECT_CANCEL
|
|
|
AmendOrderNotification: MANUAL_INTERACTION
|
This section provides a list of the User Story References that we have met in this business process, as defined by the Ultra-Fast Broadband BSS / OSS Business Interaction Framework.
The document is available from:
Refer to the TCF website for documentation.
| ID | DESCRIPTION |
|---|---|
| US38 | As a Service Provider I want standardized service order states from the LFCs so I can have consistent order management procedures across LFCs. |
| SC38.01 | The LFCs agree a common set of service states which are captured in the business interaction framework. |
| US39 | As a Service Provider I want standardised service order notifications from the LFCs so I can have consistent order management procedures across LFCs. |
| SC39.01 | The LFCs agree a common set of service order notifications which are captured in the business interaction framework. |
| SC39.09 | The Order Reference Number is included on all order notifications. |
| SC39.10 | The Service Provider Order Reference number is included on all order notifications. |
| SC39.11 | The date and time is included on all order notifications. |
| SC39.12 | LFC uses a formatted template for the notifications. |
| US53 | As a Service Provider I want to be kept informed if an installation will not be completed on RFS date so I can ensure a contingency plan can be activated if necessary. |
| SC53.01 | Service Provider will be notified if installation will not be completed on RFS date. |