PROCEDURE FOR REQUEST FOR SERVICES. 3.1. The RL shall submit each Request via email using the form set out in Annex 3. NLT shall communicate the Application Reference Identifiers that are assigned to the respective tenures of the Point-to-Point Connections that are offered under Annex 2 at a later date. Each Request shall indicate the Application Reference Identifier, and NLT shall not be liable for any loss incurred by the RL in the event that an incorrect Application Reference Identifier is stated in the Request.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1. The RL shall submit each Request via email at XXxxxxxx@xxxxxxxxxx.xxx using the form set out in Annex 4. NLT shall communicate the Application Reference Identifiers that are assigned to the respective tenures of the DC Connections that are offered under Annex 3 at a later date. Each Request shall indicate the Application Reference Identifier, and NLT shall not be liable for any loss incurred by the RL in the event that an incorrect Application Reference Identifier is stated in the Request.
PROCEDURE FOR REQUEST FOR SERVICES. 2.1. The Requesting Licensee shall submit a Request under either Schedule 3, Schedule 10 or Schedule 11 of the Approved ICO via the NetLink Trust Platform with respect to each NBAP or CO-to-NBAP Connection required. For the avoidance of doubt, the ordering procedures set out in Clause 4 of Schedule 3, Clause 4 of Schedule 10 and Clause 4 of Schedule 11 of the Approved ICO shall apply.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1 The RL shall submit the request for the Point-to-Point Connection (“Request”) via email.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1. The RL shall submit a request for a Connection (“Request”) via email using the form set out in Annex 5. Within one (1) Business Day of receiving the Request, NLT will notify the RL on whether the Request has been accepted or rejected by NLT. Where the Request has been rejected, NLT shall inform the RL of the reason for the rejection.
PROCEDURE FOR REQUEST FOR SERVICES. 2.1. The RL shall submit a Request under Schedule 3 of the Approved ICO via the NetLink Trust Platform with respect to each 1:16 NBAP Connection required and shall include the prefix “<GOVTECH/T17032/<[NAME OF AGENCY]>” in the ‘Application Reference’ field. In the event that the RL fails to include the abovementioned prefix in the ‘Application Reference’ field when submitting the Request, the charges that apply to that 1:16 NBAP Connection shall be based on Schedule 15 of the Approved ICO instead of Annex 2 of this Agreement. For the avoidance of doubt, the ordering and provisioning procedures set out in clauses 4 and 5 of Schedule 3 of the Approved ICO shall apply to this Agreement notwithstanding any variance in the definition of “NBAP Connection”, unless specifically provided otherwise in this Agreement.
PROCEDURE FOR REQUEST FOR SERVICES. 2.1. The RL shall submit a written request for a COD Connection with respect to a Primary Connection by completing and emailing a completed form in the format set out in Annex 3. The RL shall indicate the Application Reference using prefix “<GOVTECH/T17032/<[NAME OF AGENCY]>” in the email.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1 The RL shall submit the request for the NBAP Connection (“Request”) via NLT’s Service Web Portal.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1 The RL shall submit the request for the Schedule 5 Connection in accordance with the ordering and provisioning procedure set out in Schedule 5 of the Approved ICO.
PROCEDURE FOR REQUEST FOR SERVICES. 3.1 The RL shall submit the request for the NRES 1:1 Connection in the form of a self-provide order (“Request”) via Service Portal.
