Objective of the Agreement

 

First Party:

Second party: Alkhutut Al-Mithalia Computer Systems (iLines)

1.      This document outlines the agreement between the first party and the second party on the agreed-upon services, constituting an acceptable service to the first party.

2.      This agreement covers the system application services as required by the first party, which have been studied between the two parties to apply the Odoo Enterprise 17 system as per the recorded Gap Analysis.

3.      The first party commits to covering the agreed-upon costs according to the payment policies agreed upon by both parties.

 Responsible Parties

 Project Manager (Second Party)

1.      Responsible for implementing and developing the system to meet the first party's requirements.

2.      Responsible for leading training sessions.  the main point of contact from the second party.

3.      Organizes steering committees, tracks deficiencies, and provides solutions and reports on the project's status.

 Single Point of Contact (SPoC) - First Party

-        The sole responsible person for the first party, responsible for internal coordination with stakeholders within the first party.

 First Party Commitments

1.      The first party commits to providing the data required by the second party for each application as directed by the second party.

2.      Appointing a person to act as a unified point of contact during the project's implementation.

3.      Committing to payments according to the agreed policy.

4.      Committing not to employ any staff from the second party for at least 36 calendar months.

5.      Committing not to fully or partially share, develop, copy, sell, resell, or redevelop any of the second party's products and developments with any other party under any circumstances, and acknowledges that access to the second party's source code is exclusive to the second party.

 Second Party Commitments

1.      Delivering and completing the project according to the scope of work detailed in the attachment.

2.      Training users.

3.      Appointing a project manager to act as a unified point of contact during the project's implementation.

4.      Providing a summary report on the work progress at the end of each phase upon the first party's request.

5.      Training a member of the first party to perform system control, operation, management, and quick system processing.

6.      Identifying the necessary templates for data transfer operations with the first party.

7.      Submitting the project plan within seven business days after the agreement is signed by the first party.

8.      Conducting a clear analysis of the first party's requirements.

9.      The second party, whose details are registered as the second party, is fully responsible for executing the project, with no involvement of the first party with any other entities.

10.   Protecting the confidentiality of client information and documentation.

Scope of Works Terms

1.      The second party is a software development company specializing in Enterprise Resource Planning (ERP) systems and does not offer web design services or visual identity applications on any of its products. Such requests are handled by a third party chosen by the client or by the second party at an additional cost, separate from the contract cost, and only after agreement by both parties. The second party reserves the right to decline such requests altogether.

 

2.      Additional developments are carried out based on the understanding between the second party and the client during the project execution or after the project launch, if agreed upon by both parties. It is always the client’s responsibility to test the requested development and ensure its efficiency. The second party’s responsibility ends when the development is deployed in the live environment (Production or Master). The client is responsible for testing the development in a test environment and providing feedback to the second party. If no feedback is given within 3 days of the deployment, the development is considered fully accepted.

 

3.      If any technical error is discovered in the software or developments deployed to the (Production or Master) environment by the second party, the client must submit a technical error correction request. Such requests are only accepted if there is a valid maintenance contract between the two parties, and if the request relates to paid developments for which the client has already paid. No requests will be accepted if the maintenance contract has expired or if the request is related to unpaid or free developments. The second party has the right to review and reclassify the request as appropriate, without bearing any responsibility for its consequences or delays in resolution.

 

4.      The master data must be provided in Excel format only, matching the templates sent by the second party to the client. The client is not permitted to modify any part of these templates without formal written approval or email consent from the project manager on the second party’s side.

 

5.      If the master data contains dates, they must be in the Gregorian calendar. If there is a need to upload Hijri dates, this must be coordinated with and approved by the project manager. Dates for a specific category (e.g., employee birth dates) must be uniform (all in the Gregorian calendar or all in the Hijri calendar), and mixing the two in one place is not allowed without the project manager's approval.

 

6.      The client is not permitted to send data in any format other than Excel. Any file containing data intended for system import that is not in Excel format will be completely ignored.

 

7.      Uploading any images or attachments to the system is solely the responsibility of the client.

 

8.      Data migration is limited to opening balances or master data only. Any migration of detailed transactions must be explicitly stated in the agreement, specifying the nature of the data and the number of transactions in detail. Any request for data uploads outside the agreement must be approved by the second party and is subject to a separate cost from the contract cost.

 

9.      Any required document, regardless of its type, must be explicitly mentioned in the signed agreement between the two parties. The client is not permitted to request any additional document unless later agreed upon, and the second party has the right to accept or decline this request. The second party also reserves the right to apply additional fees for working on these documents.

Signature

1.      This agreement constitutes the complete understanding between the parties, replacing any prior agreements or correspondences on the same subject. Both parties have designated the provided address as the chosen address for all communications, notices, and notifications. All correspondences can be sent via email, fax, or any other means. If either party changes its address, it must give written notice of the new address; otherwise, all correspondences and notifications will remain effective at the old address.

2.      This agreement is executed in two copies, each party retaining one for reference.

3.      Both parties have signed it, acknowledging their consent and understanding after thorough review, disclaiming any claims of ignorance.