(b)            on an equitable and non-discriminatory basis.
3.3.3      Customer Relationship Principles
VADS shall observe and comply with the customer relationship principles set out in section 4.3 of the MSA Determination.

CHAPTER 4: ACCESS REQUEST
4.1           Application for Access to Services
4.1.1      An Access Seeker shall request VADS to supply Access Service(s) to it by serving an Access Request in writing setting out the information listed in Section 4.1.3 below.
4.1.2      The purpose of such Access Request is to provide VADS with sufficient information to assess the Access Seeker's request for the supply of the Access Service(s).
4.1.3      The Access Seeker must provide the following information in the Access Request:
(a)            the name and contact details of the Access Seeker;
(b)            the Access Service(s) in respect of which access is sought;
(c)             whether the Access Seeker wishes to either accept this ARD and its Standard Access Obligations or negotiate an Access Agreement on different terms and conditions from that in this ARD and Standard Access Obligations;
(d)            the ready for service  date(s) for the Access  Service(s)  the Access  Seeker reasonably requires;
(e)            the names of personnel(s) whom the Access Seeker nominates to represent the Access Seeker in access negotiations with VADS and in respect of each of those personnel:
(i)              his or her contact details; and
(ii)            his or her job title; and
(f)              the identity of the negotiating team leader whom shall have the authority to make binding representations  on behalf of the Access Seeker in relation to matters arising from the access negotiations  (subject to final approval from the Access Seeker's Chief Executive Officer or Board of Directors, if required by the Access Seeker);
(g)             contain 2 copies of the Non-Disclosure Agreement properly executed by the Access  Seeker  in  the  form  prescribed  by  VADS  and  made  available  for download at  www.vads.com;
(h)            forecasts of the capacity  which the Access  Seeker reasonably  requires,  in accordance with the forecasting procedures stated in Section 5.1;
(i)              provide the relevant information relating to the Access Seeker's Network and the functionality of its services, to the extent that the Access Seeker is aware that such information may affect VADS’ Network;
(j)              relevant   information   relating   to  the  Access   Seeker’s   Network   and  the functionality of its Services, to the extent that the Access Seeker is aware that such information may affect VADS’ Network;
(k)             Creditworthiness Information as set out in Section 4.4;
(l)              Insurance Information as set out in Section 4.6; and
(m)           such other information as VADS may reasonably request.
4.2           Non-Disclosure Agreement
The Non-Disclosure Agreement attached as Schedule 1 hereto shall be executed by the Operators  in  duplicate  prior  to  any  discussion  on  an  Access  Request. It is deemed that   persons   executing   the   Non-Disclosure   Agreement   shall   be   so authorized by their respective Operators to execute the said document.
4.3           Freedom to negotiate
Without limiting its obligations under the Act, VADS shall not:
(a)            refuse to negotiate an agreement with an Access Seeker, whether or not the access sought is based on an ARD; or
(b)            refuse to provide information required under this section on the basis that the Access Seeker wished to negotiate an agreement whether the access sought is based on an ARD or otherwise.
4.4           Creditworthiness Information
                  The Creditworthiness Information that is required to accompany an Access Request includes:
(a)            a letter, signed by an executive director of the Access Seeker, stating that the Access Seeker is not insolvent and is not under any external administration or under similar form of administration  under any laws applicable  to it in any jurisdiction; and
(b)            a  copy  of  the  Access  Seeker's  most  recently  audited  balance  sheet  and audited profit and loss statement.
4.5           Security Sum
4.5.1      VADS shall ensure that the amount and type of security requirements imposed on the Access Seeker in VADS’ security policy, commensurate with:
(a)            the estimate of the value of access to Access Service(s) to be provided to the Access Seeker by VADS over a 90 day period (“Minimum Value”);
(b)            the creditworthiness of the Access Seeker (including prior payment records of the Access Seeker); and
(c)             the security previously reasonably required by VADS (if any).
4.5.2      The Access Seeker must provide the Security Sum to VADS in the form of a Bank Guarantee.
4.5.3      VADS is not obliged to consider entering into an Access Agreement with the Access Seeker  pursuant  to this  ARD  until  the  Access  Seeker  has amongst  other things, provided (at the Access Seeker's costs) to VADS such Security Sum on terms and conditions reasonably acceptable to VADS.
4.6           Insurance Information
4.6.1      Subject to Section 4.6.2, an Access Request shall be accompanied by the following insurances:
(a)            Worker's Compensation  and/or Social Security Insurance and/or Employer's liability Insurance and/or other insurance within statutory limits as required by the laws of Malaysia to provide for payment to its employees employed or in connection  with  the  work  covered  by  the  Access  Agreement  that  may  be entered into and/or their dependants; and
(b)            Comprehensive General Liability Insurance or Public Liability Insurance of an amount  which  is  not  in  excess  of  RM20,000,000.00  for  any  one  claim  or series of claims arising out of an accident or occurrence in connection  with the  Access  Agreement  that  may  be  entered  into  resulting  in  bodily  injury and/or personal injury including death and property damage of an Operator which shall arise out of or in consequence  of any acts of omissions  of the Other Operator. Such policy shall include contractual liability.
4.6.2      For  the  purpose  of  clarification,  the  insurance  provided  by  the  Access  Seeker pursuant to Section 4.6.1 shall be commensurate with the reasonable sum which is to be agreed by VADS.

4.7           VADS’ Response to Access Request
4.7.1      VADS shall within ten (10) Business  Days of receipt of the Access  Request, inform the Access Seeker in writing that it has received the Access Request and either:-
(a)            request for additional information from the Access Seeker where there is a need for further information and a joint site survey in the case of Network Co- location Service, prior to considering the Access Request. VADS shall comply with Section 5.4.16 of the MSA Determination when it requests for such additional information; or
(b)            indicate  if  it  is  willing  to  provide  access  to  the  Access  Service(s)  under Section 4.10 or if it is rejecting the Access Request in accordance to Section 4.9;
(c)             If VADS  is  willing  to  provide  access  to the  Access  Service(s),  VADS  shall (together  with its notice of acceptance)  indicate  the Security  Sum and any non  refundable  processing  fee  payable  by the  Access  Seeker  prior to the execution of the Access Agreement.
4.7.2      If VADS requests for additional  information  under Section 4.7.1(a) and the Access Seeker  provides  the requested  information  to VADS’ satisfaction  and the joint site survey (if any) is successfully completed, VADS shall within ten (10) Business days of such response, provide the Access Seeker with a response under Section 4.7.1(b).
4.7.3      Resource charge
In accordance with Section 5.7.28 of the MSA Determination, VADS may charge an Access Seeker a one-off resource charge to be determined by reference to the costs incurred by VADS for the allocation of manpower and other resources to enable the Access Seeker to test and provide new Access Service(s).
4.8           Rejection of an Access Request
4.8.1      VADS may refuse to accept an Access Request for supply of the Access Service(s) and accordingly may refuse to supply that Access Service(s) to the Access Seeker for any of the following reasons:
(a)            in  VADS'  reasonable  opinion,  the  Access  Request  does  not  contain  the information reasonably required by this ARD provided that VADS has sought the information from the Access Seeker under Section 4.7.1(a) of this ARD;
(b)            VADS does not currently supply or provide access to the requested network facilities or network services listed in the Access List to itself or to any third parties;
(c)             it  is  not  technically  feasible  to  provide  access  to  the  requested  Access Service(s);
(d)            VADS has insufficient capacity to provide the requested Access Service(s);
(e)            there  are reasonable  grounds  in VADS'  opinion  to believe  that the  Access Seeker  would  fail  to  make  timely  payment  for  the  supply  of  the  relevant Access Service(s); or
(f)              there  are reasonable  grounds  in VADS'  opinion  to believe  that the  Access Seeker  would  fail,  to  a  material  extent,  to  comply  with  the  terms  and conditions applicable to the supply of the regulated Access Service(s).
4.8.2      Determination of technical infeasibility
For the purpose of determining technical infeasibility in Section 4.8.1(c), the Operators shall comply with Section 5.4.17 of the MSA Determination.
4.8.3      Determination of capacity constraints
For the purpose of determining capacity constraints   in Section   4.8.1(d),   the Operators shall comply with Section 5.4.18 of the MSA Determination.
4.8.4      Assessment of the Access Seeker's ability to pay for the supply of Access Service(s)
Examples of reasonable grounds for VADS' belief as mentioned in Section 4.8.1(f) include evidence that the Access Seeker is not (in the reasonable opinion of VADS) creditworthy.
4.9           Notification of Rejection to the Access Seeker
4.9.1      If VADS rejects the Access Request, VADS shall within ten (10) Business Days of receiving the Access Request:
(a)            notify the Access Seeker in writing of VADS’ rejection;
(b)            provide reasons for rejection under Section 4.8 to the Access Seeker;
(c)             provide the basis for VADS' rejection of the Access Request; and
(d)            indicate a date and time,  not later seven (7) Business  Days  from the date of this notice of rejection, at which representatives of VADS will be available to meet with  representatives  of  the  Access  Seeker  to  discuss  the  rejection  of  the Access Request.
4.9.2      If the Operators are unable to resolve their differences following the meeting held pursuant to Section 4.9.1(d), either Operator may request resolution of the dispute in accordance with the Dispute Resolution Procedures.
4.10        Acceptance of an Access Request
4.10.1  Where  the Access  Seeker  has requested  under  Section  4.1 and VADS  agrees  to provide access to the Access Service(s) to the Access Seeker in accordance  with this  ARD,  VADS  shall  within  ten (10)  Business  Days  of  such  response  under  Section 4.7.1(b),  provide  the  Access  Seeker  with  an  Access  Agreement  (based  on  the Standard Access Obligations) that includes the Charges for execution by the Access Seeker.
4.10.2  With respect  to Section 4.10.1, the Access  Seeker shall within ten (10) Business  Days either, execute and return the Access Agreement  to VADS or indicate in writing to VADS  that  it  wishes  to  negotiate  the  Access  Agreement  on  different  terms  and conditions.
4.11        Access Seeker elects to negotiate the Access Agreement
4.11.1  (a)            If the Access Seeker elects to negotiate the Access Agreement under Section 4.1.3(c), VADS must set a date and time not later than fifteen (15) Business Days from the date of VADS’ response pursuant to Section 4.7.1(b) at which VADS’ representatives will be  available for an initial meeting with  the  Access Seeker’s representatives;
(b)            If the Access Seeker elects to negotiate the Access Agreement under Section 4.10.2, VADS must set a date and time not later than fifteen (15) Business Days from the  date  of the  Access  Seeker’s  response  under  Section  4.10.2  at  which VADS’ representatives  will be available for an initial meeting with the Access Seeker’s representatives.
4.11.2  The Operators shall comply with the requirements in Sections 5.4.2, 5.4.3 and 5.4.15 of the MSA Determination in concluding an Access Agreement.
4.11.3  Operators must use their best endeavours to conclude the Access Agreement within 120 days of the Access Seeker’s Access  Request [Please refer to the negotiation procedures   set  out  in  Section  5.4.9  to  5.4.18  in  the  MSA  Determination].   If negotiations are not completed within the 120 day period:
(a)            the  Operators  may  jointly  apply  to  the  Commission  for  further  time  to negotiate - if the further time is not granted, the Operators are deemed to be in dispute and the Dispute Resolution Procedures  in the MSA Determination will take effect; or
(b)            either Operator may initiate the Dispute Resolution Procedures in the MSA Determination.
4.11.4  VADS will not be taken to have agreed to provide, and the Access Seeker will not be taken to have agreed to acquire the requested Access Service(s) until:
(a)            a  Security  Sum  has  been  provided  in  accordance  with  Sections  4.5  and Section 4.7.1(c); and
(b)            an Access Agreement has been executed between the Operators.
4.12        If Access Seeker already has an Access Agreement with VADS
4.12.1  If  an  Access  Seeker  already  has  an  Access  Agreement  with  VADS,  the  Access Seeker  may ask VADS to provide  the Access  Service(s)  based  on the terms  and conditions of its existing Access Agreement with VADS.
4.12.2  The Access Seeker shall submit its Access Request in the manner specified in the existing Access Agreement with VADS. If the existing Access Agreement does not specify how to submit an Access Request, the process set out in this VADS ARD must be followed.
4.12.3  In the Access Request, the Access Seeker must also:
(a)            specify the Access Service(s) to which access is being requested; and
(b)            confirm that the terms and conditions of the existing Access Agreement with VADS are to apply to the requested Access Service(s).

CHAPTER 5: TECHNICAL AND OPERATIONS
5.1           Forecasting Obligations
5.1.1      General.   Subject to subsections 5.1.2 and 5.1.3, VADS may require, as a condition to providing access to the Facilities or Services   (requested by the Access Seeker), that  the  Access  Seeker  provide  Forecasts  in good  faith  over  a  certain  period  of supply of access to Facilities or Services   (as the case may be) in accordance with this Section 5.1.1.
5.1.2      Confirmation of Forecast.  If VADS,  acting reasonably  will incur significant  costs to ensure  that  access  can  be  provided  in  accordance  with  a  Forecast,  VADS  may request the Access Seeker to confirm the relevant Forecast.   Once confirmed, the Forecast is deemed to be an Order for the purposes of this ARD, and Section 5.2 will apply.
5.1.3      Alternative procedure.  VADS  and  an  Access  Seeker  may  agree  to  an  alternative Forecasting  procedure other than that set out in this Section 5.1. If agreement is reached about such matters, VADS and Access Seeker will be bound by the terms of that alternative procedure and not this Section 5.1.
5.1.4      Non-binding.   Subject to Section 5.1.2, VADS shall not require an Access Seeker:
(a)            to provide Forecasts that are legally binding on the Access Seeker, subject to Section 5.1.14; or
(b)            to   provide   information   in   its   Forecast   that   identifies   or   would   allow identification of Customers.
5.1.5      Forecast request. VADS may  request  an  Access  Seeker  to  provide,  with  a sufficient level of detail to enable VADS to carry out Network planning, the following information (forecast information):
(a)            the Facilities or Services or both in respect of which Forecasts are  required;
(b)            the total period of time covered by each Forecast, which period:
(i)              shall  be  determined   having  regard  to  VADS’   own  planning  and provisioning cycles and the Forecasting requirements  which apply to the  Access  Seeker’s  own business  units  in  using  the  relevant Facilities or Services; and
(ii)            shall  be  no  longer  than  one  year,  unless  reasonably  justified on grounds  of  the  special  Network  management  requirements of the relevant Facilities or Services.
(c)             the intervals or units of time to be used in making the Forecast, which  shall be no longer than three (3) months unless reasonably justified on grounds of the special  Network  management  requirements  of  the relevant  Facilities  or Services;
(d)            the Network area or operational area to which Forecasts shall relate, which area shall correspond to that which VADS uses  for its own Network planning;
(e)            the frequency  with which a Forecast  shall be updated or further Forecast made,  which  shall  not  be  more  frequently  than  every three (3)  months  unless reasonably   justified   on   grounds   of   the   special   Network   management requirements of the relevant Facilities or  Services ; and
(f)              such other information  that VADS  reasonably  requires  in order to provide access to Facilities or Services  requested by the  Access Seeker.
5.1.6      Forecast Provision. VADS may only require an Access Seeker to provide Forecasts in accordance with a Forecast Request:
(a)            no sooner than four (4) weeks after receipt of a Forecast Request; and
(b)            until such time as VADS notifies the Access Seeker in writing that it withdraws the relevant Forecast Request.
5.1.7      Use of Forecast Information.  Forecast Information provided by the Access Seeker shall be treated by VADS as the Confidential Information of the Access Seeker and shall only be used by VADS for the purposes of responding to and planning for the Forecast and providing the Services requested by the Access Seeker.
5.1.8      Distribution of Forecast Information.  VADS  may only distribute  Forecast  Information of an Access  Seeker outside the people necessary  for the purpose referred to in Section 5.1.7 if:
(a)            the Forecast Information of the Access Seeker is aggregated with  Forecasts provided by other Operators and VADS’ own   requirements (so as to protect the confidentiality of the Forecast  Information); and
(b)            the Forecast Information  or its use does not otherwise identify the   Access Seeker in any manner.
5.1.9      Time for acceptance. VADS shall notify the Access Seeker:
(a)            within five (5) Business Days of receiving the Forecast if VADS considers that the Forecast does not comply with a Forecast  Request, specifying in that notice the additional information which the  Access Seeker  is to provide; and
(b)            within fifteen (15) Business  Days of receiving  a Forecast  which               complies with the Forecast Request, that the Forecast is accepted.
5.1.10  Reasons for rejection. VADS  may  only  reject  a  Forecast  where  VADS  reasonably believes that the Forecast is inaccurate, having regard to:
(a)            total current usage of the Facilities or Services;
(b)            the current rate of growth of the Access Seeker’s usage of the   Facilities or Services;
(c)             the current rate of growth of total usage of the Facilities or Services;  and
(d)            the amount of capacity in the Facilities or  Services that VADS currently has available and can  reasonably provision over the Forecast period, which shall be at least equivalent  than that which VADS can reasonably  provision  for itself.
5.1.11  Time for rejection. VADS shall give notice of any rejection to the Access Seeker:
(a)            within fifteen (15) Business Days of receipt of the relevant Forecast;  and
(b)            such notice of rejection shall specify:
(i)              the grounds on which VADS rejects the Forecast in accordance  with Section  5.1.10,  at a sufficient  level of     detail to enable  the Access Seeker  to understand the basis of  the rejection and to undertake its own re-assessment of the  Forecast; and
(ii)            an offer to meet within five (5) Business Days of the notice of  rejection of the  Forecast  to  discuss  the  reasons  for  rejection                and  alternative methods of compliance.   The meeting shall take place between VADS and  Access  Seeker  if the  offer  is  accepted  by  the  Access  Seeker (Rejection  Notice).
5.1.12  Reconsideration by Access Seeker.  VADS shall allow an Access Seeker to reconsider its Forecast following a Rejection  Notice and allow the Access Seeker, within twenty one (21) Business Days of receipt of a Rejection Notice, either:
(a)            to confirm its rejected Forecast, and explain why the Access Seeker  regards the Forecast as being reasonable; or
(b)            to submit  a  new  Forecast  which  the  Access  Seeker  regards  as meeting VADS’ concerns.
5.1.13  Reconsideration by Access Provider. VADS shall reconsider any amended Forecast provided pursuant to Section 5.1.10 and Sections 5.1.9 to 5.1.11 shall re-apply.
5.1.14  Recovery  for  over-Forecasting.  VADS  shall  not  seek  to  recover  any  costs  or expenses incurred due to its acceptance of a Forecast from an Access Seeker if the Forecast is not met by the Access Seeker unless:
(a)            such  costs  and  expenses  were  reasonably  and  necessarily  incurred by VADS;
(b)            VADS reasonably seeks to mitigate its loss over a six month period (including through its own usage); and
(c)             VADS  only  recovers  from  the  Access  Seeker seventy five percent (75%)  of  such  costs  and expenses which could not be mitigated under Section 5.1.12(b) above.
5.1.15  Meeting Forecasts. Subject to Sections 5.1.7 to 5.1.12, VADS shall carry out network planning in order to enable the Forecast Requested to be met.  If an Access Seeker has confirmed a forecast under Section 5.1.2, it will be binding on the Access Seeker.
5.2           Ordering And Provisioning Obligations
5.2.1      Contact point. VADS shall designate a person to whom Orders for access to Facilities and  Services  are  to  be  delivered  and  shall  notify  the  Access  Seeker  of  the designated person from time to time.
5.2.2      Order content.  Prior to access being provided, VADS may require an Access Seeker to provide it with an Order which outlines the Access Seeker’s access requirements. VADS may request an Access Seeker to provide, at a level of detail (sufficient for planning provisioning), the following information in an Order for access to Facilities and Services:
(a)            the Facilities or Services or both to which access is requested;
(b)            a requested time for delivery;
(c)             the location of the points of delivery;
(d)            Equipment of the Access Seeker to be used in connection with the Order; and
(e)            such other information that VADS reasonably requires in  Order for it to plan for the provision of access to the Facilities or  Services as requested by the Access Seeker.
5.2.3      Use of ordering information.  Ordering  information  provided  by the Access  Seeker shall be treated by VADS as the Confidential Information of the Access Seeker and shall  only  be  used  by  those  persons  for  the  purpose  of  responding  to  and provisioning for the Order.
5.2.4      Treatment of Orders and Service Qualifications.  VADS shall give the same priority to the handling of Orders from the Access Seeker and any Service Qualifications that may be required for that Access Seeker as it gives to its own Orders and Service Qualifications and any Orders and   Service Qualifications that may be required for Customers who are similarly situated to the Access Seeker in all relevant respects.
5.2.5      Acknowledgment of receipt. VADS shall acknowledge receipt of the Order, in writing (or any other material or electronic form agreed by the parties), within (two) 2 Business Days of receipt of an Order from the Access Seeker.
5.2.6      Notice of Receipt. VADS shall include in its Notice of Receipt the following information:
(a)            the time and date of receipt;
(b)            a list  of  any  additional  information  reasonably  required  by  VADS  from  the Access Seeker to clarify the Order; and
(c)             if  the  relevant  Facilities  or  Services  are  below  the  capacity  required  to provide  the  relevant  Facilities  or Services,  VADS  shall                  inform the Access Seeker of the available capacity and timeframe for the fulfillment of the Order.
5.2.7      Further information.  VADS  shall  allow  the  Access  Seeker  a  period  of  up  to  fourteen (14) Business Days after a request for additional information to provide VADS with such additional reasonable information that is reasonably necessary to clarify an Order.
5.2.8      Service Qualifications. VADS shall only conduct Service Qualifications if:
(a)            VADS reasonably requires information from such Service Qualifications which is not readily available; and
(b)            VADS   notifies   the  Access   Seeker  that  such  Service   Qualifications   are necessary within 5 Business Days of receiving the Access Seeker’s Order, or, if  further  information  has  been  requested  under  Section  5.2.7,  within  five (5) Business Days of the  expiry of the period in Section 5.2.7, together with the reasons for  such Service Qualifications.
For clarification, an Access Seeker may also seek the consent of VADS to perform a Service Qualification itself, and such consent shall not be unreasonably withheld.
5.2.9      Completion of Service Qualifications. VADS shall:
(a)            complete any Service Qualification in respect of an Order within twenty one (21) Business Days of the commencement of the Service  Qualification;
(b)            inform the Access Seeker of the result of any Service Qualification within two (2) Business Days of the completion of such Service  Qualification.
5.2.10  Withdrawal of Order following Service Qualifications. VADS shall permit an Access Seeker to withdraw its Order without penalty within fourteen (14) days after receiving the result of a Service Qualification under Section 5.2.9.
5.2.11  Acceptance  obligation.                 VADS  shall use its reasonable  efforts  to accept  and fulfill Orders  from  the  Access  Seeker  for  Services  and  Facilities  which  comply  with  a Forecast accepted by VADS pursuant to Section 5.1.
5.2.12  Time for acceptance/rejection.   VADS shall notify the Access Seeker within fourteen (14) days of receiving an Order that the Order is accepted or rejected, save where VADS undertakes a Service Qualification as contemplated in Section 5.2.8, in which case the time periods in Section 5.2.9 are to be added to this fourteen (14) days period. If VADS notifies the Access Seeker that an Order is rejected, VADS shall advise the Access Seeker if it would be able to accept the Order in a modified form.
5.2.13  Notice of acceptance.   VADS’ notice of acceptance to the Access Seeker shall contain the following information:
(a)            the delivery date, which shall be the date that is requested by the Access Seeker, or if that date cannot be met by VADS, shall be no later than the indicative delivery timeframes set out in Section 5.2.14;
(b)            the charges applicable to the fulfillment of the Order;
(c)             such information as is reasonably necessary for the Access Seeker to benefit from access to the network services or network facilities;
(d)            the validity period of the acceptance of the Order which shall be no less than ninety (90) days from the date of acceptance.
5.2.14  Indicative delivery times.  For the purposes of Section 5.2.13(a), the following are the indicative delivery timeframes for the following aspects of a  Facilities or Services:

Order type	Indicative delivery timeframes
All Orders involving the provision of new Facilities and infrastructure relevant to the Services that are the subject of the Order	8 Months
All Orders involving augmentation of capacity on existing Facilities and infrastructure relevant to the Services that are the subject of  the Order	60 days

(a)            The indicative delivery timeframes specified in Section 5.2.14 shall commence from   the   date   the   Access   Seeker   confirms   an   Order   in accordance with Section 5.2.15.
(b)            Where a delay in the delivery of an Order is caused by the Access Seeker, the delivery date specified in the confirmed Order or indicative delivery time set out above shall be extended for a further period as   may be reasonably necessary by VADS.
5.2.15  Access Seeker confirmation. VADS shall permit an Access Seeker to confirm its agreement to proceed with the Order within the validity period of VADS’ acceptance of such Order (as described in Section 5.2.13(d)). Upon such confirmation, VADS shall fulfill the Order in accordance with the notice of acceptance provided under Section 5.2.13.
5.2.16  Estimated  charges. If the notice of acceptance provided by VADS under Section 5.2.13 contains estimates of charges (e.g. based on time and materials):
(a)            VADS shall not exceed the estimate without providing the Access Seeker with written notice prior to exceeding the estimate that:
(i)              the estimate will likely be exceeded;
(ii)            an explanation of the reasons for exceeding the estimate; and
(iii)           a further estimate of the charges for the work necessary to fulfill  the Order.
(b)            VADS shall permit the Access Seeker to withdraw the Order without penalty if the revised estimate exceeds the original estimate by more than ten percent (10%) of the original estimate within 14 days of the notice given by VADS under Section 5.2.16(a).
(c)             where  the  actual  cost  incurred  by  VADS  exceeds  an  estimate  or  revised estimate for a specific scope of work provided by  VADS due to:
(i)              information or facts provided by  the  Access   Seeker   which  are inaccurate or erroneous or not disclosed by the Access  Seeker; and
(ii)            a change in the scope of work by the Access Seeker,
the Access Seeker shall be obliged to pay VADS for the  actual cost incurred.
(d)            VADS  shall  commence  work  after  the  Access  Seeker  confirms  that  it  is agreeable  to  the  estimate  or  revised  estimate,  such  confirmation  to  be provided by the Access Seeker within fourteen (14) days from the notice given by VADS under Section 5.2.6(a).
5.2.17  Reasons  for  rejection:                   VADS  may  only  reject  an  Order  from  an  Access  Seeker where:
(a)            it is not technically  feasible to provide   access to the Facilities  or Services requested by the Access Seeker;
(b)            VADS has insufficient capacity to provide the requested Facilities or Services;
(c)             subject to Section 5.2.19, the Order is in excess of agreed  Forecast levels;
(d)            the Order or variation request duplicates an Order awaiting fulfillment;
(e)            the  Access  Seeker  has  not  obtained  necessary  related  agreements from VADS (e.g. Facilities access for a new Point of  Interface);
(f)              there are reasonable grounds to believe that the Access Seeker would fail, to a material  extent,  to comply  with the terms and conditions  of the Access Agreement; or
(g)             there are reasonable grounds to believe that the Access Seeker would  fail, in connection with the supply of the Facilities or Services to  protect the integrity of  a  Network;  or  the  safety  of  individuals  working on, or using services supplied by means of, a Network or Equipment.
5.2.18  Notice of rejection. VADS’ notice of rejection to the Access Seeker shall:
(a)            set out the grounds on which VADS rejects the Order, at  a sufficient level of detail to enable the Access Seeker to understand   the basis of the rejection and to undertake its own re-assessment of  the Order; and
(b)            offer to meet, and meet if the offer is accepted by the Access Seeker,  within five (5)  Business  Days  of  the  notice  of  rejection  of  the  Order  to discuss  the reasons for rejection and alternative methods of  compliance.
5.2.19  Order in excess of Forecast. Notwithstanding Section 5.2.17(b), VADS shall use its reasonable efforts to provide sufficient capacity to enable VADS to accept and fulfill Orders from an Access Seeker for Facilities or Services or both which are in excess of the relevant Forecast. VADS  is  only  required  to  do so  if,  after  meeting  the Forecast requirements  of other Operators  and of its own business units, there   is available  capacity  or VADS  could  readily  upgrade  existing capacity. VADS shall allocate  the  available  capacity  on  a  nondiscriminatory   basis  to  meet  the  over Forecast requirements of the Access Seeker, other Operators and its own business units. VADS  is not required  to supply  Facilities  or Services  or both in excess  of Forecast if, despite adopting any reasonable improvements (including upgrading capacity),  this  would  cause  a  material  degradation  in  the  quality  of  Forecast Services provided to other Operators or its own business or both.
5.2.20  Required extra capacity.  VADS  may  require  an  Access  Seeker  to  procure  such additional capacity on the Access Seeker’s side of the Network as VADS, in good faith  and  reasonably  estimates,  may  be  required  by  the  Access  Seeker  to  meet demand. Where the Access Seeker fails to so procure additional capacity and the demand exceeds the   capacity on the Access Seeker’s Network, VADS shall notify the Access Seeker in writing, and the Access Seeker and the Access  Provider shall meet  (no  later  than  five (5)  Business  Days  after  receipt  of  the  notice      from  VADS)  to attempt to identify alternative sources of  capacity.  If the matter cannot be resolved within 10 Business Days of the date of that meeting, VADS may bar or block calls to the Access Seeker’s Network to the extent necessary to minimise congestion within VADS’ Network.
5.2.21  Other uses. VADS shall permit capacity installed in connection with the provision of a network service to be used, to the extent technically feasible, in connection with another network service, at the Access Seeker’s option.
5.2.22  Delivery dates. VADS shall deliver the ordered access to Facilities or Services by the date specified in the notice of acceptance (as provided under Section 5.2.13).
5.2.23  Early delivery dates. If VADS, in the normal course of business, is able to offer a delivery date earlier than the delivery date that would otherwise apply, it shall advise the Access Seeker and, if requested by   the Access Seeker, deliver access to the relevant Facilities or Services or both at the earlier delivery date.
5.2.24  Delayed delivery dates. VADS shall:
(a)            notify  an  Access  Seeker  of  the  delay  to  a  delivery  date  and  the  revised delivery date, together with the reasons for the delay, as soon as  practicable after VADS becomes aware of the possible  delay;
(b)            permit the Access Seeker notified under Section 5.2.24(a) above to cancel the Order without penalty if the delay is longer than fourteen (14) days; and
(c)             provide the Access Seeker with a remedy in accordance with Section 5.2.33.
5.2.25  Cancellation and variation of Orders.  If an Order is cancelled or varied by an Access Seeker, VADS may ask the Access Seeker to pay any cost reasonably incurred by VADS in respect of the Order.
5.2.26  Testing and provisioning. VADS shall:
(a)            co-operate with the Access Seeker in relation to the testing and  provisioning of ordered Facilities or Services or both; and
(b)            treat an Access Seeker’s testing and provisioning on an equivalent basis to that which VADS treats itself.
5.2.27  Resource charge.  VADS  may  charge  the  Access  Seeker  a  one-off  fee,  to  be determined by reference to the costs incurred by VADS for allocation of manpower and other resources to enable the Access Seeker to test and provide a new Facilities or Services for purposes of interconnection.
5.2.28  Constrained capacity.  If VADS reasonably believes that the capacity in any Facilities or Services required by:
(a)            the Access Seeker pursuant to the relevant Forecast;
(b)            other Access Seekers, pursuant to their relevant Forecasts; and
(c)             VADS, for its own purposes would, in aggregate, exceed the capacity which VADS will be in a position to be able to provide, VADS shall:
(i)              notify the  Access  Seeker  and  other  persons   to  whom  relevant capacity is supplied; and
(ii)            allocate the available capacity between itself, the Access  Seeker and other  Access  Seekers  in  accordance  with  the Access  Provider’s Capacity Allocation Policy.
5.2.32  Capacity Allocation Policy.  If VADS is likely to claim that it has insufficient capacity to meet an Access  Seeker’s  Forecasts  or Orders, VADS shall maintain a Capacity Allocation Policy, which:
(a)            shall be disclosed, free of charge, to any other Operator on request;
(b)            shall set out the principles  in accordance  with which the Access Provider shall determine how to allocate capacity between itself (including its related bodies corporate) and other Operator or  Operators, in circumstances where the  amount  of  capacity  available  is      less  than  the  aggregate  of  capacity required  by  VADS, its  related  bodies  corporate  and  other  Operator  or Operators;
(c)             shall:
(i)              be fair and reasonable;
(ii)            be consistent, so far as practicable, with VADS’ general duty of non-discrimination in accordance with  subsection 149(2) of the Act;
(iii)           treat the requirements of the Access Seeker and third parties on an equivalent basis to VADS’ own  requirements; and
(iv)           allocate the available capacity in the relevant Facilities or  Services or both in proportion to each Operator’s Forecast  requirements.
5.2.33  Late delivery.  If VADS fails to meet any timeframe in Section 5.2.14 with respect to the  delivery  of  access  to  Facilities  or  Services  pursuant  to  an  Order  made  in accordance with Section 5.2, except where such failure has been caused solely by the  Access  Seeker’s  delay,  VADS  shall,  without  limitation  to any  other  rights  the Access Seeker may have under Section 5.2 or law, provide a rebate to the  affected Access  Seeker. The  rebate  shall  be  for  an  amount  equivalent  to  the  recurring charges payable for access to the Facilities or Services over a period equal to the period of VADS’ delay.
5.3           Network Conditioning Obligations
5.3.1      Non-discrimination. VADS shall perform Network Conditioning on an equivalent basis to that which VADS performs for itself for the same or similar Services.
5.3.2      Impact of retail commercial arrangements. VADS shall not refuse to commence  or complete  Network  Conditioning  on  the  basis  that  the  commercial  arrangements (other than matters required under Section 5.3.3 to perform Network Conditioning) are not agreed                  between the parties in relation  to the retail service for which the Network  Conditioning is to be provided.
5.3.3      Commencement. VADS   shall   commence   Network   Conditioning   immediately following receipt of an Order from an Access Seeker and agreement by VADS and the Access Seeker in relation to:
(a)            geographical coverage;
(b)            number information (i.e. length and code allocation);
(c)             origins from or destinations to which access is required;
(d)            Network routes (including which Operator is responsible for the provisioning of the Interconnection Links); and
(e)            handover arrangements and relevant Points of Interface.
5.3.4      Intra-Network codes and numbers.  Section 5.3.4 does not apply to codes or number ranges not intended for use across interconnected Networks.
5.3.5      Costs.  The costs incurred in Network Conditioning shall be apportioned between the Operators as follows:
(a)            if  the  work  has  been  carried  out  in  accordance  with  a  Government  or Commission requirement, the Operators will bear their own costs;
(b)            if the work has been carried out to fulfill an Order made in accordance  with this Standard, the costs shall be apportioned in an equitable manner between the Operators having regards to cost causation.
5.4           Point Of Interface Procedures
5.4.1      Interconnection. Each Operator                shall interconnect and keep its Network interconnected with the Network of another Operator in accordance with the terms of an Access Agreement with that Operator.
5.4.2      Point of Interface locations. Subject to Section 5.4.3, VADS shall publish on its website and keep updated a list of the general locations at which physical co-location is available.
5.4.3      Lack of space. If there are space constraints at a particular location, VADS shall take reasonable steps to optimise its usage of the space, including through the upgrading of Facilities. If VADS has used its best efforts to accommodate all Access Providers and it is not physically possible for any further Access Seekers to be accommodated, the Access Provider shall be excused from providing physical interconnection at such location.
5.4.4      Access Seeker requested Point of Interface.  VADS shall reasonably consider a request by an Access Seeker to interconnect at a point other than that specified under Section 5.4.2.   VADS shall promptly accept or reject a request by an Access Seeker under this Section, and provide the Access Seeker with reasons if it rejects the Access Seeker’s request.
5.4.5      Network responsibility.                 Each  Operator  is  responsible  for  the  provisioning and maintenance   of   Facilities   (including   those   Facilities   which   form   part   of   the Interconnect  Links  and  the  transmission  equipment)  on  its  side  of  the  Point  of Interface.
5.4.6      Point of Interface factors.   When determining which locations are to be listed under Section  5.4.2,  or  when  determining  a  request  under  Section  5.4.6,  each  Access Provider shall have regard to the following:
(a)            VADS  shall  offer  interconnection  and  co-location  at  any  other  technically feasible point;
(b)            VADS  may  offer  more  than  one  form  of  interconnection  in  relation  to  a particular location (e.g. physical interconnection and virtual interconnection);
(c)             VADS shall not reserve space other than for its own current needs, its future needs  (calculated  by use of a reasonably  projected  rate of growth  over 2 years) and the needs of other  Access Seekers who are currently occupying or have Ordered  additional space from VADS; and
(d)            any possible re-arrangement of its Equipment configuration to eliminate space inefficiencies.
5.5           Decommissioning Obligations
5.5.1      Decommissioning notice.  Except where VADS is required to vacate the site where a Point of Interface is located as a result of a third party landlord’s notice (under an arm’s length tenancy agreement), an Access  Provider shall provide no less than:
(a)            one (1)  year’s  notice  in  writing  to  all  relevant  Access  Seekers  prior  to  the decommissioning of a Point of Interface; or
(b)            six (6)  month’s  notice  in  writing  to  all  relevant  Access  Seekers  prior  to  the decommissioning of any other Facilities or Services.
Where VADS is required to vacate the site where a Point of Interface is located as a result of a third party landlord’s notice (under an arm’s length tenancy agreement), VADS shall provide all relevant Access Seekers with as much notice as possible in relation to the matters in Sections 5.5.1(a) and 5.5.1(b) above.
5.5.2      Co-operation.  VADS shall co-operate and negotiate with all relevant Access Seekers in relation to the timetable for decommissioning of the relevant Point of Interface, Facilities or Services.
5.5.3      Alternative arrangements.  VADS which notifies an Access Seeker of its intention:
(a)            to decommission  a Point of Interface,  shall provide to the Access Seeker functionally equivalent interconnection at another Point of  Interface on terms and conditions and at a recurring charge which are  not disadvantageous to the Access Seeker, relative to the terms and  conditions and recurring charge applying  in  respect  of  the  Point  of Interface  that  is  proposed  to  be decommissioned,  for  a  period  not  less than three (3)  years  from  the  date  of decommissioning; or
(b)            to decommission another Facilities or Services, shall provide to the  Access Seeker  access  to  an  alternative   Facilities  or  Services   on  terms and conditions and at a recurring charge which are not   disadvantageous  to the Access  Seeker,  relative to the terms and conditions and recurring  charge applying in respect of the Facilities or Services that is proposed to be decommissioned, for a period not less than 3 years from the date of decommissioning.
5.6           Network Change Obligations
5.6.1      Scope.  This  Section  5.6.1  applies  where  an  Operator  proposes  to  implement  a Network Change of a type referred to in subsection which necessitates a change in the hardware or software (including interface software) of the other Party’s Network in Order to ensure the continued   proper operation and compatibility of the Parties’ respective Networks, services and procedures.
5.6.2      Types of changes:  The following kinds of proposed Network Changes maybe within the scope of Section 5.6.1:
(a)            any change by the Party proposing to make the change (Notifying Party) to any technical specification of the interconnection interface between their respective Networks (Interface Change);
(b)            any   change   by   the   Notifying   Party   to   any   technical   specification   or characteristic of the Facilities or Services to which the other Party (Recipient Party) has access which will or might affect:
(i)              the Recipient Party’s Network;
(ii)            the Recipient Party’s use of the Facilities or Services provided by the Notifying Party (Service Change);
(c)             any   change   by   the   Notifying   Party   to   any   technical   specification   or characteristic of that Notifying Party’s Network which will or might   affect the Recipient Party’s Network (Network Change);
(d)            any change by the Notifying Party to any of the operational support systems used in intercarrier processes, including without limitation:
(i)              the billing system;
(ii)            the Ordering and provisioning systems; or
(iii)           the Customer Churn process (OSS Change); and
(e)            any  enhancement   by  the  Notifying   Party  of  the  features,   functions   or capabilities  of  the  Facilities  or  Services  to  which  the  Recipient  Party  has access, which enhancement the Notifying Party proposes to make  available either:
(i)              to itself; or
(ii)            to any other Operator (Functionality Change), (collectively, Relevant Changes).
5.6.3      Notification of change:  If a Notifying Party proposes to make a Relevant  Change to  its  Network,  services  or  procedures,  the  Notifying  Party  shall                 provide  the Recipient Party with notice in writing (Change Notice) of:
(a)            the nature,  effect,  technical  details  and  potential  impact  on the Recipient Party’s Network of the proposed Relevant Change,  described at a sufficient level of detail to enable the other Party to  identify and begin planning such changes as may be necessary or  desirable for the Recipient Party to make to its Network, services or  procedures in consequence of the Relevant Change; and
(b)            a date, which shall be no later than 10 Business Days from the  date of the notice under this clause, on which representatives of the  Notifying Party will be  available  to  discuss  with  representatives   of  the  Recipient  Party  the proposed  Relevant  Change  and  the  changes  that  may  be  necessary  or desirable  for  the  Recipient  Party  to  make  to  its  Network,  services   or procedures in consequence of the Relevant  Change,
as soon as reasonably practicable and, in any event, with not less than the relevant notice period set out in the table below:

Relevant Change:	Notice period:
Interface Change	3 months
Network Change	3 months
Service Change	3 months
OSS Change	3 months
Functionality Change	3 months

5.6.4      Post-notification procedures.  The Notifying Party shall:
(a)            meet with representatives  of the Recipient Party on the date set out in   the Change Notice or as soon as practicable  thereafter (but no later   than the notice  period  set  out  in  the  table  in  Section  5.6.3),  for  the purpose of discussing the Relevant Change and any changes that  may be necessary or desirable  for  the  Recipient  Party  to  make  to  its     Network,  services  or procedures in consequence of the Relevant  Changes;
(b)            provide  any additional  information  reasonably  requested  by  the Recipient Party no later than ten (10) Business Days after the  Recipient Party’s request for such additional information; and
(c)             take  reasonable  account  of concerns  raised  and  proposals  made  by              the Recipient Party to minimise any adverse impact of the Relevant  Changes on the Recipient Party and revise the Change Notice  accordingly.
5.6.5      Testing. A Notifying Party shall, bearing its own costs in doing so:
(a)            co-operate   with   a   Recipient   Party   in   relation   to   the   development   of procedures for testing the impact of the Relevant Changes on the proper operation and compatibility of the Parties’ respective Networks;
(b)            jointly carry out testing with the Recipient Party no less than 20 Business Days before the Notifying Party proposes to effect the   Relevant Changes. The testing shall be conducted in accordance with the testing procedures developed under Section 5.6.5(a).
5.6.6      Testing failure.  Subject to the Recipient Party having co-operated with the Notifying Party in relation to the conduct of tests under Section 5.6.5, if such tests:
(a)            are not accepted by 10 Business Days prior to the date when the Notifying Party proposes to effect the Relevant Changes; or
(b)            do not provide reasonable assurance of the continued proper operation and compatibility of the Parties’ respective Networks, services and procedures the Notifying Party shall postpone implementation of the Relevant Changes. The period of postponement will be the period necessary to allow the Parties to repeat the steps in Sections 5.6.3 to 5.6.5 above.
5.7           Operations And Maintenance Obligations
5.7.1      Operations & maintenance responsibility.  Each Operator shall be responsible for the operations and maintenance of its own Facilities and Services.
5.7.2      Fault reporting systems.  Each Operator shall establish and maintain a fault reporting service  that  allows  Customers  who are  directly  connected  to the  Network  of that Operator  and to whom that Operator  supplies  services  (inter alia), to report faults relating to any Network or support system.
5.7.3      Customer   notification.   Each Operator   will advise all of its directly connected Customers to report all faults to the fault reporting service described in Section 5.7.2.
5.7.4      Non-discriminatory fault reporting and identification. An Operator shall perform fault reporting and identification on a non-discriminatory basis.
5.7.5      Cross-referrals.  If a Customer reports a fault to an Operator:
(a)            when the Customer is directly connected to another Operator; or
(b)            which clearly relates to a Network or support system of another Operator that Operator shall promptly inform the other Operator of the   reported fault, or refer that Customer to the other Operator’s fault reporting service.
5.7.6      Network fault responsibility. The Operator in whose Network the fault occurs is responsible for rectifying it and restoring services.
5.7.7      Transmission service faults. The Operator that supplies transmission services is responsible for maintaining and repairing that transmission service, notwithstanding that the transmission service may be used in another Operator’s Network.
5.7.8      Major inter-working faults.  If a major fault occurs which affects a communication that crosses or is to cross both Operators’ Networks, initial responsibility for identifying the fault rests with the Operator who first becomes aware of the fault.
5.7.9      Faults affecting other Networks or Equipment. If  an  Operator  identifies  a  fault occurring  in its Network  or with its network  facilities  which  may have an adverse effect  on  the  other  Operator’s  Network,  network  facilities,  network           services  or Equipment, the first-mentioned Operator shall promptly inform the other Operator of:
(a)            the existence of the fault;
(b)            the actions being taken by the first mentioned Operator to restore   service and to further identify and rectify the fault; and
(c)             the outcome of those actions.
5.7.10  Bear own costs.   Each Operator is responsible for establishing and maintaining a fault reporting service at its own cost irrespective of the location of the fault.
5.7.11  Fault priority.  Each Operator shall give priority to faults which have:
(a)            the  highest  service  loss  impact  in  terms  of  the  number  of  Customers affected; or
(b)            those which have been reported on previous occasions and have reoccurred.
5.7.12  Fault rectification.  Each Operator shall rectify faults on a non-discriminatory basis.
5.7.13  Target times.  Each Operator shall respond to and rectify faults of a type listed in the following  table  in  accordance  with  the  relevant  response  and  rectification  time frames:

Priority Level	Fault Types (examples)	Response Time	Restoration Time
Level 1	1.  Major switch 2.  Transmission bearer total outage 3.  Route blocking > 30% 4.  Major signaling problem 5.  Major routing issues 6.  Fraudulent calls outage	Within 1 hour	4 hrs
Level 2	1.  Minor switch outage 2.  Minor routing issue 3.  Minor signaling problems 4.  Route blocking 10%-30% 5.  Cross line & silent calls	Within 4 hours	24 hours
Level 3	1.  Faults affecting single or  small number of Customers 2.  Route blocking <10%	Within 24 hrs	72 hrs
Level 4	1.  Remote Congestion 2.  External Technical Irregularities (ETI) 3.  Other performance related issues	Within 48 hrs	14 days

Explanatory Notes to Section 5.7.13:
(a)            All faults reported shall be ascribed with a “Priority Level” as set out in the above table for response and restoration purposes and the Operators involved shall cooperate with one another to achieve the given time targets based on the severity of the fault reported.
(b)            Some of the common “Fault Types” are listed as examples in the above table.
(c)             “Response  Time”  refers  to  the  time  for  the  Operator  whose  Network  or service is faulty to respond to and appropriately attend to the fault.  Response Times are to be measured from either the time the fault is notified by the other Operator or from the time when the Operator first becomes aware of the Fault, whichever is the earlier.
(d)            “Restoration Time” refers to the time taken by the Operator to restore a faulty service and is determined by the period between the reporting of a fault to the respective  IFRC/NMC  of  the  Operator  and  the  restoration  of  the  faulty service.
5.7.14  Planned maintenance. If an Operator (Maintenance Operator) intends to undertake planned                  maintenance which may affect an Access Seeker’s Network, the Maintenance Operator shall:
(a)            provide at least ten (10) Business Days notice of the planned maintenance;
(b)            use its reasonable endeavours to minimise any disruption to the carriage of communications which cross or are to cross both   Operators’ Networks, and which are caused by the maintenance or rerouting; and
(c)             where practicable and agreed by the Operators, provide alternative routing or carriage at no additional cost to the Access Seeker.
5.7.15  Planned maintenance windows.   An Operator shall undertake planned maintenance within windows of time agreed with other Operators, and where the windows of time for such planned maintenance have the least effect on end-users.
5.7.16  Emergency   maintenance. If an Operator (Maintenance Operator) needs to undertake emergency maintenance which may affect the other Operator’s Network, the Maintenance Operator shall, if it is able to:
(a)            provide at least 24 hours notice of the planned maintenance;
(b)            use its reasonable endeavours to minimise any disruption to the carriage of communications which cross or are to cross both Operator’s Networks, and which are caused by the maintenance or rerouting; and
(c)             where practicable and agreed by the Operators, provide alternative routing or carriage at no additional cost to the other Operator.
5.7.17  Hours of fault reporting and rectification.   VADS shall maintain a twenty four (24) hours a day, seven (7) days a week fault reporting and rectification service.
5.7.18  Complaints Handling.  The Operators shall report all interconnection outages that relate to Facilities and/or Services to the respective Fault Reporting Centre.
5.7.19  Routine  Testing. The  Operators  shall  conduct  interconnection  service  tests  at agreed half yearly intervals to ensure the maintenance of interconnection  services at agreed services levels in accordance with  standards as agreed   by both parties or such other standards as may be determined by the  Commission.
5.8           Technical Obligations
5.8.1      Compliance.   Operators  shall  adhere  to  the  relevant  guidelines  issued  by  the Commission  from  time  to  time  to  the  extent  that  they  have  not  been  expressly revoked or are not inconsistent with any technical obligations set out in this ARD.
5.8.2      Prevention of technical harm. An Operator shall take reasonable measures to ensure that the interconnection does not cause physical or technical harm to the other Operator’s Network.
5.8.3      Technical   Standards.   An Operator   shall comply with any applicable technical Standard adopted by the Commission under Chapter 3 of Part VII of the Act.
5.8.4      No Interference.   An Operator shall not do anything, or knowingly permit any third person  to  do  anything,  in  relation  to  a  network  facilities,  network  services or Equipment which:
(a)            causes interference; or
(b)            materially obstructs, interrupts or impedes the continuous use or   operation of, the network facilities, network services or Equipment of  another Operator.
5.8.5      Notice of interference and rectification.   If an Operator (Notifying Operator) notifies another Operator that the other Operator’s network facilities, network services or Equipment  is  causing  interference  to  the  Notifying  Operator’s  network  facilities, network services or Equipment:
(a)            the other Operator shall rectify the situation so that no interference is  caused within twenty four (24) hours of receiving notice from the  Notifying Operator; or
(b)            if the other Operator is not able to locate the source of the interference within twenty four (24) hours under Section 5.8.5(a), the other Operator shall promptly notify the Notifying Operator, and both   Operators shall meet within 24 hours of such notice and jointly examine each other’s network facilities, network services or Equipment to locate the source of the interference.

CHAPTER 6:          BILLING AND SETTLEMENT OBLIGATIONS
6.1           Invoices
VADS shall  use its best  endeavours  to issue to the Access  Seeker  an invoice  in writing within thirty (30) days of the end of the Billing Period for amounts due in respect of the supply of any of the Access Services during such Billing Period.
6.2           Currency
Unless otherwise agreed, all invoices will be stated in Ringgit Malaysia and payment shall be made by the Access Seeker in Ringgit Malaysia.
6.3           Billing Cycle
The Access Provider shall issue invoices in monthly Billing Cycles, unless otherwise agreed with the Access Seeker.
6.4           Billing Rates
The Access Seeker shall pay VADS the Charges for the relevant Access Service(s) supplied by VADS to the Access Seeker, as specified in Access Agreement.
6.5           Billing Verification Information
The Access Provider shall provide, with each invoice, such information as may be reasonably necessary for the Access Seeker to verify rates and charges contained in an invoice.
6.6           Other Billing Information
An Operator must provide to any Operator with which it interconnects, information within its possession that is reasonably necessary to allow the other Operator to provide accurate and timely billing services to itself, its affiliates or other Operators.
6.7           Summarised Invoice and Billing Information
VADS   shall  provide   the  Access   Seeker   at  the  Access   Seeker’s   request,   an aggregated  summary  of  billings  for  access  to  the  network  facilities  and  network services provided to the Access Seeker, in monthly tranches.
6.8           Billing Error
If an Operator discovers an error in an invoice, it must notify the Other Operator.  The Operator which made the error must make necessary adjustments  to correct  that error in the next invoice.
6.9           Time for Payment
(a)            An Operator must pay any amount due and owing to the Other Operator on the Due Date unless otherwise agreed in writing by both parties; and
(b)            an Operator to whom any service is provided under the Access Agreement must pay the Operator providing the service the applicable rates and charges, and on the terms and conditions set out or referred to, as the case may be, in the Access Agreement.
6.10        Method of Payment
All payments can be made by bank cheque or electronic funds transfer directly to an account nominated by VADS.
6.11        Billing Disputes
VADS  shall  allow  an  Access  Seeker  to  dispute  an  invoice  if  the  Access  Seeker notifies  VADS  within  twenty one (21)  days  after  the  date  of  receipt  of  such  invoice  and  such notification specifies the information set out in Section 6.12.

6.12        Billing Dispute Notification
VADS  may  require  an  Access  Seeker  to  provide  the  following  information  when disputing an invoice:
(a)            the reasons for which the Invoiced Party disputes the invoice;
(b)            the amount in dispute;
(c)             details  required  to  identify  the  relevant  invoice  and  charges  in  dispute including:
(i)              the account number;
(ii)            the invoice reference number;
(iii)           the invoice date;
(iv)           the invoice amount; and
(v)             billing verification amount.
6.13        Billing Dispute Resolution
The Access Provider and an Access   Seeker   must comply   with the Dispute Resolution Procedures applicable to billing disputes.
6.14        Interest
VADS may charge interest on due and unpaid amounts which is outstanding from the Access Seeker at the following rates:
(a)            one percent (1%) per annum above the Malayan Banking Berhad Base Lending Rate; or
(b)            two percent (2%) per annum above the Malayan Banking Berhad Base Lending Rate, for sums which overdue by more than sixty (60) days,
calculated daily from the due date until the date of receipt of payment in full by VADS from the Access Seeker.
6.15        Backbilling
VADS may include omitted or miscalculated charges from an earlier invoice in a later invoice  or issue  an invoice  for charges  which  have  previously  not  been  invoiced provided that VADS is able to substantiate  the charges to the Access  Seeker and such inclusion, amendment or issuance is made within three (3) months from the end of the Billing Period in which the relevant service was provided.
6.16        Provisional Billing
Where VADS is unable to issue an invoice, it may issue an invoice to an Access Seeker for a provisional amount, based on the last invoice (provisional invoice). In such circumstances,  VADS may invoice an Access Seeker for a provisional amount for a period of not more than three (3) successive Billing Period, provided the amount of the provisional invoice is no more than the average of the most recent three (3) invoices.  Where there have not been three (3) past invoices for access to the relevant network facilities or network services, the Access Provider may issue a provisional invoice up to the full value of the amount based on the most recent invoice. The provisional invoice will be adjusted in the next invoice or as soon as practicable but not later than sixty (60) days after  the  calendar  month  in  which  the  charges  were  incurred  or such  other  time period as may be agreed in writing.
6.17        Security Sum
(a)            For the purpose of clarification, the Security Sum does not relieve the Access Seeker from its obligations to pay amounts to VADS as they become due and payable, nor does it constitute a waiver of VADS’ right to suspend, disconnect, or terminate the relevant network facilities or network services due to non- payment of any sums due or payable to VADS.
(b)            VADS  shall  be  entitled  to revise  the  Security  Sum  in  any  of the  following event:-
(i)              at each subsequent anniversary from the Commencement Date;
(ii)            where, in the opinion of VADS, the Security Sum is less than the actual Minimum  Value  calculated  at  the  end  of  the  most  recent  ninety (90)  days period;
(iii)           upon the provisioning of new or additional network facilities or network services to the Access Seeker; or
(iv)           where  there  is  material  change  in  circumstances  in  relation  to  the Access Seeker's creditworthiness. For clarification, a material change in circumstances includes, but is not limited to, a failure by the Access Seeker to pay on the Due Dates at least three (3) Invoices rendered in the preceding  six (6)  months  (so  long  as  those  amounts  have  not  been disputed in good faith). If the amounts in the Invoices are disputed in good faith, this will not constitute a material change in circumstances for purposes of this Section 6.17(b)(iv).
(c)             Where the Security  Sum is revised pursuant to Section 6.17(b) above, the Access  Seeker  shall  within  five (5)  Business  Days  from  the  written  request  of VADS, deposit the new Security Sum with VADS in the manner specified in Section 4.5.
(d)            In the event VADS elects to suspend or terminate the provisioning of relevant Access Service(s) to the Access Seeker, VADS shall have the right to use the Security Sum (together with any interest thereon) to set off any outstanding sum due and payable to VADS by the Access Seeker.
(e)            Subject to Section 6.17(d) above, upon termination of the Access Agreement, the  Security  Sum  deposited  with  VADS  or parts  thereof  (if  any)  shall  be returned  and/or  refunded  to the  Access Seeker.

CHAPTER 7:          TERM, TERMINATION, SUSPENSION AND OTHER PROVISIONS
7.1           Term
The Operators  shall enter into an Access Agreement  for a term of no less than three (3) years from the execution date of the said Access Agreement.
7.2           Termination
Subject to Section 7.5, VADS may terminate an Access Agreement or part thereof if any of the circumstances referred to in Section 7.2(a), 7.2(b) or 7.4(c) below apply and VADS has notified the Access  Seeker of its intention to terminate  the Access Agreement:-
(a)            the Access Seeker has materially breached the Access Agreement and VADS has notified the Access Seeker that it will terminate the said agreement in no less than thirty (30) days if the Access Seeker does not remedy its breach by the end of that period; or
(b)            the Access Seeker is subject to a winding up order; or
(c)             a Force Majeure has continued for a period of more than ninety (90) days.
VADS  shall forward  to the  Commission  a copy  of the notice  of termination  at the same time as providing the notice of termination to the Access Seeker.
7.3           Change In Law
Where the continued operation of the Access Agreement or access to any Access Service(s)  provided  by  VADS  is  or  will  be  unlawful  (as  a  result  of  a  legislative change),  the  Access  Seeker  and  VADS  shall  meet  within  five (5)  Business  Days  of becoming  aware  of  the  relevant  change  in  law  to  review  whether  access  to  the relevant  Access  Service(s)  may  be  provided  by  VADS  on  different  terms  and conditions  (which  are  acceptable  to the  Access  Seeker).  If the  Operators  cannot agree  to  the  provision  of  access  on  different  terms  and  conditions,  VADS  may terminate the provision of access to the relevant Access Service(s).
7.4           Suspension
Subject to Section 7.5, VADS may only suspend access to any Access Service(s) in the following circumstances:
(a)            the Access Seeker is in breach of a material obligation and fails to remedy such breach within thirty (30) days (or seven (7) days for breach of payment obligations) of receiving written notice from VADS to remedy such breach;
(b)            the   Access   Seeker’s   Facilities   materially   adversely   affect   the   normal operation of VADS’ Network or are a material threat to any person’s safety;
(c)             the Access  Seeker’s  Facilities  or the supply  of Access  Service(s)  pose an imminent threat to life or property of VADS, its employees or contractors;
(d)            the Access Seeker’s Facilities  cause material physical or technical harm to any Facilities of VADS or any other person;
(e)            where  the  Access  Seeker  has  failed  to  pay  Invoices  in  accordance  with Section 6 of this ARD;
(f)              where Force Majeure applies; or
(g)             the Access Seeker breaches any laws, regulations, rules or standards which has a material adverse effect on VADS or the provision by VADS of Access Service(s) under the Access Agreement.
For  the  purposes  of  this  Section  7.4,  VADS  must  provide  the  Access  Seeker  five (5) Business  Days  notice  in  writing,  including  written  reasons,  prior  to  suspending access to any Access Service(s).
7.5           Approval
Prior  to  terminating   or  suspending   or  seeking   to  materially   vary   an  Access Agreement or access to any Access Service(s) provided under it, VADS must inform the Commission in writing of the action it proposes to take and the reasons why such action is appropriate.
VADS shall not terminate, suspend or seek to materially vary the Access Agreement or access to any Access Service(s) until such time and on such conditions, as the Commission may specify.
7.6           Undertakings
If the parties to an Access Agreement adopt the terms and conditions specified in an undertaking that has been registered with the Commission in accordance with the Act, the parties must notify the Commission within five (5) Business Days of such adoption. In  such  circumstances,  the  terms  and  conditions  of  the  Access  Agreement  will continue to be in force for the remainder of the term of that Access Agreement, even if the access undertaking is withdrawn or expires prior to the expiry of that term.
7.6           Post-termination fees
VADS shall not recover any additional charges, costs or expenses on termination or suspension of an Access Agreement or access to any Access Service(s) provided under it except:
(a)            Charges invoiced in arrears and not yet paid; or
(b)            Charges   arising   during   an   applicable   minimum   contractual   period   (as described in Section 7.1 above.
7.7           Upfront charges refund
On termination of an Access Agreement or access to any Access Service(s) provided under it, VADS shall refund to the Access Seeker all amounts paid in advance to the extent that the amount (or part of the amount calculated on a pro-rata basis) relate to the period after the date of effect of such termination.
7.8           Deposits and guarantees
Notwithstanding the obligation in Section 7.7, VADS shall:
(a)            within sixty (60) days of termination of the Access Agreement refund to the Access Seeker any deposit paid (without interest) provided all other amounts payable by the Access Seeker to VADS have been paid; and
(b)            immediately upon termination of the Access Agreement unconditionally waive any rights under any guarantees  provided by the Access  Seeker except in respect of amounts payable by the Access Seeker to VADS as at the date of termination.
7.9           Intellectual Property Rights
The Operators agree not to use any patent, trade mark, trade name, housemark, service mark, designs, copyright, database rights, know-how and any other type of intellectual property rights belonging to the Other Operator or any of its affiliates without the prior written consent of the Other Operator for purposes including but not limited to any advertising, publicity releases or sales presentations.
7.10        Interconnect Steering Group (“ISG”)
7.10.1  Establishment of the ISG
The  Operators  will  establish  a  body  to  be  known  as  the  “Interconnect  Steering Group”  or  “ISG”  which  will  be  responsible  for  coordinating  the  activities  of  the Operators,  the  operation  of  the  Access  Agreement  and  any  matter  specifically referred to the ISG under this ARD.  The ISG may establish such working groups as it thinks fit to report to it on particular issues.
7.10.2  Representation
VADS and the Access Seeker will be equally represented on the ISG and such representatives shall fully represent and shall be authorized to bind the Parties with regard to decisions made by the ISG.
7.10.3  Timing
The ISG shall be established within fourteen (14) days from the Commencement Date and thereafter shall meet within fourteen (14) days from the date of written request by either Party.
7.11        Force Majeure
7.11.1  If  a  Party  (“Affected  Party”)  is  prevented  from  performing  any  of  its  material obligations  under  this  Agreement  (but  shall  not  include  any  of  the  Customer’s payment  obligations)  by  reason  of  Force  Majeure,  it  must  immediately  notify  the other Party (“Other Party”) in writing of the circumstances  constituting the event of Force Majeure and must keep the Other Party regularly informed of the progress in resolving the event of Force Majeure and use all reasonable steps to minimize the adverse effects of the event of Force Majeure on the performance of its obligations under this Agreement.
7.11.2  If the delay in performance  or non-performance  of the Affected Party’s obligations due to the event of Force Majeure is continuous for a period of one (1) month from the date of the  Affected  Party’s  written  notification  under  Section  7.11.1,  then either  Party shall have the right to terminate this Agreement  with immediate effect and neither Party shall have any claim against the other in respect of such termination save for antecedent breaches.
7.12        Governing Law
This  ARD  shall  be  governed  by  and  interpreted  in  accordance  with  the  laws  of Malaysia.
7.13        Assignment
Neither  party  shall  be  entitled  to  assign,  transfer  or  novate  any  of  its  rights, obligations or liabilities without the prior written consent of the other party.

SCHEDULE 1: NON-DISCLOSURE AGREEMENT
MUTUAL NON DISCLOSURE AGREEMENT
THIS AGREEMENT is made on                         200

BETWEEN

VADS BERHAD (Company No. 208739-W), a company incorporated in Malaysia and having its principal place of business at 15th Floor, Plaza VADS, No. 1 Jalan Tun Mohd Fuad, Taman Tun Dr. Ismail, 60000, Kuala Lumpur (“VADS”) of the one part;

AND

(COMPANY) (Company No.XXXXX) (“Company”),  *a company incorporated in Malaysia /
*organised under the laws of name of country, having its business address at  Address.
(* Delete where inapplicable.)

WHEREAS:-
VADS  and  the  Company  are  desirous  of  evaluating  the  possibility  of  entering  into  the Proposed  Transaction  (as  defined  below)  and  for this  purpose,  the  Disclosing  Party  (as defined  below)  may  disclose  certain  Confidential  Information  (as  defined  below)  to  the Receiving Party (as defined below), subject to and upon the terms and conditions below.

NOW IT IS HEREBY agreed by the Parties as follows:
1.              DEFINITIONS
1.1           “Confidential  Information”  means any and all information of the Disclosing Party disclosed by or on behalf of the Disclosing Party in relation to or for the purpose of the Proposed Transaction, whether disclosed before or after the date hereof, whether in written or electronic format, oral or otherwise, and whether or not labeled as “Confidential”,   including,   without  limitation,  information  relating  to  its  business, financial condition, marketing strategies, know-how,             suppliers, customers, operations, pricing, technical information and any information relating to or belonging to  any  member  of  the  Group,  and  also  includes  any  documents  or  materials  in whatever form prepared by the Receiving Party and/or its Representatives using or incorporating any Confidential Information.
1.2           “Disclosing Party” means the Party disclosing the Confidential Information.
1.3           “Group”   means a Party’s shareholders, subsidiaries, affiliates, related and/or associated companies.
1.4           “Party” means either VADS or the Company and “Parties” means VADS and the Company collectively.
1.5           “Proposed Transaction” means the proposed request for Access Services by the Company from VADS pursuant to VADS’ Access Reference Document.
1.6           “Receiving Party” means the Party receiving the Confidential Information.
1.7           “Representatives”   means a Party’s employees, directors, advisors, permitted representatives or agents and those of any member of its Group.

2.              CONFIDENTIALITY OBLIGATIONS
2.1           The Receiving Party undertakes that it shall not use or copy or reproduce or part with possession  of any Confidential  Information  except to the extent necessary  for the purpose  of assessing  and  negotiating  with  the  Disclosing  Party  on the  Proposed Transaction.
2.2           The Receiving Party shall not disclose any of the Confidential Information to any person without the prior written consent of the Disclosing Party and subject to such person signing a confidentiality undertaking substantially similar to the terms of this Agreement.
2.3           The Receiving Party is permitted to disclose such Confidential Information to those of its Representatives who have a need to know the Confidential Information for the purpose of the Proposed Transaction.       Prior to disclosure of the Confidential Information to such Representatives, the Receiving Party shall ensure that such Representatives are made fully aware of the confidentiality obligations set out herein and shall procure that such Representatives comply with the same.   The Receiving Party shall be fully responsible in the event of any breach of the confidentiality obligations herein by any of its Representatives.
2.4           The Receiving Party agrees that it will take all appropriate and reasonable measures to prevent   unauthorised   disclosure   or use of   Confidential   Information,   which measures shall include the same degree of care that the Receiving Party utilises to protect its own confidential information.
2.5           The Receiving Party agrees to notify the Disclosing Party in writing of any misuse or misappropriation of Confidential Information of the Disclosing Party upon becoming aware of the same.

3.              EXCEPTIONS
3.1           The confidentiality obligations imposed herein shall not apply to information which:-
(a)            prior to the date hereof, is in the public domain or hereafter comes into the public domain other than as a result of a breach of this Agreement  by the Receiving Party and/or its Representatives;
(b)            was known to the Receiving Party without confidentiality restrictions prior to its receipt  of such information  from the Disclosing  Party, as shown  by the Receiving Party’s written records in existence at the time of disclosure;
(c)             is lawfully disclosed to the Receiving Party by a third party that is, to the best of the Receiving Party’s knowledge, legally free to disclose such information;
(d)            is independently   developed   by  the  Receiving   Party   as  shown   by  the Receiving Party’s written records ; or
(e)            is  required  to  be  disclosed  by  law  or  order  of  court  or  directive  of  any regulatory  or governmental  body  provided  that,  to the  extent  permitted  by such law, order or directive, the Receiving Party shall promptly notify the Disclosing   Party  of  such  requirement   to  disclose   and  shall  limit  such disclosure required or provide the Disclosing Party the opportunity to seek a protective or other court order in respect thereof. If the Receiving Party is still required to disclose the information, the Receiving Party shall, to the extent permitted by such law, order or directive, seek confidential treatment from the recipient for such information disclosed.

4.              RETURN OF MATERIALS
4.1           On the request of the Disclosing Party at any time, and without demand in the event the  Proposed  Transaction  has  been  aborted                   or terminated,  the  Receiving  Party shall, and shall procure its Representatives to, return all Confidential Information together with all copies or extracts of such materials or documentation, provided that the Receiving Party shall be entitled to retain 1 copy of the Confidential Information solely for corporate governance purposes and subject to the same being kept confidential.

5.              PROPRIETARY RIGHTS
5.1           All Confidential Information including any intellectual property rights thereunder shall at all times remain the sole and exclusive property of the Disclosing Party.
5.2           Nothing  in this  Agreement  is intended  to grant  any  rights  to the  Receiving  Party whatsoever  under any patent or copyright  or trademark,  nor shall this Agreement grant  the  Receiving  Party  any  property  right  or  rights  or  interest  in  or  to  the Disclosing  Party’s  Confidential  Information  except  the limited  right to review such Confidential Information solely for the purposes of determining whether to enter into the Proposed Transaction with the Disclosing Party.

6.              NO REPRESENTATION
6.1           The   Disclosing   Party   does   not   make   representation   or   warranty   as   to   the completeness and/or accuracy of the Confidential Information, unless expressly provided otherwise in a definitive agreement in respect of the Proposed Transaction, and the Receiving Party shall be fully responsible for any assumptions or conclusions derived from the Confidential Information.

7.              TERM
7.1           This Agreement shall be effective for the duration of the Proposed Transaction and shall continue to be effective:
(a)            for a period of two (2) years from the date either Party notifies the other Party of its decision not to proceed with the Proposed Transaction; or
(b)            unless superseded by confidentiality  terms in a definitive agreement entered into between the Parties in respect of the Proposed Transaction, as the case may be.

8.              REMEDIES FOR BREACH
8.1           Both Parties acknowledge that they are aware and fully understand that in the event of any breach of this Agreement by the Receiving Party and/or its Representatives, the  Disclosing  Party  could  suffer  substantial  loss  and  damage  which  monetary damages cannot adequately remedy.
8.2           The  Receiving  Party  acknowledges  that  the  Disclosing  Party  shall  be  entitled  to specific performance, injunctive and other equitable relief in enforcing the obligations in this Agreement in addition to all other remedies available in law.
8.3           The Receiving Party shall indemnify and hold the Disclosing Party harmless from and against   any  losses,  damages,   liabilities,  costs  or  expenses   (including   without limitation legal costs) which is determined by a court of final jurisdiction to be due to a breach of this Agreement by the Receiving Party and/or its Representatives. Notwithstanding  anything to the contrary herein contained,  in no event shall either Party  be  liable  to  the  other  for  any  special,  indirect,  incidental,  or  consequential damages (including, without limitation, damages for loss of business profits, business interruption,  loss of business information  or other pecuniary  loss) arising out of or relating to this agreement,  including without limitation any service schedule issued hereunder, even if advised of the possibility of such damages.

9.              LAWS AND JURISDICTION
9.1           This  Agreement  is  governed  by  and  interpreted  in  accordance  with  the  laws  of Malaysia and each Party hereby agrees to submit to the non-exclusive jurisdiction of the courts of Malaysia.

10.           NO WAIVER OR ACQUIESCENCE
10.1        No  delay  by  either  Party  in  exercising  any  right,  power  or  remedy  under  this Agreement shall operate as a waiver or acquiescence thereof nor shall it restrict or affect the Party’s right or powers under this Agreement.  No waiver of any term or condition to this Agreement shall be effective unless made in writing.

11.           AMENDMENTS
11.1        This Agreement is the entire agreement between the Parties and supersedes any and all prior or contemporaneous representations, agreements and promises, written or oral, between the Parties, regarding the subject matter of this Agreement.  Any amendments to this Agreement shall only be effective if agreed in writing and signed by both Parties.

12.           NO ASSIGNMENT AND BINDING EFFECT
12.1        Neither Party shall assign, novate or transfer this Agreement to any person without the prior written consent of the other Party.
12.2        This Agreement shall be binding on the heirs, permitted assigns and successors in title of the Parties hereto.

13.           NO OBLIGATION TO PROCURE PRODUCTS OR SERVICES
13.1        In  no  event  shall  this  Agreement  or  the  Parties’  agreement  to  enter  into  this Agreement  be construed  to mean that either Party shall procure from or shall be obliged to procure from the other Party any products or services or to enter into the Proposed Transaction or any transaction or be obliged to enter into any transaction with each other.

14.           CONSTRUCTION
14.1        While the Parties believe that the terms hereof are fair, reasonable and enforceable in all respects, it is agreed that in the event that any provision of this Agreement is found to be invalid, void or unenforceable, unless such provision materially affects the intent and purpose of this               Agreement, such invalidity, voidability or unenforceability shall not affect the validity of this Agreement nor the remaining provisions herein.

IN WITNESS WHEREOF, the Parties have caused this Agreement to be executed by their respective authorised representatives.

 

Signed by                                                                    ]
For and on behalf of                                            ]
VADS Berhad                                                            ]
In the presence of                                                ]

 

 

Signed by                                                                    ]
For and on behalf of                                            ]
Company XXX                                                          ]
In the presence of                                                ]