Name
Customer Creates Order
Description
This process provides you with the ability to create an order to purchase or relinquish a product, make changes to an existing product instance, and to lock in appointments.
Related B2B Services
Preceded by
Succeeded by
Pre-conditions
The BIC003: Query Order Feasibility response returned the FEASIBILITY_CODE 998 or 999.
If your order requires a site visit you have reserved the appointment(s) using BIC005: Reserve Appointment.
Post-conditions
You receive our response with confirming that your order has been submitted and the state and substatus are Acknowledged/Received.
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 1 | Submit create order request. | Customer |
| 2 | Receive the request and validate the message. | Chorus |
| 3 | Validate the order information. | Chorus |
| 4 |
Determine if the order passes validation. If the request is invalid refer to alternate flow 1. |
Chorus |
| 5 | Provide response containing a result of the create order request. | Chorus |
| 6 | Receive the create order response. | Customer |
| STEP | DESCRIPTION | ROLE |
|---|---|---|
| 4.1 | If the Create Order request is invalid, return an error response. | Chorus |
| 4.2 | Return an error response explaining why the order cannot be created. | Chorus |
Refer to the Exception Codes table for error details
Create Order Requests
| ORDER TYPE | RULE |
|---|---|
| Connect |
We will reject Connect order requests if:
|
| Connect Secondary |
We will reject Connect Secondary order requests if:
|
| Connect and Replace |
We will reject Connect and Replace order requests if:
|
| Move |
We will reject Move order requests if:
***Note: Use separate disconnect and connect orders to overlap services. |
| Move and Replace |
We will reject Move and Replace order requests if:
|
| Disconnect |
We will reject Disconnect order requests if:
|
| Transfer |
We will reject Transfer order requests if:
|
Disconnect Secondary Offer
A location can only have a secondary offer if there is an existing primary offer.
If the primary offer is disconnected, we will send you an order notification to advise that we intend to disconnect the secondary offer. If you do not reject our notification and create a Change Offer order to promote the secondary offer, we will process the disconnection.
Note: the notification must be rejected and the Change Offer order actioned within 5 calendar days or the secondary offer will be disconnected.
The use case example showing how to Answer a Disconnect Secondary notification is provided by:
Replace Orders
On receipt of a replacement order, we will send a disconnect notification to the Losing Service Provider(s) (LSP) and they must respond within 5 days.
The replacement will not proceed if the LSP:
In either of these cases, the Gaining Service Provider (GSP) will be advised that we intend to cancel their order and they may accept the cancellation or raise an escalation with us.
The use cases examples showing how to Answer a Disconnect Abandonment notification are provided by:
The Exception Codes table lists the exceptions that may be returned by this service.
For a full list of exception codes and their meanings see B2B Exception Codes.
| CODE | DESCRIPTION |
|---|---|
| 000 | Backend processing error encountered - If the problem persists please contact Chorus admin |
| 015 | Site Visit ID not found |
| 016 | DateTime Range not valid |
| 017 | RFS validation failed: {%s} |
| 019 | Customer Order ID or Customer Reference ID not found |
| 025 | The attribute {%s} in the request does not exist or does not match the corresponding attribute in the Order record. |
| 026 | Request validation failed: {%s} |
| 027 | Order Feasibility has expired. |
| 029 | The Order State of the specified Customer Order does not support the selected action |
| 030 | The Order ID provided belongs to a different customer |
| 060 | Notification Email is mandatory when Notification Preference is true |
The following use cases support this business process.
Click on the links to view the XML samples.
> Connect Primary
Create Order Request is executed to order a Product Offer for the location using Order Type Connect Primary and OrderItem action new.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect Primary | |
| Order details Product Offering id Product Characteristics |
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Connect Additional ONT
Create Order Request is executed to order a Product Offer for the location using Order Type Connect Additional ONT and OrderItem action new.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect Additional ONT | |
| State & Substatus: Acknowledged/Accepted | |
|
AmendOrderNotification: RFS_CONFIRMED
|
> Connect Secondary
Create Order Request is executed to order a Product Offer for the location using Order Type Connect Secondary and OrderItem action new.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect Secondary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Connect and Replace
Create Order Request is executed to order a Product Offer for the location using Order Type Connect and Replace, and OrderItem action new.
Note: the order moved to Held Pending Disconnect and a disconnection notification is sent to the LSP.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect and Replace | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
|
|
AmendOrderNotifcation: HELD_PENDING_DISCONNECT_ACCEPTANCE
|
> Move Primary
Create Order Request is executed to order a Product Offer for the location using Order Type Move Primary, OrderItem action new and relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Move Primary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Move Additional ONT
Create Order Request is executed to order a Product Offer for the location using Order Type Move Additional ONT, OrderItem action new and relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Move and Replace
Create Order Request is executed to order a Product Offer for the location using Order Type Move and Replace, OrderItem action new and relinquish.
Note: the order moved to Held Pending Disconnect and a disconnection notification is sent to the LSP.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
|
|
AmendOrderNotifcation: HELD_PENDING_DISCONNECT
|
> Change Offer
Create Order Request is executed to order a Product Offer for the location using Order Type Change Offer, OrderItem action new and relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Change Offer | |
|
CreateOrderRequest
|
CreateOrderRequest
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Change Offer - Promote to Primary
Create Order Request is executed to order a promote a Product Offer for the location using Order Type Change Offer, OrderItem action new and relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Change Offer (Promote to Primary) | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Modify Attribute
Create Order Request is executed to order a Product Offer for the location using Order Type Modify Attribute and OrderItem action modify.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Modify Attribute | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Modify Attribute with CSE
Create Order Request is executed to order a Product Offer for the location using Order Type Modify Attribute, OrderItem action modify and OrderItem action new.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Modify Attribute with CSE | |
|
CreateOrderRequest
|
CreateOrderRequest
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Disconnect Primary
Create Order Request is executed to order a Product Offer for the location using Order Type Disconnect Primary and OrderItem action relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Disconnect Primary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Disconnect Secondary
Create Order Request is executed to order a Product Offer for the location using Order Type Disconnect Secondary and OrderItem action relinquish.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Disconnect Secondary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
> Transfer Primary
Create Order Request is executed to order a Product Offer for the location using Order Type Transfer Primary and OrderItem action new.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Transfer Primary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: RFS_CONFIRMED
|
|
|
|
AmendOrderNotification: SCHEDULED
|
|
AmendOrderNotification: SERVICE_GIVEN
|
|
|
AmendOrderNotification: COMPLETED_BILLING
|
|
|
AmendOrderNotification: CLOSED_COMPLETED
|
The following Use Cases provide examples of orders that require manual activity by Chorus.
-- Connect Primary - Order Requires Network Design
Create Order Request is executed to order a Product Offer at the location using Order Type Connect Primary and OrderItem action new.
The AmendOrderNotification: RFS_CONFIRMED is omitted and the order state and substate are changed to In Progress/Network Design.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect Primary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: NETWORK_DESIGN
|
-- Connect Primary - Order Requires Consent
Create Order Request is executed to order a Product Offer at the location using Order Type Connect Primary and OrderItem action new.
The Amend Order Notification: RFS_CONFIRMED is omitted and the order state and substate are changed to In Progress/Consent Required.
| REQUEST | NOTIFICATION / RESPONSE |
|---|---|
| Customer Creates Order - Connect Primary | |
|
CreateOrderRequest
|
CreateOrderResponse
|
|
AmendOrderNotification: ACKNOWLEDGED_ACCEPTED
|
|
|
AmendOrderNotification: CONSENT_REQUIRED
|
The following table describes the use case exceptions that support this business process.
Click on the scenario link to view the XML sample.
| SCENARIO | DESCRIPTION | REQUEST | RESPONSE |
|---|---|---|---|
| Customer Creates Order - Order Feasibility Expired |
CreateOrderRequest is executed to order a product after the order feasibility period has expired. The order feasibility valid For period is returned by Query Order Feasibility Order Feasibility Result Item Detail - Valid For. |
|
|
| Customer Creates Order - RFS Validation Failed |
CreateOrderRequest is executed to create an order using an invalid RFS date. |
|
|
| Customer Creates Order - Request Does Not Match Corresponding Order Record |
CreateOrderRequest is executed to create an order using values that do not match the ones you used in Query Order Feasibility. You must use the same values you entered in Query Order Feasibility in the Create Order Request. |
|
|
| Customer Creates Order - Email address is invalid |
CreateOrderRequest is executed to create an order using an invalid email address. |
|
|
| Customer Creates Order - Site Contact Details Incorrect or Missing |
CreateOrderRequest is executed to create an order. The site contact details are missing or invalid. |
|
|
| Customer Creates Order - Site Visit Validation Failed |
CreateOrderRequest is executed to create an order. The site visit appointment has expired or has not been reserved. |
|
|
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.
Request Success Criteria
| ID | DESCRIPTION |
|---|---|
| US30 | As an LFC I want a pre-qualification to be completed before the Service Provider submits a service request so that I can manage the order process. |
| SC30.01 | Service Provider is prevented from submitting a service request without having previously completed a pre-qualification. |
| SC30.02 | Whereamanualpre-qualificationis required,theServiceProviderispreventedfrom submitting a service request without the manual pre-qualification template being completed. |
| US31 | As a Service Provider I want to place a Service Request via the BSS/OSS so I can save cost and time. |
| SC31.01 | Service Provider can submit a service request via the SSP. |
| SC31.02 | Service Provider can submit a service request via the B2B. |
| US34 | As a Service Provider I don’t want to have to re-enter any information that comes from the pre-qualification so I can save time when placing a service request order. |
| SC34.03 | ServiceProvider can submit key related to the previous transaction when submitting a service request via the B2B so they don’t have to submit the whole address. |
| US35 | As a Service Provider I want to be able to add my own reference ID to a Service Request order so that I can easily match the order with orders in my own systems. |
| SC35.01 | Service Provider can enter a Service Provider Order Reference ID when submitting a service request via the B2B and/or SSP. |
| SC35.02 | Service Provider can enter any letter, number or punctuation key. |
| US36 | As the LFC I want to collect all relevant information on the “New” or “Modify” service request so I can manage the order effectively. |
| SC36.01 | Service Provider provides the name of the staff member logging the service request. This field is mandatory. |
| SC36.02 | Service Provider provides the name of the staff member logging the service request. This field is mandatory. |
| SC36.03 | Service Provider provides the phone number of the staff member logging the service request. This field is mandatory. |
| SC36.04 | Service Provider can enter the Business Name of the End Customer of the service order. This field is optional. |
| SC36.05 | Service Provider enters the contact name of the End Customer of the service order. This field is optional. |
| SC36.06 | Service Provider provides the phone number of the End Customer of the service order. This field is optional. |
| SC36.07 | Service Provider provides an alternate phone number of the End Customer of the service order. This field is optional. |
| SC36.08 | Service Provider provides the Site Contact Name for the service order. This field is mandatory. |
| SC36.09 | Service Provider provides the Site Contact Number for the service. This field is mandatory. |
| SC36.10 | Service Provider can specify the preferred connection date. |
| SC36.11 | ServiceProvider can specifyAM orPM as the preferred installation time on the connection date. |
| SC36.12 | Service Provider can specify a preferred installation time on the connection date. |
| SC36.13 | Service Provider can complete an additional notes field if required to alert to site specific requirements and health and safety issues. This field is optional. |
| SC36.14 | Service Provider can specify the preferred ETP installation location. |
| SC36.15 | Service Provider can specify the preferred ONT installation location. |
| SC36.16 | Service Provider must specify the product required. |
| SC36.17 | Service Provider can specify additional products or services required. |
| SC36.21 | Service Provider can specify the UNI VLAN. |
| SC36.22 | Service Provider can enter the Service ID. NOTE: This field is a mandatory requirement when it is a “modify” service request. |
| SC36.23 | Service Provider can provide the name and contact details of the nominated primary contact person within their organisation to be contacted about the service request |
| SC36.24 | Service Provider can provide the name and contact details of the nominated person within their organisation to be contacted about escalations regarding the service request. |
| US37 | As the LFC I want to limit the products the Service Provider can order to only those which they have been authorised to order so I can avoid processing of invalid service requests. |
| SC37.02 | The Service Provider can only select products which they are certified for |
| SC37.03 | The Service Provider can only select products for which a valid POI and Backhaul exist for the specified site. |
| US41 | As a Service Provider I want to be able to inform the LFC that specific orders for services are related to each other so that the LFC build is managed to meet Customer expectations. |
| SC41.01 | The LFC has an agreed process for the Service Provider to notify them that a service is related to another service. |
| US43 | As a Service Provider I want to be able to book an appointment for when the LFC is going to perform a site visit so that I can inform the Customer that they need to be at home on that day. |
| SC43.01 | The Service Provider can specify the preferred date and time of the site visit. |
| US44 | As the Service Provider I want to be able to request a service order be fast-tracked so that I can coordinate complex installs with more flexibility. |
| SC44.01 | The LFC has an approved process for fast-tracking a service request. |
| SC44.03 | The Service Provider can notify the LFC of the preferred installation date. |
| 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.04 | Service Provider can nominate the person (or persons) to be contacted when an RFS date is to be rescheduled with the End Customer. |
| US58 | As the LFC I want to collect any information on the “Relinquish” service requested so I can manage the order effectively. |
| SC58.01 | Service Provider provides the name of the staff member logging the service request. This field is mandatory. |
| SC58.02 | Service Provider provides the phone number of the staff member logging the service request. This field is mandatory. |
| SC58.03 | Service Provider can enter the Business Name of the End Customer of the service order. This field is optional. |
| SC58.04 | Service Provider enters the contact name of the End Customer of the service order. This field is optional. |
| SC58.05 | Service Provider provides the phone number of the End Customer of the service order. This field is optional. |
| SC58.06 | Service Provider provides an alternate phone number of the End Customer of the service order. This field is optional. |
| SC58.07 | Service Provider provides the Site Contact Name for the service order. This field is mandatory. |
| SC58.08 | Service Provider provides the Site Contact Number for the service. This field is mandatory. |
| SC58.09 | Service Provider can specify the preferred relinquishment date. |
| SC58.10 | ServiceProvider can specifyAM orPM as the preferred relinquishment time on the connection date. |
| SC58.11 | Service Provider can specify a preferred relinquishment time on the connection date. |
| SC58.12 | Service Provider can complete an additional notes field if required to alert to site specific requirements and health and safety issues. This field is optional. |
| SC58.13 | Service Provider must enter the Service ID. |
| SC58.14 | ServiceProvider can provide the name and contact details of the nominated primary contact person within their organisation to be contacted about the service request. |
| SC58.15 | ServiceProvider can provide the name and contact details of the nominated person within their organisation to be contacted about escalations regarding the service request. |
| US65 | As the LFCI want to know which type of service request theServiceProviderrequires so I can tailor the information I require. |
| SC65.01 | Service Provider can specify the type of service request from a list containing: New, Modify, Relinquish |
| US66 | As a Service Provider I want to be able to make changes to the mapping of services to handover points so that I can manage handover capacity and network elements. |
| SC66.02 | The LFC has an approved process for re-mapping services to different handover points on request from a Service Provider. |
| US401 | As a Gaining Service Provider I want to know the LFC product instance ID of the service instance that the end customer wishes to transfer from the Losing Service Provider, so that I can identify the correct service/s to transfer. |
| SC401.01 | Every product instance provided by an LFC to an end user premise has a unique identifier (unique by LFC). |
| US406 | As a Service Provider I want to be able to indicate to the LFC exactly which resources I wish to transfer so that only the services I have requested are transferred and none are left behind. |
| SC406.01 | The UFB services specified in the Transfer Service Request are transferred to the requested Service Provider point of interconnect. |
| SC406.02 | The Service Provider uses the Product Instance Id to specify which service is to be transferred. |
| US407 | As an LFC I want the Gaining Service Provider to provide the agreed set of information in a Transfer Request so that I have sufficient information to action the request. |
| SC407.01 | Gaining Service Provider provides the Product Instance ID of each product instance to be transferred. |
| SC407.02 | Gaining Service Provider specifies the Product Offering(s) that they wish to have activated in place of the product instance(s) to be transferred. |
| SC407.03 | Gaining Service Provider provides the Place ID where the new offering(s) is/are to be activated. |
| SC407.04 | Gaining Service Provider provides the RFS date/time that the transfer is to be actioned. |
| SC407.05 | Gaining Service Provider provides the billing account ID that the Losing Service Provider bills the End Customer for the product instance that is to be transferred. |
| US410 | As a Gaining Service Provider I want to be able to specify, when requesting service activation, that it is a Transfer so that the End customer is not left without service while transferring from one Service Provider to another. Note: This USonly applies when no secondary services exist at that location. |
| SC410.01 | The LFC provides a mechanism to indicate that a request relates to a transfer. |
| SC410.04 | Only those access services that are requested to be transferred are actually transferred. |
| ID | DESCRIPTION |
|---|---|
| US30 | As an LFC I want a pre-qualification to be completed before the Service Provider submits a service request so that I can manage the order process. |
| SC30.01 | ServiceProviderispreventedfromsubmittingaservicerequestwithouthaving previously completed a pre-qualification. |
| SC30.02 | Where a manual pre-qualification is required, the Service Provider is prevented from submitting a service request without the manual pre-qualification template being completed. |
| US31 | As a Service Provider I want to place a Service Request via the BSS/OSS so I can save cost and time. |
| SC31.03 | ServiceProviderreceivesnotificationacknowledgingthattheservicerequesthasbeen received. |
| US35 | As a Service Provider I want to be able to add my own reference ID to a Service Request order so that I can easily match the order with orders in my own systems. |
| SC35.03 | Service Provider reference is provided on all notifications regarding the service request order. |
| US36 | As the LFC I want to collect all relevant information on the “New” or “Modify” service request so I can manage the order effectively. |
| SC36.23 | ServiceProvider can provide the name and contact details of the nominated primary contact person within their organisation to be contacted about the service request. |
| SC36.25 | Service Provider receives a notification acknowledging that the service request has been received. |
| US38 | As a Service Provider I want standardised service order states from the LFCs so I can have consistent order management procedures across LFCs. |
| SC38.01 | The LFCs agree on 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 on 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 are included on all order notifications. |
| SC39.12 | LFC uses a formatted template for the notifications. |
| US40 | As an LFC I want to validate the information entered within the service request on the OSS/BSS before the order is submitted so I can be assured of quality. |
| SC40.04 | When a Service Request submitted via the SSP has failed the validation check, The LFC can highlight the fields which failed the validation check. |
| SC40.05 | When a Service Request submitted via the B2B has failed the validation check, The LFC can send information on which fields failed the validation check. |
| US41 | As a Service Provider I want to be able to inform the LFC that specific orders for services are related to each other so that the LFC build is managed to meet Customer expectations. |
| SC41.02 | TheServiceProvideris notified of a designation identifierto be associated with the service, where the service will be interconnected with other services from the LFC. |
| US42 | As theServiceProviderI want to receive a notification when my service request has been confirmed so I that can pre-configure the end-user service, and manage Customer expectation. |
| SC42.01 | Service Provider receives confirmation that the service request has been confirmed. |
| SC42.02 | The notification contains the Order Reference Number. |
| SC42.03 | The notification contains the Service Provider Order Reference Number where supplied. |
| SC42.04 | The notification contains a date and time stamp. |
| SC42.05 | The notification contains confirmation of the first appointment date. |
| SC42.06 | If the requested appointment date is unavailable, the notification shows that it is a revised appointment date. |
| SC42.11 | The notification contains the unique address identifier. |
| SC42.12 | The notification contains the UNI Port identifier(s) where not defaulted in the Service Template. |
| SC42.13 | The notification contains the UNI VLAN identifier(s) where applicable and not defaulted in the Service Template. |
| SC42.14 | The notification contains all necessary information to enable the service provider to pre-configure the service. e.g. SVID, CVID and ONT port. |
| SC42.15 | The notification includes whether or not this service is the primary service on this access. |
| SC42.16 | The notification contains the projected RFS date |
| SC42.17 | The notification can include the LFC’s parent ID that they have assigned to the service being activated and to related services that are to be joined to form an end-to-end service. |
| SC42.18 | The notification can include the Service Providers parent ID that they have assigned to the service being activated and to related services that are to be joined to form an endto-end service where supplied. |
| SC42.19 | The notification contains the agreed option 82 value where relevant. |
| US43 | As a Service Provider I want to be able to book an appointment for when the LFC is going to perform a site visit so that I can inform the Customer that they need to be at home on that day. |
| SC43.02 | The Service Provider is notified if the preferred date and time have been confirmed as part of the service request acceptance notification. |
| US66 | As a Service Provider I want to be able to make changes to the mapping of services to handover points so that I can manage handover capacity and network elements. |
| SC66.02 | The LFC has an approved process for re-mapping services to different handover points on request from a Service Provider. |
| US401 | As a Gaining Service Provider I want to know the LFC product instance ID of the service instance that the end customer wishes to transferfrom the LosingService Provider, so that I can identify the correct product instance(s) to transfer. |
| SC401.01 | Every product instance provided by an LFC to an end user premise has a unique identifier (unique by LFC). |