GENERAL TERMS AND CONDITIONS
Effective Date:01.09.2026
Version: 1.0
Provider | Datatech Consulting Limited, Vaults 13-15, Valletta Waterfront, Floriana, Malta Comp. Reg: C32602 VAT MT16898512 |
|---|
SA.1 Definitions
Term | Definition |
|---|---|
Application Software | Shall mean the software that End Users will operate. |
Approval | Shall mean a confirmation in writing by either Party to a request, which request would have an impact on this Agreement or any particular Agreement or Statement of Work. |
Business Go Live | Shall mean the hand-over of the productive environment following a Technical Go Live to the Client End User base. |
Business Process Owner | Shall mean the Client’s appointee who is the single point of contact to oversee the provision of Product/s and/or Services under a particular Agreement or Statement of Works. |
Calendar Days | Shall mean the measure of calendar days as per the Gregorian calendar. |
Change Request | Shall mean a deviation of the standard functionality as specified by the Product, Service or as requested in accordance with Clause 5 of the Agreement. |
Contractual Phases | Shall mean the agreed contractual units of an Agreement or Statement of Work where the Service Provider is obliged to deliver and where the Client is obliged to pay and typically include the following six (6) phases: (i) Prep Phase, (ii) Explore Phase, (iii) Realise Phase, (iv) Deploy Phase, (v) Technical Go Live Phase and (vi) Business Go Live Phase. |
Consultant | Shall mean the appointee of the Service Providers to execute a particular Agreement or Statement of Work. |
Customisation | Shall mean the adjustments (workflow, reports, integration, interfacing, screen and form enhancements) that are required to the software by the Client which adjustments either fit the clients need or localisation needs. |
Database Software | shall mean software that’s purpose is to store Client Data |
Deadline | Shall mean a date by which certain obligations need to be fulfilled as specified in the respective Agreement or Statement of Work |
Deploy Phase | Shall mean the transportation of the configuration in quality / test to the productive system, check and confirmation of Client readiness, and finally, move business operation from an "as-is" to a "to-be" system. |
End to End Process | Shall mean a process that takes a system or service from beginning to end and delivers a complete functional solution. |
End User | shall mean the Client’s business users |
End User Training | Shall mean training provided by Client trainers to the Client’s employees |
Executive Manager | Shall mean the single point of contact that has overall authority over the Agreement. |
Explore Phase | Shall mean a number of validation workshops in which the teams meet and go through the standard solution and process documentation and where such standard solution is not applicable, the agreement in the form of change requests of the customisations that will reduce or eliminate the gap in the standard solution. |
Feature | Shall mean a distinctive attribute of a Product |
Formatted Report | Shall mean data output to a device in a pre-formatted form. |
Function | Shall mean a single function within an end to end business process |
Implementation | Shall mean all works in this Agreement |
In Scope | Shall mean what is included in a Agreement or Statement of Work |
Industry Practice | Shall refer to the official documentation content pertaining to the Product, Model and Version |
Industry Standard | Shall refer to the official documentation content pertaining to the Product, Model and Version |
Interface | Shall mean the interface by which the Client end user interacts with the Application Software |
Key User | Shall mean the Client appointee who has specific expertise in an end-to-end process. |
Legacy Data | Shall mean data that is current in the systems being replaced |
Legacy System | Shall mean the system being replaced. |
Legal Localisation | Shall mean the adjustments required to the Product to make it legally compliant for the country it is intended to operate in and which localisations are limited and subject to the generation of legal reports. |
Localisation | Shall mean the adjustments (workflow, reports, integration, interfacing, screen and form enhancements) that are required to the software by the Client which adjustments either fit the Clients need or localisation needs other than legal reports |
Man days | Shall mean the measure of obtainable work by a number of resources in any workable day. |
Master Data | Shall mean data that is required for the configuration and also activation of Modules |
Methodology | Shall mean the method including procedures and steps to which the Parties agree to adhere to. |
Milestone | Shall mean a date where the Parties have agreed to take stope of the progress and agree on a way forward accordingly |
Migration | Shall mean the process governing data extracted, transformed and uploaded from the Legacy System to the New System |
Model | shall mean the model of a hardware product |
Module | Shall mean a group of functionalities representing an end to end business process within a business unit |
New System | Shall mean the system replacing the Legacy System |
Out of Scope | Shall mean what is not included in an Agreement or Statement of Work. |
Out of the Box / Standard Functionality/Industry Standard Functionality | Shall mean the ability of the software to provide end to end functionality for any given process as described by the developer of the software in his/her official documentation. |
Prep / Prep Phase | Shall mean an official kick off of the project and a deep dive into the scope of work, project timeline, members of the project and communication strategies, followed by a high-level plan for training and testing, technical tasks and mobilisation. |
Project | Shall mean the agreed entire scope of work, dates governing the deliverables and resources or the Parties involved in a particular Agreement or Statement of Work |
Project Freeze | Shall define an agreed move to stop all changes in the project. The Project Freeze can be planned by iterative changes or by a stipulated time following the Explore phase, which time will not surpass the given time required to complete the deploy phase. Unless otherwise agreed, the project freeze for all projects will be 22 days following the signing of the Explore Phase certificate. |
Project Manager | Shall mean the single point of contact that has the authority to oversee the provision of Product/s and/or Service/s under a particular Agreement or Statement of Works. |
Realise Phase | Shall mean to incrementally configure, extend, and test the pre-configured solution to reflect a client’s integrated business processes based on requirements defined in the Explore phase and captured in documentation. Additionally, during this phase, the project team loads Client data into the system, plans adoption activities, and prepares cutover plans and plans for operationally running the solution. |
Report /Output | Shall mean data output to a device |
Specifications | Shall mean the identification of requirements pertaining to a Product or Service |
System Software | Shall mean low level software that is required to operate the application |
System Users | Shall mean the Client technical administrators |
Task | Shall mean one or more units of work that have a scope, date and resource |
Technical Go Live | Shall mean the complete installation, configuration and operation of the hardware equipment, systems, database and application software without Client data that are included in the contract. |
Testing | Shall mean one or more types of tests agreed to be carried out to verify the quality of the Product/s and/or Service/s in any particular Agreement or Statement of Work. |
Train the Trainer | Shall mean the task of training Business Process Owners and Key Users |
Training | Shall refer to activity of delivering organised teaching by qualified and informed members of both Parties through various modes of communication. |
Transactional Data | Shall mean data that refers but not replicates business transactions originally done in the legacy once migrated in the new systems |
Transported to Production | Shall mean the process after Client approval where units of work are transferred to a productive environment |
Version | Shall mean the version of the model |
Workflow | Shall mean a group of business functions combined together that while they form an end-to-end process, they are dependent on each other and are executed by different End Users. |
SA.2 Communication & Escalation
- a. The Client shall designate a Project Manager in respect of each Agreement or Statement of Work and any communication in respect of an Agreement or Statement of Work shall be handled at first instance by the said Project Manager. The Client shall appoint, as Project Manager, a person who has the necessary experience and competence to assist with the Product/s and/or Services subject of the Agreement or Statement of Work. Any person nominated by the Client to act as Project Manager shall be subject to approval by the Service Provider. Any change in the Project Manager shall also be subject to prior approval by the Service Provider.
- b. The Project Manager shall be authorised to give instructions, directions and approvals to the Service Provider in writing including by email and for this purpose the Client warrants and represents that the Client has obtained the necessary corporate authorisations granting the Project Manager the power to bind the Client.
- c. Any change in Project Manager shall be without prejudice to any decisions, instructions or approvals already taken for granted by the previous Project Manager. Any such replacement Project Manager shall not be empowered to modify, revoke or restrict any decision, instruction or approval already granted by the previous Project Manager.
- d. The Service Provider shall appoint a Consultant in respect of each Agreement or Statement of Work who shall serve as a point of contact and representative of the Service Provider. The Consultant shall be the personal responsible to liaise with the Project Manager.
- e. In addition, each Party shall designate an Executive Manager who will have full disclosure and full knowledge of this Agreement. The Executive Manager shall receive all communications related to this Agreement and the Agreement or Statement of Work and shall be authorised to represent it in all related matters
- f. All communication between the Project Manager and the Consultant shall be copied to the Executive Manager and shall be professional and ethical. Official communications will always be done by email, and both Parties agree to acknowledge the communication as soon as possible by replying to the email.
- g. Both Parties agree that project communications (notes, process, specifications, minutes of meetings, questions and answers) that have not been answered in a useful manner will be deemed as accepted by the other Party if no substantive reply is forthcoming within 5 Business Days.
- h. Both Parties agree that contractual communications (Phase submissions, approvals, change requests, payment related) that have not been addressed will be deemed as accepted by the other Party if no substantive reply is forthcoming within 10 Business Days.
- i. Both Parties agree that in both the above cases there shall be at least one reminder sent to escalate the matter.
- j. Escalation is important in order to prioritise and mitigate future issues. Both Parties agree that either Party may escalate a matter beyond the Project Manager to the Executive Manager in the event of no reply or repetitive failures during the Project.
SA.3 Approval Process
- a. Each Agreement or Statement of Work issued under Annex 1 shall consist of six (6) Contractual Phases (as defined above or as otherwise specified in the respective Agreement or Statement of Work).
- b. Submission: On completion of a Contractual Phase, the Service Provider shall submit, for approval, all the documentation or other deliverable pertaining to that Contractual Phase. In the event that, the Service Provider is unable to submit the full documentation or other deliverable due to the Client’s failure to respond to any project communication or contractual communication, the Service Provider shall submit the partial documentation or other deliverable for approval in satisfaction of the requirement under this paragraph b.
- c. Client Approval: The Client shall submit its approval or otherwise within ten (10) Business Days from the receipt of the full or partial documentation or other deliverable in terms of the foregoing paragraph. For the avoidance of doubt, the approval by the Project Manager, in writing including by email, shall be deemed a Client approval in terms of this Agreement.
- d. Client Refusal: Where the deliverable of a Contractual Phase is
- i. exclusively documentation, the Client may refuse the documentation submitted within the above-specified time-frame only if the documentation falls short of the Industry Standard. The following shall be considered acceptable causes of failure: Documentation being unreadable; Incomplete content (except where partial documentation is allowed in accordance with paragraph b. hereof); Unclear content; and Wrong formatting.
- ii. Software configuration, the Client may refuse the software submitted for approval if the software does not perform as intended (Intended Use); does not produce the results as it is programmed to do (Syntax or System bug); is not stable (resilience and stability); does not match the process documentation.
- e. Service Provider Objection: The Service Provider shall be entitled to object to any Client refusal and request approval and immediate payment if:-
- i. The documentation is according to the agreed delivery format agreed in the Prep Phase;
- ii. The software has spelling mistakes which can be easily corrected;
- iii. The Service Provider is using a different methodology or quality platform or measure than that agreed to in this Agreement of Prep Phase;
- iv. The Service Provider replaces the members of the team who were involved in the preparation of the documentation;
- v. The software is performing as it is intended to perform. Standard Functionality, Industry standard, Out of the Box; or
- vi. The software is performing as it was configured to following a customisation by the Client.
- f. Notwithstanding the internal approval process setup by the Client Parties agree that unless a formal objection is made by any side within10 Business from the submission of the documentation or other deliverable the Contractual Phase (in respect of which approval was requested) shall be deemed approved and payment in respect thereof shall be issued without undue delay.
SA.4 Payment Terms
Unless otherwise stated in the respective Agreement or Statement of Work:-
- a. Any Products provided under Annex 2 shall be invoiced and payable as follows:-
- i. One hundred percent (100%) on order for perpetual license products; or
- ii. Annual upfront payment for subscription-based Product/s.
- b. Any Products provided to the Client under Annex 5 shall be billed and payable one hundred percent (100%) on order.
- c. Any Services provided in terms of Annex 1 with a value of less than twenty thousand Euro (€20,000) shall be invoiced and payable as follows:
- i. Deposit: a deposit of thirty percent (30%) of the respective Agreement or Statement of Work Value shall be payable prior to the Start Date;
- ii. Successful Phase Completion: The Client shall pay the remaining balance of the respective Agreement or Statement of Work Value in six (6) equal instalments. Each instalment to be paid upon successful completion of the six (6) Contractual Phases of implementation of the Agreement or Statement of Work.
- d. Any Services provided in terms of Annex 1 with a value of twenty thousand Euro (€20,000) or greater shall be invoiced and payable as follows:-
- i. Deposit: a deposit of ten percent (10%) of the Agreement or Statement of Work Value.
- ii. Monthly Payment – a monthly payment shall be due and payable each month from the Start Date until the Final Date which monthly payment shall be calculated in accordance with the following formula: Monthly Payment = (Agreement or Statement of Work Value * 50%) / Project Duration).
- iii. Successful Phase Completion: Upon successful completion of each of the six (6) Contractual Phases of the implementation of the Agreement or Statement of Work, the Client shall pay a sum to be calculated in accordance with the following formula: Successful Phase Completion = (Agreement or Statement of Work Value * 30%) / 6.
- iv. Commissioning – the remaining balance of the Agreement or Statement of Work Value shall be due and payable on the End Date in addition to any other payments which may fall due on the same day. The payment shall be calculated in accordance with the following formula: Commissioning = Agreement or Statement of Work Value * 10%.
- e. Any Change Authorisation shall be invoiced and payable fifty percent (50%) upon signature of the Change Authorisation and the remaining fifty percent (50%) on delivery.
- f. Any other expenses incurred by the Service Provider to provide the Product/s and/or Service/s to the Client which expenses are agreed to but which are not included in the Agreement or Statement of Work Value shall be billed and payable at the end of each month.
- g. The Service Provider will provide the Client with one invoice for each service covered per month. The invoice will include
- i. The Client Number
- ii. The Master Agreement Number
- iii. The Agreement or Statement of Work Number
- iv. The Date of Invoice
- v. The Description of the service being invoiced
- vi. The Value Excluding Taxes
- vii. Taxes if any
- viii. Final Value
SA.5 Standard – Industry – Out of the Box
- a. Both Parties agree that the software and Products to be implemented support the legal localisation of the countries the software is intended to operate in.
- b. The Client hereby agrees that processes exercised and used internally are by no means Industry Standard or Out of the Box Functionality and therefore cannot claim such. Moreso, the Service Provider cannot be made to implement functionality in the software if the provider purchased further licenses during the project, unless agreed so in the scope of work.
SA.6 Service Levels
- a. Service Level Agreement: These GTCs outline the Service Level Agreement (“SLA”) between the Parties in respect of the provision of Service/s and/or Product/s in terms of any Agreement or Statement of Work. In particular, this Section SA.6 and SA.7 outline the performance parameters and quality of service to be provided by the Service Provider to the Client.
- b. Service Level Delivery: All support services will be provided 24hours, 7days, 365days a year. Scheduled maintenance will take into consideration the Client location and work calendar. The Service/s within this Agreement will be delivered by the Service Provider operations offices and by Service Provider staff.
- c. Response Times:
- i. In the event that a problem occurs in the Service Provider Data Centre and such problem is detected by the Service Provider or reported by the Client, the Service Provider shall use its best endeavours to repair and restore the affected Core Service within the following Response Times:
Trigger Event | Response Time* | Target Time to Repair |
|---|---|---|
CRITICAL EVENT: Any failure of Core Service causing loss of power to the Company's rack e.g.: Failure of UPS, climate control failure, security breach - actions of intruder | IMMEDIATE response from time of Event being notified by Company/ detected by the Service Provider, and assigned a Trouble Ticket number. | Within 1 hour |
NON-CRITICAL EVENT: Core Service affected but not critical e.g.: failure of N+l technology, failure of CAT5 CAT6 cable, access control failure | IMMEDIATE response from time of event being notified by Company or detected by the Service Provider and assigned a Trouble Ticket number. | Within 4 hours |
* Please note that these Response Times do not apply to any Events that have been caused by any act or omission on the part of the Company, its employees, agents, subcontractors, or caused by Company's Equipment or any Force Majeure event.
- ii. in the event of service incident management tickets, a response time will be maintained as follows
Incident | Response SLA | Update / Escalation | Resolution / Changeover | Calendar | Typical Usage |
|---|---|---|---|---|---|
Level 1 | 4 hours | 3 days | 5 days | 24 by 7 | User improvement, inefficient or uncomfortable incident. |
Level 2 | 2 hours | 3 days | 4 days | 24 by 7 | User, process issue |
Level 3 | 2 hours | 2 days | 2 days | 24 by 7 | Compartmentalized issues across the organisation |
Level 4 | 30 minutes | 1 hour | 4 hours | 24 by 7 | Express, substantial issues across the organisation |
Level 5 | 30 minutes | 30 minutes | 4 hours | 24 by 7 | VIP, DRP |
Note: If a final resolution is considered “far reach” and subsequently the Service Provider is able to provide an interim resolution, then that interim solution is taken as the final resolution[1].
- iii. Each incident will be managed through the following service model
- iv. For every ticket opened by the Client, the Service Provider will provide an estimate (Response SLA + Identification of Problem).
- d. Limitations: Hours will be calculated on man hours and not service or ticket hours. When a ticket is opened by the Client and such is considered a project by the Service Provider team, the ticket will be removed from the support queue and placed in the project queue. For clarification purposes, maintenance works will not be organised as a Project.
- e. Every ticket will be supported with a Job Specification. The job specification will be provided by the Service Provider. The job specification needs to be approved by the Client in order to progress.
- f. Closing a ticket: A consultant will flag a ticket for closure upon completion of his works.
- g. The Client shall have five (5) calendar days (excluding weekend and Public Holidays) to provide feedback. A ticket that has no feedback is considered successfully closed the hours of support charged accordingly.
- h. All Client responses will be handled within the SLA of the incident level. For the sake of clarity: Client Opens Ticket <Counting SLA TIME> Consultant Updates Ticket as Acknowledged < Counting Identification of Problem> Consultant provides Estimate <TIME STOPS> Client Provides PO <TIME Counts from DATE and TIME of RECEIPT in Email> Consultant provides JOB Specification <TIME STOPS> Client Signs Job Specification<TIME COUNTS>Consultant Flags Job Finished <TIME STOPS, 3DAYS COUNT>
1.Client Responds <TIME COUNTS>
2.Client does not respond <Service Provider invoice>
SA.7 Security & Data Protection
- a. Perimeter & System Access:
- i. Physical Access to Data Centre. The data Centre is operated and maintained to ISO 27001 quality standard. Access to the data centre is limited and managed. All correspondence should be primarily addressed to Datacentre@datatech.com.mt.
- ii. Access to systems. The Service Provider assigns specialists depending on the equipment and system in this agreement. All staff are trained in the quality standard ISO9001 and ISO27001. Service provider employees and associates are covered by indemnity agreement and data protection clause.
- iii. Access to Application is provided by the Service Provider or his authorized representative. All staff are trained in the quality standard ISO9001 and ISO27001. Service provider employees and associates are covered by indemnity agreement and data protection clause.
- iv. The Client, or its representative/s will not have access to the system unless a prior written approval is provided by the Service Provider. Access to the system whether physical or virtual will only be provided upon verification of any request. All requests for Access will be treated individually and will be supported by a verification process, which may include verbal or written supporting documentation form authorized Client officials.
- b. Systems Security – Systems and Applications: The Service Provider will install, implement, configure and maintain all systems according to manufacturing installation and operation recommendations. The systems will be reviewed from time to time to make sure that security recommendations, flaws in design, setup and configuration are mitigated.
- c. Password Management: The Service Provider and the Client will agree and implement a password management policy. Admin or Service Passwords of the systems will be managed by the Service Provider alone and deposited at its legal representative for the duration of the Contract.
- d. Bulk Data Transfer: The Client may ask for a bulk transfer of data from time to time. The Client will make this request in writing. This request is subject to authorization. As per our ISO27001 standards no data can be physically transferred and therefore the Service Provider will place the bulk data in an accessible place for the Client to transfer electronically. The transfer of the data will be encrypted. Upon first access to the bulk data repository, the Company will automatically assume full responsibility for that data.
- e. Operational Event Logging: The Service Provider aims to immediately detect any problems or faults in any of the Core Services listed above. The Service Provider will notify the Client immediately of any of the following events that may have affected the Core Services being provided to the Client:
- i. Disasters/Calamities (explosions, fire, flood, accidents etc)
- ii. Theft and burglary
- iii. Power failures
- iv. Cooling failures
- v. System Performance
- vi. System Storage
Any faults will be notified to the Client and will be logged by Service Provider. Any faults or problems detected by the Client must be immediately reported by the Client (and in any event within 24 hours) to the Service Provider Network Operations Centre ("NOC") using the telephone number provided to the Client by Service Provider. The fault or problem will then be logged by the NOC and the Company will receive a Trouble Ticket number. This ticket number will form the basis of all follow-up actions as specified in this SLA.
- f. Operational Incident Management: In the case of incidents, the Service Provider will invoke a Disaster Recovery and Business Continuity plan according to the incident impact. A business continuity will be equally measurable to the incident impact. The Service Provider will provide the Client with a full investigation report of the incident. Depending on the impact of the incident, the Service Provider may also engage 3rd party independent suppliers to support in the incident investigation. An Incident will be reported as follows:-
- i. Date Of Incident
- ii. Date Of Incident discovery
- iii. Description of Incident
- iv. Root Cause of Incident
- v. Counter Measures Taken to Mitigate Incident
- vi. Long Term measure to eliminate or reduce Incident recurrence
The Service Provider will endeavour to complete all investigation of an incident within 3 months of the incident.
- g. Maintenance & Upkeep: The Service Provider carries out most of its maintenance on Friday from 2100 to 0500. During this time, systems will be taken offline.
- h. Service Incident Management: The Service Provider operates an incident management system. You may reach us on:
- i. Visits & Auditing:
- i. Client Access to the Data Centre: The Service Provider operates a strict only 1 Client at any time visit. Furthermore, the Service Provider will provide access to any legal authority operating in Malta that has provided a valid authorisation to enter the data centre. The Service Provider will only recognise the validity of such a request through verification by its legal department. If the Service Provider cannot verify that a request to visit the Data Centre is genuine or legitimate, the Service Provider will require to validate the request through its Legal Department.
- ii. Client Access to the Data Centre for Auditing purposes: Client shall have the right to visit the data centre and to carryout annual audits of the Data Centre operations pertaining their information security management systems. The Client is not permitted to take photos of the data centre or any equipment within. Only the Service Provider personnel are authorised to take photos. The Client may make arrangements for such photos to be taken and then transferred by contacting the Service Provider authorized personnel. The Client will make arrangements at least 2 working days before the audit takes place. This is done to make sure that no other Client is present in the Data centre during the audit.
- iii. Client Access to the Data Centre for operation purposes: Client access to the data centre is restricted to Clients who have co Located equipment. The Client may appoint up to 2 people that are authorised to visit and enter the data Centre. Client who have IAAS or SAAS solutions shall not be given physical access to the Data Centre.
- j. Premises
The Client shall, at its own cost and expense, make available office space within the country where the Products and/or Services are to be provided which office space shall be sufficient to accommodate at least four (4) members of the Service Provider’s personnel and which shall be fully furnished, functional and equipped with all necessary amenities and services including, in particular, a reliable and fast internet connection and printing facilities.
Datatech® and its Logo are protected by copyright