1.
Delivery requirements
NetDesign must provide its services in accordance with the agreed time frame/project plan. The project plan, including the plan for delivery and implementation, is to be specified in connection with initial project startup meeting. Unless another written agreement is in place, the customer’s company- and user subscriptions will be delivered and billed no later than 3 months from the date when the contract was signed. This time frame does not apply if there is a binding or notice of termination with the ceding operator company, and in such cases, commissioning and subscription start-up will be 14 days from the time the customer is free from binding with the previous supplier.
Required resources and data
It is expected that the customer will provide the necessary resources for the project and that the customer agrees to provide the necessary information 


The Customer's Internal Network
It is the customer's responsibility that the LAN cabling in the customer's internal private network meets the technical requirements necessary for the delivery of the solutions. The quality of the internal meetings experience in the customer's private internal network depends on the equipment used, including routers, switches and cabling. Further information on technical requirements for internal network and equipment can be found in the technical prerequisite document.
Project meeting
NetDesigns project management will prepare a phased project plan that will clearly outline what will happen when and who is responsible for each task.
Frozen Zone
Once data collection is in place and the customer and NetDesign’s project managers agree on the solution setup, the project moves to the Frozen Zone phase. The customer has thus accepted the setup, and NetDesign can start configuring and programming the solution. The date of the transition to the Frozen Zone is found at the same time as the GoLive date and is binding for being able to deliver the solution to the agreed date.
Ongoing implementation
If the customer already has an existing solution, the solution will be implemented in parallel with the use of this existing solution - with the possible use of a pilot for selected users or departments. In this case, the entire solution will first be commissioned when the solution is implemented, tested and passed. If the pilot is regarded as successful by both parties and any adjustments are completed, the actual roll-out will begin. The specific installation dates are agreed with the customer's project manager at a project meeting. The customer's project manager undertakes to ensure that the right conditions for the solution are met at the locations, see the General Terms and Conditions. 

The Customer's participation

The customer is obliged to actively contribute to the Supplier's performance of this agreement, including by providing information, making staff available to provide offices and other facilities available to participate in the acquisition test/acceptance tests and carry out operational tests.

This involvement by the customer shall not cause the customer significantly increased costs. The Supplier shall immediately give written notice to the customer, if the custoemr is not participating as agreed.
Access to the customer's environment
As long as NetDesign provides integration with the customer's Microsoft Teams solution, the customer must ensure that NetDesign has partner access to the customer's Microsoft Cloud solution and maintains the service accounts required to run the solution. NetDesign cannot offer opt-out of the required accesses, as the solution will not work without. Details of what is required are given in the technical prerequisites for implementation.
Works done in customer's Microsoft Cloud environment
NetDesign reserves the right to make changes to the provided Microsoft Teams meetings solution going forward. This may have an impact on the required APIs and data access to Microsoft Cloud (Office 365 / Microsoft 365) solution. The access is used in relation to NetDesign CVI integration, statistics data and other third-party integrations. Please note that these changes cannot be planned or predicted at any time due to the way Microsoft develops their Cloud products
Limitation of Liability
NetDesign cannot directly make changes or be held responsible for any changes that are provided in the cloud solution provided by Microsoft. It is only possible to provide Cloud Video Interop as an extra product that integrates into Microsoft Teams. It is the responsibility of the customer to keep opdated of changes through the updates in the Administrator Portal and the roadmaps provided by Microsoft.


Breakdown in the Microsoft cloud solution is beyond NetDesign's area of responsibility. Any loss and dispute caused by Microsoft's cloud solution must be attributed to Microsoft and the guidelines described in Microsoft's terms of service. NetDesign is solely responsible for the CVI integration, and NetDesign will rectify errors and omissions on this part of the solution in accordance with applicable rules.

Testing
Testing of the solution takes place initially with a preliminary internal pretest, followed by a subsequent acceptance test and an operational test. After a test is passed, the customer shall give its written approval to the Supplier without undue delay. No review, comment or approval by the customer of any test can be taken to reflect a change in the requirements that may be imposed under this Agreement. 
Internal pretest
Prior to the delivery and testing in the operating environment, preliminary internal testing is carried out in the Supplier's/the customer's environment as previously mentioned. This is intended to ensure optimum conditions prior to the acceptance test.

Acceptance test

The purpose of the acceptance test is primarily to determine whether the agreed functionality is in place. The acceptance test is conducted by the Supplier with the customer's active participation. 
If the customer approves the acceptance test with any found deficiencies, these must be entered in a list of deficiencies. The customer is only required to approve the operational test "in accordance with section Operational test" when such deficiencies are essentially remediated.

Operational test
The purpose of the operational test is to determine whether the delivery functions in the operating environment is working with respect to the solution description. The operational test is conducted by the customer with assistance from NetDesign. The operational test shall be commenced by the customer within 5 calendar days after the acceptance date, otherwise the operational test is no longer valid. The work shall be deemed to be delivered to the customer when the operational test has been approved. If the customer fails to convene an acceptance test as specified above, the work is deemed to be delivered at the latest time when a duly announced acceptance test might have occurred.  
Final delivery approval

Corrections that have been made in an ongoing manner in the operating period after the delivery took place, see the deficiency list, shall be corrected when the final delivery approval document is signed by the customer. After this there can no longer be made any adjustments, modifications or similar situation before the installation and delivery of the solution.
During this period, both parties should also be able to, and have a duty to, test the system, and upon the discovery of deficiencies notify these to the other party without undue delay. Faults, deficiencies or ad-justments that could or should have been discovered and notified within this time period may not subse-quently be the subject of a complaint to the Supplier.
This should be seen in relation to the general duty to investigate which is required of the customer by the Sales of Goods Act. 14 days to 1 month, which is the typical fault correction period for the Supplier, must be regarded as a reasonable period to allow for an agreement and resolution of the nature and character as described in the concluded agreement/offer.  Complaints made after this period where there still exists a deficiency list with items that should or could have been discovered will not be covered by the Supplier's warranty period, and will therefore be invoiced at the Supplier's then-current hourly rate (per started hour).
Standard support, remediations, etc., are either covered under the then applicable service agreement or are invoiced at the then-current hourly rate (per started hour)

2.
Purchase of hardware
The customer has 12 months warranty on all goods purchased from NetDesign from the day the customer receives the item. The customer must notify NetDesign within a reasonable time after receipt of the goods, if the customer finds errors or defects in the goods received.

If the item is damaged as a result of self-inflicted errors such as liquid damage or physical overload, this is not covered by the right of complaint. In these cases, the customer will receive an offer to repair the item for payment upon submission of the item for repair.