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 |
ServiceProviderreferenceisprovidedonallnotificationsregardingtheservicerequest order. |
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 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. |
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.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. |
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. |
US49 |
As a Service Provider I want to know if amending or cancelling an order is going to incur a cost so I can advise my Customer and charge them accordingly for any Customer initiated change. |
SC49.02 |
Service Provider is told when amending the order of the charge incurred. |
US56 |
As the LFC, I want to know why a service order has been cancelled so I can identify issues and trends within the process. |
SC56.01 |
Service Provider can select from a list of reasons when cancelling the service order: End Customer Cancelled; Preferred Installation Date Unavailable; Installation Issue/Complexity; Building owner consent not received; Cost to Connect; or Other. |
SC56.02 |
If other is selected, it is mandatory for the Service Provider to enter the reason in a free text field. |
US423 |
As a Gaining Service Provider I want to be able to cancel a Transfer request so that I can avoid an erroneous transfer |
SC423.01 |
TheGainingServiceProvider can cancelaTransferrequest atany pointbefore the ProductInstance(s)toberelinquishedaspartoftheTransferhavebeendeactivated. Key Non-Functional References |
US203 |
As an LFC or Service Provider I need all interactions relating to contractual transactions to have a guaranteed, verified delivery, so that commercial disputes can be resolved factually. |