Common use of Order Handling Clause in Contracts

Order Handling. ‌ 4.1 The Contracting QP must place Orders for any of the following purposes in accordance with paragraph 4.2: (a) to set up one or more L3 Virtual Routing Domains; (b) to request Modification(s) to an Approved Project Schedule; and/or (c) to Deactivate any L3 Virtual Routing Domains which has been set up by Nucleus Connect. In relation to paragraph 4.1(a), the number of L3 Virtual Routing Domains that the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up of the L3 Virtual Routing Domain(s), Nucleus Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basis. 4.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.6, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two (2) Business Days after Nucleus Connect’s receipt of such Order. 4.6 Subject to paragraph 4.7, where the Contracting QP submits an Order, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such Order in the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by the Contracting QP is other than as set out in IETF RFC4364; (b) where such Order is not in the prescribed form; (c) where the information in such Order is illegible, inaccurate, incomplete or incorrect; (d) pursuant to paragraph 8.1; or (e) where the Contracting QP has committed a material breach of the ICO Agreement. 4.7 Where the Platform is in operation, the grounds in paragraphs 4.6(b) and 4.6(c) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground in paragraph 4.6(a), 4.6(d) or 4.6(e) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for the Contracting QP at the time, in which case this Service Schedule shall remain in force.

Order Handling. ‌ 4.1 5.1 The Contracting QP must may place Orders an Order for any of the following purposes in accordance with paragraph 4.25.2: (a) to set take up one or more L3 Virtual Routing Domains;Patching Service(s); and/or (b) to request Modification(s) to an Approved Project Schedule; and/or (c) to Deactivate any L3 Virtual Routing Domains which has been set up by Nucleus Connect. In relation to paragraph 4.1(aterminate Patching Service(s), the number of L3 Virtual Routing Domains that the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up of the L3 Virtual Routing Domain(s), Nucleus Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basis. 4.2 5.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 5.3 Upon the submission by the Contracting QP of an Order to take up a Patching Service, the Contracting QP shall pay Nucleus Connect the applicable Charges as set out in paragraph 10, in accordance with the Master ICO Agreement. 5.4 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 5.5 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 5.6 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.65.7, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two (2) Business Days after Nucleus Connect’s receipt of such Order. 4.6 5.7 Subject to paragraph 4.7, where the Contracting QP submits an Order5.8, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such any Order submitted by the Contracting QP in any of the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by activation date or deactivation date (as the Contracting QP is other than as case may be) set out in IETF RFC4364such Order is earlier than the date falling five (5) Business Days from the date such Order is submitted; (b) where such Order is not in the prescribed form; (c) where the information in such Order is illegible, inaccurate, incomplete or incorrect;; and (d) pursuant to paragraph 8.1; or (e) where the Contracting QP has committed a material breach of the ICO Agreement. 4.7 5.8 Where the Platform is in operation, the grounds in paragraphs 4.6(b5.7(a) and 4.6(cto 5.7(c) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground in paragraph 4.6(a), 4.6(d) or 4.6(e5.7(d) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for providing Patching Services to the Contracting QP at the time, in which case this Service Schedule shall remain in force.

Order Handling. ‌ 4.1 5.1 The Contracting QP must shall place Orders for any of the following purposes each Order to take up Co-location Services in accordance with paragraph 4.25.2. The Contracting QP shall be required to specify the following in each such Order: (a) to set up one or more L3 Virtual Routing Domainsthe location of the NC CO at which Co-location Space is requested; (b) the type of equipment proposed to request Modification(s) to an Approved Project Schedule; and/orbe installed (“Co-located Equipment”); (c) to Deactivate any L3 Virtual Routing Domains which has been set up by Nucleus Connect. In relation to paragraph 4.1(a), the number of L3 Virtual Routing Domains that space and power requirements; (d) the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up weight of the L3 Virtual Routing Domain(s), Nucleus Co-located Equipment; and (e) any other information that may be reasonably requested by ▇▇▇▇▇▇▇ Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basisduring the ordering process. 4.2 5.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 5.3 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 5.4 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 5.5 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.65.6, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two three (23) Business Days after Nucleus Connect’s receipt of such Order. 4.6 5.6 Subject to paragraph 4.7, where the Contracting QP submits an Order5.7, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such any Order submitted by the Contracting QP to take up Co-location Services in any of the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by the Contracting QP is other than as set out in IETF RFC4364; (b) where such Order is not in the prescribed form; (cb) where the information in such Order is illegible, inaccurate, incomplete or incorrect; (dc) pursuant to paragraph 8.1; orunavailability of the Co-location Space at the NC CO; (ed) where the Contracting QP has committed a material breach of the ICO Agreement; or (e) where Nucleus Connect is not able to fulfil such Order due to security and confidentiality requirements or restrictions imposed by any Singapore governmental or regulatory authority. 4.7 5.7 Where the Platform is in operation, the grounds in paragraphs 4.6(b5.6(a) and 4.6(c5.6(b) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground grounds in paragraph 4.6(a), 4.6(dparagraphs 5.6(c) or 4.6(eto 5.6(e) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for providing Co- location Services to the Contracting QP at the time, in which case this Service Schedule shall remain in force.

Order Handling. ‌ 4.1 5.1 The Contracting QP must shall place Orders for any of the following purposes each Order to take up Co-location Services in accordance with paragraph 4.25.2. The Contracting QP shall be required to specify the following in each such Order: (a) to set up one or more L3 Virtual Routing Domainsthe location of the NC CO at which Co-location Space is requested; (b) the type of equipment proposed to request Modification(s) to an Approved Project Schedule; and/orbe installed (“Co-located Equipment”); (c) to Deactivate any L3 Virtual Routing Domains which has been set up by Nucleus Connect. In relation to paragraph 4.1(a), the number of L3 Virtual Routing Domains that space and power requirements; (d) the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up weight of the L3 Virtual Routing Domain(s), Nucleus Co-located Equipment; and (e) any other information that may be reasonably requested by ▇▇▇▇▇▇▇ Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basisduring the ordering process. 4.2 5.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 5.3 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 5.4 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 5.5 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.65.6, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two three (23) Business Days after Nucleus Connect’s receipt of such Order. 4.6 5.6 Subject to paragraph 4.7, where the Contracting QP submits an Order5.7, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such any Order submitted by the Contracting QP to take up Co-location Services in any of the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by the Contracting QP is other than as set out in IETF RFC4364; (b) where such Order is not in the prescribed form; (cb) where the information in such Order is illegible, inaccurate, incomplete or incorrect; (dc) pursuant to paragraph 8.1; orunavailability of the Co-location Space at the NC CO; (ed) where the Contracting QP has committed a material breach of the ICO Agreement; or (e) where Nucleus Connect is not able to fulfil such Order due to security and confidentiality requirements or restrictions imposed by any Singapore governmental or regulatory authority. 4.7 5.7 Where the Platform is in operation, the grounds in paragraphs 4.6(b5.6(a) and 4.6(c5.6(b) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground grounds in paragraph 4.6(a), 4.6(dparagraphs 5.6(c) or 4.6(eto 5.6(e) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for providing Co- location Services to the Contracting QP at the time, in which case this Service Schedule shall remain in force.

Order Handling. ‌ 4.1 5.1 The Contracting QP must shall place Orders for any of the following purposes each Order to take up Co-location Services in accordance with paragraph 4.25.2. The Contracting QP shall be required to specify the following in each such Order: (a) to set up one or more L3 Virtual Routing Domainsthe location of the NC CO at which Co-location Space is requested; (b) the type of equipment proposed to request Modification(s) to an Approved Project Schedule; and/orbe installed (“Co-located Equipment”); (c) to Deactivate the space and power requirements; (d) the weight of the Co-located Equipment; and (e) any L3 Virtual Routing Domains which has been set up other information that may be reasonably requested by Nucleus Connect. In relation to paragraph 4.1(a), Connect during the number of L3 Virtual Routing Domains that the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up of the L3 Virtual Routing Domain(s), Nucleus Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basisordering process. 4.2 5.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 5.3 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 5.4 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 5.5 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.65.6, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two three (23) Business Days after Nucleus Connect’s receipt of such Order. 4.6 5.6 Subject to paragraph 4.7, where the Contracting QP submits an Order5.7, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such any Order submitted by the Contracting QP to take up Co-location Services in any of the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by the Contracting QP is other than as set out in IETF RFC4364; (b) where such Order is not in the prescribed form; (cb) where the information in such Order is illegible, inaccurate, incomplete or incorrect; (dc) pursuant to paragraph 8.1; orunavailability of the Co-location Space at the NC CO; (ed) where the Contracting QP has committed a material breach of the ICO Agreement; or (e) where Nucleus Connect is not able to fulfil such Order due to security and confidentiality requirements or restrictions imposed by any Singapore governmental or regulatory authority. 4.7 5.7 Where the Platform is in operation, the grounds in paragraphs 4.6(b5.6(a) and 4.6(c5.6(b) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground grounds in paragraph 4.6(a), 4.6(dparagraphs 5.6(c) or 4.6(eto 5.6(e) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for providing Co- location Services to the Contracting QP at the time, in which case this Service Schedule shall remain in force.

Order Handling. ‌ 4.1 5.1 The Contracting QP must may place Orders an Order for any of the following purposes in accordance with paragraph 4.25.2: (a) to set take up one or more L3 Virtual Routing Domains;Patching Service(s); and/or (b) to request Modification(s) to an Approved Project Schedule; and/or (c) to Deactivate any L3 Virtual Routing Domains which has been set up by Nucleus Connect. In relation to paragraph 4.1(aterminate Patching Service(s), the number of L3 Virtual Routing Domains that the Contracting QP can have per Order is limited to one hundred (100). If the Contracting QP requires a number of L3 Virtual Routing Domains which exceeds one hundred (100), or has other specific requirements on the set up of the L3 Virtual Routing Domain(s), Nucleus Connect will assess such requirements on a case-by-case basis. In such event, additional Charges will also be applicable on a cost-oriented basis. 4.2 5.2 The Contracting QP shall use the Platform to place Orders, or (only if the Platform is not in operation) shall send Orders using the application form attached to this Service Schedule by email to ▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇ (and/or such other email address as Nucleus Connect may notify the Contracting QP from time to time) in the first instance or if email is not available for any reason by facsimile to (▇▇) ▇▇▇▇ ▇▇▇▇ (and/or such other facsimile number as Nucleus Connect may notify the Contracting QP from time to time) (the latter method shall hereinafter be referred to as the “Manual Process”). 4.3 5.3 Upon the submission by the Contracting QP of an Order to take up a Patching Service, the Contracting QP shall pay Nucleus Connect the applicable Charges as set out in paragraph 10, in accordance with the Master ICO Agreement. 5.4 The Contracting QP is responsible for the acts and omissions of its Authorised Users in connection with the Platform and the Manual Process. 4.4 5.5 All Orders received by Nucleus Connect will be processed by Nucleus Connect in the order in which they are received. For Orders received via the Platform or via email, Nucleus Connect shall notify and send to the Contracting QP an acknowledgement that the Orders have been received. 4.5 5.6 Nucleus Connect shall use the Platform to notify the Contracting QP if Nucleus Connect rejects any Order submitted by the Contracting QP pursuant to paragraph 4.65.7, or (only if the Platform is not in operation) shall send such notification by email in the first instance or if email is not available for any reason by facsimile, to the email address or facsimile number of the “Primary contact person” specified in Annex 5 of the Master ICO Agreement. Any such rejection, and the reasons therefor, shall be notified to the Contracting QP as aforesaid within two (2) Business Days after Nucleus Connect’s receipt of such Order. 4.6 5.7 Subject to paragraph 4.7, where the Contracting QP submits an Order5.8, the Contracting QP acknowledges and agrees that Nucleus Connect shall be entitled to reject such any Order submitted by the Contracting QP in any of the following circumstances: (a) where the configurations for L3 Virtual Routing Domains requested by activation date or deactivation date (as the Contracting QP is other than as case may be) set out in IETF RFC4364such Order is earlier than the date falling five (5) Business Days from the date such Order is submitted; (b) where such Order is not in the prescribed form; (c) where the information in such Order is illegible, inaccurate, incomplete or incorrect;; and (d) pursuant to paragraph 8.1; or (e) where the Contracting QP has committed a material breach of the ICO Agreement. 4.7 5.8 Where the Platform is in operation, the grounds in paragraphs 4.6(b5.7(a) and 4.6(cto 5.7(c) shall not automatically entitle Nucleus Connect to reject an Order. In the event such grounds materialise, Nucleus Connect shall grant to the Contracting QP the opportunity to make the necessary corrections in real time via the Platform, without the need to re-enter all of the other correct information. If the Contracting QP does not make such correction as aforesaid, or the ground in paragraph 4.6(a), 4.6(d) or 4.6(e5.7(d) materialise, Nucleus Connect shall be entitled to reject such Order in which case this Service Schedule shall lapse, unless Nucleus Connect is separately setting up L3 Virtual Routing Domains for providing Patching Services to the Contracting QP at the time, in which case this Service Schedule shall remain in force.