OPERATIONAL READINESS PROGRAMME. 26 Service Provider on Boarding 26.1 The Operational Readiness Programme is the programme of work to be undertaken jointly by the LFC and the Service Provider as part of an on boarding process as the Service Provider prepares for connection to the LFC Network, including; (i) the establishment of commercial relationships; (ii) set up of OSS/BSS interfaces; (iii) build of Footprints (if required); (iv) build of UFB Handover Connections and associated circuits (if required); (v) training as per clauses 26.11 and 26.12; and (vi) the testing and commissioning of processes, products and interfaces (including layer 2 interoperability). Each task within the on-boarding plan has appropriate service levels, milestones, the LFC and Service Provider requirements. The diagram below provides an overview of the plan. 26.2 The items in paragraphs 26.1(i) to 26.1(iii) of the on boarding process are specific to on boarding of the Service Provider to enable consumption of UFB services, e.g. execution of commercial agreements and staff training, and the Service Levels set out in this Part 11, subject to: (i) delay in the provision of materials or information to be supplied by the Service Provider, required to complete the item; (ii) acts or omissions of Service Providers that prevent the LFC from completely item e.g. making staff available for training; and (iii) any period of extension agreed between the Service Provider and an End User or between the LFC and the Service Provider. 26.3 The items in paragraphs 26.1(iv) to 26.1(vi) of the on boarding process, that involve provision of UFB services e.g. Handover Connection or Co-location Footprint, will be subject to the Service Levels in the appropriate Service Level Terms, including any service level extensions in those terms. 26.4 The diagram below provides an overview of the plan with indicative timings. Residential Service Provider On Boarding - Overview Configure and Test Layer 2 Initial DFAS / ICABs Link Build Initial Handover Connection Build Accept Order Prepare Initial Co-location Quote Install ITF Test Circuits Install Test P2P Circuits Initial Tie Cable Build Accept Order BAU orders OSS/BSS Training Commercials 25 30 35 40 Working days On Boarding Initial Build 26.5 The Service Provider will be required to sign a WSA and meet the requirements of the General Terms before they can take the Bitstream Services. 26.6 The Service Provider must provide all information required in a timely manner as any delay will extend the service level time. This information includes details of insurance, credit guarantee and contact information for the WSA. 26.7 The LFC’s OSS/BSS is required to enable the Service Provider to place and track Service Requests and Service Orders for UFB Services, to report faults and to obtain other operational information. 26.8 The Service Provider needs to have the OSS/BSS system in place and staff available for training. 26.9 Set up of the OSS/BSS requires the LFC to allocate passwords and test interfaces including processing trial Service Requests. 26.10 The LFC will provide training to the Service Provider staff which includes: (i) explanation of guides, products, processes, procedures and tools; (ii) submission of test Service Requests; (iii) handling exceptions; and (iv) Q & A. 26.11 The LFC will provide reasonable initial set up training consisting of a workshop held at a location determined by the LFC. The workshop will address: (i) overview of forecasting templates; (ii) overview of forms for Service Requests; (iii) basic details of OSS/BSS (including demonstration of the system); (iv) overview of billing and accounts; and (v) Q & A. 26.12 The Service Provider will ensure that a reasonable number of staff (up to a maximum number of 10 per session) attend any training provided. The Service Provider may choose to train only a limited number of staff initially to facilitate the placing of the infrastructure orders with a second session(s) on the wider order and assure processes once they are ready to go market. 26.13 Any additional training required by the Service Provider beyond reasonable initial set up training (up to 50 hours) may be charged for by the LFC in accordance with the Price List. 26.14 If a Service Provider requires co-location space, the Service Provider may place an initial Service Request with all required information once the OSS/BSS is in place and their staff are trained in its use. 26.15 The LFC will provide quotes for co-location build, once these are accepted the co- location build will commence subject to the provision of any materials or information required from Service Provider. On acceptance of the co-location build, the footprints will be handed over to the Service Provider. 26.16 The provision of a Co-location Footprint and any associated ancillary services will be subject to the Service Levels in the Central Office and POI Co-location Service Level Terms. 26.17 If a Service Provider requires a UFB Handover Connection and/or backhaul, the Service Provider may place an initial Service Request with all required information when signing WSA or they can wait until the OSS/BSS is in place and their staff are trained in its use. 26.18 The LFC will commence build subject to the provision of any materials or information required from Service Provider. On completion of joint testing the links will be handed over to the Service Provider. 26.19 The provision of a Handover Connection will be subject to the Service Levels in the Bitstream Service Level Terms.
Appears in 2 contracts
Samples: Ufb Services Agreement, Ufb Services Agreement
OPERATIONAL READINESS PROGRAMME. 26 Service Provider on BoardingBoarding
26.1 The Operational Readiness Programme is the programme of work to be undertaken jointly by the LFC and the Service Provider as part of an on boarding process as the Service Provider prepares for connection to the LFC Network, including;
(i) the establishment of commercial relationships;relationships;
(ii) set up of OSS/BSS interfaces;
(iii) build of Footprints (if required);required);
(iv) build of UFB Handover Connections and associated circuits (if required);required);
(v) training as per clauses 26.11 and 26.12; and
(vi) the testing and commissioning of processes, products and interfaces (including layer 2 interoperability). interoperability). Each task within the on-boarding plan has appropriate service levels, milestones, the LFC and Service Provider requirements. The diagram below provides an overview of the plan.
26.2 The items in paragraphs 26.1(i) to 26.1(iii) of the on boarding process are specific to on boarding of the Service Provider to enable consumption of UFB services, e.g. execution of commercial agreements and staff training, and the Service Levels set out in this Part 11, subject to:
(i) delay in the provision of materials or information to be supplied by the Service Provider, required to complete the item;
(ii) acts or omissions of Service Providers that prevent the LFC from completely item e.g. making staff available for training; and
(iii) any period of extension agreed between the Service Provider and an End User or between the LFC and the Service Provider.
26.3 The items in paragraphs 26.1(iv) to 26.1(vi) of the on boarding process, that involve provision of UFB services e.g. Handover Connection or Co-location Footprint, will be subject to the Service Levels in the appropriate Service Level Terms, including any service level extensions in those terms.
26.4 The diagram below provides an overview of the plan with indicative timings. Residential Service Provider On Boarding - Overview Prepare Initial Co-location Quote Initial Co-location Build Accept Order Initial Handover Connection Build Install Test P2P Circuits Initial Tie Cable Build Configure and Test Layer 2 Initial DFAS / ICABs Link Build Initial Handover Connection Build Accept Order Prepare Initial Co-location Quote Install ITF Test Circuits Install Test P2P Circuits Initial Tie Cable Build Accept Order BAU orders OSS/BSS Training Commercials 25 30 35 40 Working days On Boarding Initial Build
26.5 The Service Provider will be required to sign a WSA and meet the requirements of the General Terms before they can take the Bitstream Services.
26.6 The Service Provider must provide all information required in a timely manner as any delay will extend the service level time. This information includes details of insurance, credit guarantee and contact information for the WSA.
26.7 The LFC’s OSS/BSS is required to enable the Service Provider to place and track Service Requests and Service Orders for UFB Services, to report faults and to obtain other operational information.
26.8 The Service Provider needs to have the OSS/BSS system in place and staff available for training.
26.9 Set up of the OSS/BSS requires the LFC to allocate passwords and test interfaces including processing trial Service Requests.
26.10 The LFC will provide training to the Service Provider staff which includes:
(i) explanation of guides, products, processes, procedures and tools;
(ii) submission of test Service Requests;
(iii) handling exceptions; and
(iv) Q & A.
26.11 The LFC will provide reasonable initial set up training consisting of a workshop held at a location determined by the LFC. The workshop will address:address:
(i) overview of forecasting templates;
(ii) overview of forms for Service Requests;
(iii) basic details of OSS/BSS (including demonstration of the system);
(iv) overview of billing and accounts; and
(v) Q & A.
26.12 The Service Provider will ensure that a reasonable number of staff (up to a maximum number of 10 per session) attend any training provided. The Service Provider may choose to train only a limited number of staff initially to facilitate the placing of the infrastructure orders with a second session(s) on the wider order and assure processes once they are ready to go market.market.
26.13 Any additional training required by the Service Provider beyond reasonable initial set up training (up to 50 hours) may be charged for by the LFC in accordance with the Price List.
26.14 If a Service Provider requires co-location space, the Service Provider may place an initial Service Request with all required information once the OSS/BSS is in place and their staff are trained in its use.
26.15 The LFC will provide quotes for co-location build, once these are accepted the co- location build will commence subject to the provision of any materials or information required from Service Provider. On acceptance of the co-location build, the footprints will be handed over to the Service Provider.
26.16 The provision of a Co-location Footprint and any associated ancillary services will be subject to the Service Levels in the Central Office and POI Co-location Service Level Terms.
26.17 If a Service Provider requires a UFB Handover Connection and/or backhaul, the Service Provider may place an initial Service Request with all required information when signing WSA or they can wait until the OSS/BSS is in place and their staff are trained in its use.
26.18 The LFC will commence build subject to the provision of any materials or information required from Service Provider. On completion of joint testing the links will be handed over to the Service Provider.
26.19 The provision of a Handover Connection will be subject to the Service Levels in the Bitstream Service Level Terms.
Appears in 1 contract
Samples: Bitstream Services Agreement
OPERATIONAL READINESS PROGRAMME. 26 46 Service Provider on Boarding
26.1 46.1 The Operational Readiness Programme is the programme of work to be undertaken jointly by the LFC and the Service Provider as part of an on boarding process as the Service Provider prepares for connection to the LFC Network, including;
(i) 46.1.1 the establishment of commercial relationships;
(ii) 46.1.2 set up of OSS/BSS interfaces;
(iii) 46.1.3 build of Footprints (if required);
(iv) 46.1.4 build of UFB Handover Connections and associated circuits (if required);
(v) 46.1.5 training as per clauses 26.11 46.10 and 26.1246.11; and
(vi) 46.1.6 the testing and commissioning of processes, products and interfaces (including layer 2 interoperability). Each task within the on-boarding plan has appropriate service levels, milestones, the LFC and Service Provider requirements. The diagram below provides an overview of the plan.
26.2 46.2 The items in paragraphs 26.1(i) 46.1.1 to 26.1(iii) 46.1.3 of the on boarding process are specific to on boarding of the Service Provider to enable consumption of UFB services, e.g. execution of commercial agreements and staff training, and the Service Levels set out in this Part 1112, subject to:
(i) 46.2.1 delay in the provision of materials or information to be supplied by the Service Provider, required to complete the item;
(ii) 46.2.2 acts or omissions of Service Providers that prevent the LFC from completely item e.g. making staff available for training; and
(iii) 46.2.3 any period of extension agreed between the Service Provider and an End User or between the LFC and the Service Provider.
26.3 46.3 The items in paragraphs 26.1(iv) 46.1.4 to 26.1(vi) 46.1.6 of the on boarding process, that involve provision of UFB services e.g. Handover Connection or Co-location Footprint, will be subject to the Service Levels in the appropriate Service Level Terms, including any service level extensions in those terms.
26.4 46.4 The diagram below provides an overview of the plan with indicative timings. Residential Service Provider On Boarding - Overview Configure and Test Layer 2 Initial DFAS / ICABs Link Build Initial Handover Connection Build Accept Order Prepare Initial Co-location Quote Install ITF Test Circuits Install Test P2P Circuits Initial Tie Cable Build Accept Order BAU orders OSS/BSS Training Commercials 25 30 35 40 Working days On Boarding Initial Build
26.5 46.5 The Service Provider will be required to sign a WSA and meet the requirements of the General Terms before they can take the Bitstream ServicesCentral Office and POI Co-location Service.
26.6 46.6 The Service Provider must provide all information required in a timely manner as any delay will extend the service level time. This information includes details of insurance, credit guarantee and contact information for the WSA.
26.7 46.7 The LFC’s OSS/BSS is required to enable the Service Provider to place and track Service Requests for the Central Office and Service Orders for UFB ServicesPOI Co-location Service, to report faults and to obtain other operational information.
26.8 46.8 The Service Provider needs to have the OSS/BSS system in place and staff available for training.
26.9 46.9 Set up of the OSS/BSS requires the LFC to allocate passwords and test interfaces including processing trial Service Requests.
26.10 46.10 The LFC will provide training to the Service Provider staff which includes:
(i) 46.10.1 explanation of guides, products, processes, procedures and tools;
(ii) 46.10.2 submission of test Service Requests;
(iii) 46.10.3 handling exceptions; and
(iv) Q & A.46.10.4 Q&A.
26.11 46.11 The LFC will provide reasonable initial set up training consisting of a workshop held at a location determined by the LFC. The workshop will address:address:
(i) 46.11.1 overview of forecasting templates;
(ii) 46.11.2 overview of forms for Service Requests;
(iii) 46.11.3 basic details of OSS/BSS (including demonstration of the system);
(iv) 46.11.4 overview of billing and accounts; and
(v) Q & A.46.11.5 Q&A.
26.12 46.12 The Service Provider will ensure that a reasonable number of staff (up to a maximum number of 10 per session) attend any training provided. The Service Provider may choose to train only a limited number of staff initially to facilitate the placing of the infrastructure orders with a second session(s) on the wider order and assure processes once they are ready to go market.market.
26.13 46.13 Any additional training required by the Service Provider beyond reasonable initial set up training (up to 50 hours) may be charged for by the LFC in accordance with the Price List.
26.14 46.14 If a Service Provider requires co-location spacespace , the Service Provider may place an initial Service Request with all required information once the OSS/BSS or email ordering is in place and their staff are is trained in its use.
26.15 46.15 The LFC will provide quotes for co-location build, once these are accepted the co- location build will commence subject to the provision of any materials or information required from Service Provider. On acceptance of the co-location build, build the footprints will be handed over to the Service Provider.
26.16 46.16 The provision of a Co-location Footprint and any associated ancillary services will be subject to the Service Levels in the Central Office and POI Co-location Service Level Terms.
26.17 46.17 If a Service Provider requires a UFB Handover Connection and/or backhaul, Service and/ or backhaul the Service Provider may place an initial Service Request Requests with all required information when signing WSA or they can wait until once the OSS/BSS is in place and their there staff are trained in its use.
26.18 46.18 The LFC Build will commence build subject to the provision of any materials or information required from Service Provider. On completion of joint testing the links will be handed over to the Service Provider.
26.19 46.19 The provision of a Handover Connection will be subject to the Service Levels in the Bitstream Service Level Terms.
Appears in 1 contract
Samples: Ufb Services Agreement
