OPERATIONAL READINESS PROGRAMME Clause Samples
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 th...
OPERATIONAL READINESS PROGRAMME. 21 PONFAS Operational Context
(i) PONFAS Feeder Services are used to establish a Service Provider Coverage Area for their PONFAS-enabled services; and
(ii) PONFAS Distribution Services are used to connect individual Premises within this Coverage Area to their PONFAS-enabled services. The following table shows how Service Providers would typically offer Passive Optical Network-based broadband services by combining PONFAS Services with their own network: Type Purpose Services Typical Process 1 Build (Infrastructure) Create geographical coverage Co-location, including TPAD + Tie Cables; PONFAS Feeder, including DFAS/ICABS if required 1. Plan Coverage Area (SP). 2. Request Co-location service (SP). 3. Build Co-location service (including TPAD if applicable) (SP, LFC). 4. Commission active electronics within, or connected to, co-location services (SP). 5. Request PONFAS Feeder(s) on LFC Systems (SP). 6. LFC confirms Feasibility for each PONFAS Feeder, including path (LFC). 7. Service Provider confirms order on LFC OSS (SP). 8. LFC confirms quote for PONFAS Feeder path (including additional services if required) (LFC). 9. Service Provider confirms PONFAS Feeder order (SP). 10. Build PONFAS Feeder and connect to the specified Co-location or Linking service (LFC). 11. Connect to active electronics (SP). 12. Coverage now available (SP). Type Purpose Services Typical Process 2 Connect Customer Connection PONFAS Distribution 1. Request PONFAS Distribution (SP). 2. Configure active electronics with service (usually done in advance of connection) (SP). 3. Build PONFAS Distribution, including lead-in if required (LFC) 4. Connect ONT to PONFAS Distribution (SP or, on request, LFC); 5. Commission service: a. configure ONT to talk to OLT (SP). b. ONT auto-downloads configuration (SP). c. specific on-site configuration or service testing (SP or, on request, LFC). Although the above model shows how Service Providers can consume PONFAS, this should not be seen as constraining Service Providers from implementing alternative operational models or services that consume PONFAS services, processes and service levels. PONFAS Operations Manual March 2021
OPERATIONAL READINESS PROGRAMME. 19 Service