AI	Artificial Intelligence
CFCU	Central Finance and Contracts Unit
CE	Conformitè Europëenne
CNA	Converged Network Adapter
CoC	Court of Cassation
CoE	Council of Europe
CoS	Council of State
CSA	Canadian Standards Association
DIMM	Dual In-line Memory Module, RDIMM-Registered, LRDIMM-Load Reduced
ECC	Error Checking and Correction
ECLI	European Case Law Identifier
ECtHR	European Court of Human Rights
EN	European Standard
EU	European Union
FC HBA	Fibre Channel Host Bus Adapter
FCC	Federal Communications Commission
GB, TB	Gigabytes, Terabyte, Gbps- Giga bit per second
GUI	Graphical User Interface
HDD	Hard Disk Drive
HTML	Hyper Text Mark-up Language
HW	Hardware
Hz, GHz	Hertz, Giga Hertz
IEEE	Institute of Electrical and Electronical Engineers
IPMI	Intelligent Platform Management Interface
ISO	International Organisation for Standardization
IT	Information Technologies
PCIe	Peripheral Component Interconnect Express
RAID	Redundant Array of Inexpensive Disks
SAS	Serial Attached Small Computer System Interface
SATA	Serial AT Bus Attachment
SQL	Structured Query Language
TCC	Turkish Constitutional Court
UYAP	Ulusal Yargı Ağı Bilişim Sistemi (Turkish National Judiciary Network)
YİM	Yargıtay İçtihat Merkezi (CoC Documentation Centre)

1. SCOPE OF THE WORK

Within the scope of the EU-CoE Joint Project, ‘Strengthening the Institutional Capacity of Court of Cassation’, the Contractor shall achieve the following results for the establishment of case law database for the Court of Cassation:

Result-1: A case law database and related software modules are developed.

Result-2: Hardware and sustainability components are supplied.

The following sections describe the terms of reference for the contract.

2. ASSUMPTIONS AND RISKS

2.1. ASSUMPTIONS UNDERLYING THE PROJECT

Beneficiary;

· Has got a great experience, gathered over decades, on evaluation, classification and publication of case laws.

· Has already appointed a Classification Board for this purpose.

· Has already been operating a database of approximately six million CoC decisions on UYAP system, open to the public access.

· Has already employed competent and enough number of technical experts to manage existing IT infrastructure.

· Has already employed competent and enough number of technical experts to develop and maintain Java based software with relational databases.

· Will actively involve software development activities of this Project.

· Will provide rooms, permissions and infrastructure during the Project implementation.

2.2. RISKS

As of today the following risks are identified;

· Insufficient allocation of appropriate level of human and financial resources required for the successful implementation of the project and its outputs.

· Insufficient involvement, cooperation and participation of all the stakeholders.

· Lack of intra and inter-organisation coordination and communication.

The Contractor shall prepare a Risk Management Plan as a part of the Project Management Plan defined in Article 4.1 of this document, in order to mitigate those risks, and to identify and manage further risks during the implementation period.

3. LOGISTICS AND TIMING

3.1. LOCATION

The base of operation for the Project is Ankara/Turkey. The Contractor may use its own premises for backstopping purposes, and during software design and coding activities, provided that associated Beneficiary project experts can actively attend and contribute.

3.2. START DATE AND PERIOD OF IMPLEMENTATION

Project will start as of the contract signature date (T0), and period of implementation will be 12 months from this date. Due dates of the individual deliverables are given in Article 6 of this document.

4. WORK STREAMS

4.1. ORGANIZATION AND METHODOLOGY

The Contractor shall prepare a Project Management Plan explaining its methodology, organisation, timeline, procedures, standards and other measures to achieve the results of the project, and submit to the Contracting Authority after the contract signature.

Recommended project organisation is presented in the following diagram;

In order to ensure sustainability, participation of Beneficiary experts to the project team is essential. Therefore, the Beneficiary shall assign no less than a deputy project manager, a field expert and a programmer, as well as a test team of two experts, of which one of them is the field-expert assigned to the analysis team, and appropriate number of test operators. Beside contributing to the process and ensuring sustainability, this will be a good on-the-job training opportunity for the Beneficiary experts, regarding contemporary development tools and techniques.

4.2. WORK STREAM: SOFTWARE DEVELOPMENT

The Contractor shall design and develop a Case Law Database and related software with coordination and actively involvement of the Beneficiary, as specified in Article 5.1 of this document, and deliver both executable codes and recompilable source codes to the Beneficiary.

Software development phases, and corresponding document deliveries are depicted in the following diagram;

Abovementioned documents shall comply IEEE 12207 requirements, and are subject to the approval of the Beneficiary, in order to finalise a phase and start the next one or to perform acceptance.

1. Software Development Plan: (to be prepared as a part of the Project Management Plan, which is mentioned in Article 4.1 of this document) team organisation, timeline, team members, communication procedures, deliveries, technologies to be employed, international standards to be respected.

2. Software Requirements Specification: detailed list of requirements, collected by means of interviews and document overview, and agreed validation/verification method for each requirement.

3. Software Design Description: definition of all software components and software units (screens, reports, database tables, interfaces), meeting the abovementioned requirements, including a bi‑directional traceability matrix between requirements and software units.

4. Software Test Procedures: prepared by the test team, test steps and sample data to validate/verify each software requirement, including a bi‑directional traceability matrix between requirements and test steps. (This document contains pilot test procedures as well.)

5. Software Test Report: results of all tests, including pilot tests, successful or failed.

4.3. WORK STREAM: SUPPLY OF HARDWARE AND SUSTAINABILITY COMPONENTS

The Contractor shall;

· Supply, install and put into operation the hardware specified in the Article 5.2 of this document,

· Provide necessary licenses, trainings and warranty/maintenance specified in the Article 5.3 of this document, in order to achieve a sustainable system.

Overview of the prospected IT infrastructure of YİM is depicted in the following picture;

(Mobile or Desktop Users) Firewall

Where;

· Document repository will be the library, where the both original and anonymised versions of the case laws are stored.

· Search engine will be responsible for indexing and retrieving the documents. Search engine will be the only interface to access the repository.

· Case Law Database, the catalogue of documents in the repository, will hold all information about the documents. Most of the search criteria will be examined on this index in order to speed up the inquiry responses.

· Application server will provide different types of users with appropriate interfaces to accept the inquiries and to deliver the search results in return.

5. REQUIREMENTS

5.1. SOFTWARE REQUIREMENTS

5.1.1 The Contractor shall perform a Software Requirements Analysis to be coordinated by the Beneficiary Deputy Project Manager and determine required components and modules of a Case Law Database and related software. YİM shall include at least the following main functionalities;

· Case Law Publication: identification as case law, classification/keyword extraction, anonymization, association to other legal documents/law articles,

· Case Law Inquiry: With different criteria, including text and keyword,

· Case Law Print/Download,

· Subscription: different user profiles and preferences,

· Notification: “deferred document request”, where users submit their requests and are notified later, when the document is available.

Therefore, YİM shall;

5.1.2 Allow selection of case law, including decisions of chambers, general assemblies and even decisions of boards of presidents and the Judicial Ethics Advisory Committee, if needed,

5.1.3 Determine the importance of a judgment in line with its precedential nature,

5.1.4 Identify keywords,

5.1.5 Build a notification system to inform requesting users about the requested case law,

5.1.6 Ensure ease of access to judgments according to time frames of incident, proceedings, or crime,

5.1.7 Identify relevant articles of laws (if there are any references to international conventions or any related usage, identify these as well),

5.1.8 Create a case identifier whose numbers will be given by the Beneficiary (the European Case Law Identifier (ECLI)).

5.1.9 Identify and develop classification criteria (based on reversals, approvals, judgments submitted by appellate courts, judgments submitted by first instance courts, judgment of a chamber, decision of a general assembly, old legislation-new legislation, acceptance of the case, abatement of the case, etc.),

5.1.10 Delete or modify personal data and set up an infrastructure of legislation on this matter,

5.1.11 Create folders of precedents in accordance with their expertise for judges and provide them with sample judgments, up-to-date information notes, summaries of judgments, notes on the details of cases and summaries,

5.1.12 Produce bulletins of monthly case law summaries, through an appropriate user interface for the authorized people, who will make data entry.

5.1.13 Provide judges in Classification Board with appropriate user interface in adding content to the database by writing abstracts of the selected decisions.

5.1.14 Provide interfaces for the authorized users of the companies processing case law, offering an option for retrieving documents in batches,

5.1.15 Include both manual and automatic anonymization, concept/keyword extraction and correlation tools that will enable more efficient searches. During anonymization, person and organization names can be replaced with pseudo names.

5.1.16 Allow the following single or combined search criteria to be applied during inquiries on the decisions;

· Free Text (word groups, included/not included, complex search with AND/OR/NOT)

· Originating body (court chambers, sections, general assembly of chambers/unification, Grand General Assembly etc.)

· Significance level (most recent, first-in-the-row, relevant, convenient decisions will take higher scores)

· Date Interval

· Instance Court

· Decision type (reversal, approval, etc.)

· Keywords

· Law Articles

· Decision date (before, after, between)

· Document Type (predefined types)

· Case Title

· Conclusion

· Decision Number

· Separate Opinion(s) (yes/no)

· Referenced Strasbourg/Domestic Law/International Law Articles

· Referenced Procedural Rules of the Court

· ECLI or similar Case Number

5.1.17 Allow text search over the different sections of a document (Procedure, Complaints, Separate Opinions, etc.), using a thesaurus to extend the range of the search,

5.1.18 List the case laws queried and allow the result list to be printed or sorted, in increasing or decreasing order, on different columns.

5.1.19 Allow users to click on any document on the list to select, display, download and print the document, accompanying/explanatory documents and press release, if available, as well as guide users to access related TCC, CoS, and ECtHR documents.

5.1.20 Provide a subscription mechanism, which allows YİM to serve users in different profiles by granting different data access privileges, retrieve opinions, complaints, satisfaction level, demands, preferences, search tendency of the users, personalize the services, guess document needs based on the previous inquiries, and send notifications to meet “upcoming content” requests.

5.1.21 Allow Classification Board, chamber members, rapporteur judges, data entrance operators and public prosecutors of CoC to access original documents and additional information, whereas the other users, including lawyers, academics and citizens, can view only the anonymized version of the decisions.

5.1.22 Allow authorised users to record thematic notes that only judges of the Court of Cassation are allowed to see, in order to avoid case law inconsistency and conflicting decisions on the cases. (A feature only for the Classification Board users, who make data entry.)

5.1.23 Provide links to User Manuals, and on-screen immediate help (tip) options for guidance,

5.1.24 Support both personal computers (through internet browsers) and mobile devices (through mobile application) over the internet in Turkish user interface. Features to be included in the mobile application, which should run natively on minimum Android 7.1 and iOS 13 operating systems, will be determined during the design phase.

In addition;

5.1.25 At the end of the analysis study, the Contractor shall prepare a Software Requirements Specification document, in English or Turkish, in the course of IEEE 12207 requirements, and submit to the Beneficiary for joint review. The document shall be revised by the Contractor according to the comments and inputs given during the review, and subject to the approval of the Beneficiary. If in English, final version of the document shall be translated to Turkish.

5.1.26 During the Design and Implementation phase, the Contractor shall prepare a Software Design Description document, in English or Turkish, in the course of IEEE 12207 requirements, and submit to the Beneficiary for joint review. Initial version of the document shall contain the architectural/preliminary design of the software to be jointly reviewed before commencing the programming activities. The second version of the document shall contain the finalised detailed design of the software, and be jointly reviewed before the installation of the software. The document shall be revised by the Contractor according to the comments and inputs given during the final review, and subject to the approval of the Beneficiary. If in English, final version of the document shall be translated to Turkish.

5.1.27 During the Design and Implementation phase, the Contractor shall support Beneficiary Test Team to prepare Software Test Procedures document, in the course of IEEE 12207 requirements, which will be the basis of the acceptance of the developed software, and utilise those procedures during its internal tests as well.

5.1.28 By taking the advantage of the size and the know-how of the Java community in Turkey, it is recommended to utilise Java technologies for YİM software development. In addition, JavaScript/HTML based frameworks, such as React/Angular for front-end and Node.js for server-side components are also promising. However, Contractor is recommended to implement AI components in Python language.

5.1.29 The Contractor shall utilise PostgreSQL free and open source relational database. However, as the need emerges for storing and accessing contents in different formats, such as multi-media files, the Contractor is recommended to utilise NoSQL databases, such as MongoDB for the document repository and content management features of YİM.

5.1.30 Software Testing Phase will include pilot testing, which is to be performed in-house by the Beneficiary experts under the supervision and support from the Contractor, based on the agreed test procedures, and by utilising an automated test tool, which is supplied by the Contractor and capable of storing, executing and monitoring test scenarios. The Contractor shall correct the errors and revise the documents, if necessary, after each failing test.

5.1.31 Test system shall be independent from the live system.

5.1.32 The Contractor shall submit the report of successful penetration tests performed by a third-party body, before the acceptance.

5.1.33 Beneficiary’s technical experts shall involve actively in the whole development process in order to ensure sustainability. The Contractor shall provide necessary development environment and tools at its own and/or Beneficiary’s premises, based on the selected teamwork methodology.

5.1.34 Capacity of the Beneficiary in Contemporary Software Development Technologies is to be enhanced through the trainings specified in Article 5.3.2 of this document.

5.1.35 End-user trainings, including those for Classification Board users, as well as User Manuals are to be provided in digital and traditional means.

5.1.36 After installation of the software, before commencing the pilot tests, the Contractor shall deliver executable codes and recompilable source codes to the Beneficiary, in electronic format. After pilot testing, revised version of the codes shall also be delivered.

5.1.37 Regarding the software developed in the scope of this section, the Contractor shall provide regular software patches and bug fixes, as well as remote or on-site consulting/support during the warranty period, defined in Article 5.3.3.1 of this document.

5.1.38 As a distinctive feature of YİM, implementation of AI technologies and algorithms, including Named Entity Recognition with Deep Learning is required for the following functionalities of YİM;

· Concept extraction and categorization

Based on the initial “training” of the selected AI algorithm by means of selected documents from The Journal of Court of Cassation on Court Judgments, candidate contents are categorised automatically and concepts/keywords are identified. Classification Board’s responsibility in this process is to determine candidate documents to be sent to YİM, and review and approve AI based classification. Eventually AI may take over these responsibilities as well.

· Links to the law articles and other related documents

AI algorithms will be trained to identify law articles in the subject documents and to establish links to the related documents. This can be performed during both the classification and query optimisation stages.

· Extraction and anonymization of private/personal data

Classified and approved documents are further processed to identify and replace or remove private/personal data. In this scope, person and company/organisation names are in the first line. Those names are replaced by random pseudo names from a pre-defined list.

· Query building and optimisation

AI algorithms will be employed in assisting users for query building, and thus speeding up the access to the documents of interest. Previous searches, areas of interest, trend topics, and connection between documents are some of the inputs for query optimisation.

· Feedbacks and smart statistics

Users generally hesitate submitting feedbacks, complaints, satisfaction or comments during online transactions/inquiries. These can easily be recognized by AI algorithms after a proper deep learning process. Inquiry success or failure rates and reasons, personal preferences, common blunders, trend topics, case law access frequencies, connection between documents are just a few examples of input that can be used as a basis for such a behaviour analysis. Together with the explicit user comments, the results of that evaluation can assist Sustainability Committee of the Beneficiary in the course of optimising YİM.

· Quality control for data and process

AI algorithms can regularly check data consistency and process performance, and prepare automatic reports for the Management, IT Managers, and Sustainability Committee of the Beneficiary.

Deep learning algorithms can be employed on already classified documents in The Journal of the Court of Cassation on Court Judgments and annual reports. In addition, senior judges’ support is very valuable.

In principle, YİM is expected to deliver uttermost use of AI -content, not only as a data mining instrument, in all possible components. The following diagram summarises the recommended utilisation of AI;

5.2. HARDWARE REQUIREMENTS

5.2.1 The Tenderer shall supply two server computers for a fault-tolerant operation, each one with the following specifications;

· Two Rack Unit size, Rack-Mount

· Minimum dual 900W, redundant (1+1), fault-tolerant, hot-plug power supply, with backup fan support

· Integrated graphics card with minimum 8MB memory

· Supports 64 bit architecture processors

· Minimum two new generation processors, each one having at least 20 cores, 40 threads, with 27.5MB L3 cache memory, minimum 2.1 GHz clock speed

· Support ECC and memory mirroring or Mirrored Channel Mode

· 24 DDR4 DIMM slots, and support RDIMM, LRDIMM memory types

· Total memory size expandable to 1.5TB

· 768 GB, minimum 2933 MHz RDIMM memory, in minimum 64 GB modules

· Supports hot-swappable eight 2.5 inch SAS, SATA HDD

· Two 240 GB SATA interface M2 driver with HW RAID for installing operating system

· In addition to the keyboard, mouse, monitor and serial communication ports, minimum two USB 3.0 ports

· Minimum seven PCIe 3.0 ports

· Minimum two on-board 10GBaseT Ethernet ports, configured to backup each other when needed

· Server architecture to support 1/10/25/40 Gbps Ethernet adapters and 8/16/32 Gbps FC HBA cards.

· Minimum two dual-port 10/25Gbps CNA

· Minimum two dual-port 16Gbps FC HBA

· Supports Suse/Red Hat Linux, Windows Server 2016/2019 operating systems

· Virtualisation by using VMware vSphere 7 Enterprise Plus (by means of extending Beneficiary’s existing licence, corresponding to the proposed servers)

· Integrated IPMI 2.0 compatible management tool to monitor and manage hardware components status, CPU, RAM utilisation, and perform firmware updates, with visual (GUI) and command-line support;

o Allows operating system independent, remote access to the system console

o Allows use of keyboard and mouse

o Allows integrated management of other rack/blade type servers of the same brand

o Single tool for the different parameters/components of the server

5.2.2 All the equipment and machinery shall be provided complete with the necessary accessories and/or parts such as to ensure that the unit (required item) is capable of operating to the required technical and quality specifications. All specifications and details listed within the tender for each item are the minimum requirements and any higher specification cannot be incompatible with primary performance. Any improvements on the specifications or additional features offered should be clearly identified in the Tenderer’s offer.

5.2.3 The type of the supplied current in Turkey is 220 V (mono-phase) and 380 V (tree-phase + neutral). The quality and stability of the supplied current may undergo fluctuations of ±10 %. All hardware must operate on 220 V ± 20 V, 50 Hz ± 0.5 Hz (unless otherwise explicitly stated) power supply and be suitable for direct connection to the standard power outlets in Turkey. The type of electrical outlets generally installed in Turkey is the type with 2 (two) side mounted earthling poles (Euro Plug). Electrical plugs of equipment should be compliant with the standards of use in Turkey and fit exactly. The supplier will evaluate the supplied current, the quality of the current and the fluctuations of the current and take the necessary precautions to avoid damages to the equipment.

5.2.4 All supplies must be suitable for operation in the climatic conditions in place of delivery, Ankara, Turkey. All hardware units must be operable in an office environment with regards to at least the following conditions:

· Operating temperature : Between 10°C and 35°C

· Relative Humidity: Between 20 % and 80 %.

5.2.5 System components and whole system must be compatible with each other. Any interoperability problems between software and hardware, if applicable, must be resolved by the Contractor at no additional cost to the Contracting Authority.

5.2.6 An operating manual detailing the normal operation of the equipment, actions to be taken in abnormal situations and basic routine maintenance must be provided with each item of equipment. The hardware and software manuals shall be supplied in English and in Turkish (if commercially available) as electronic copy.

5.2.7 The supplier will be responsible for advising of any Health & Safety risks associated with equipment provided and of suitable protective measures.

5.2.8 In the specifications offered, the tender must clearly state the manufacturers name and the Country of origin for each items tendered.

5.2.9 The Tenderer shall be aware that supply, delivery, installation, integration and final customization must include all needed parts and accessories required for the supplies to be presented for acceptance fully installed, operational and ready for use. The Tenderer shall be aware that accessories, parts and documentations used during delivery, installation, integration and customization before acceptance must therefore be anticipated and included in the offered price.

5.2.10 The Tenderer is aware that it shall be the sole responsibility of the Contractor to ensure that all pre-requisites for the completeness of the supply delivery are met before its commencement.

5.2.11 The supply, delivery, installation, commissioning, putting into operation, inspection, testing, training and warranty services must be completed on time in accordance with the Project Management Plan prepared by the Contractor according with Article 4.1 of this document.

5.2.12 All system software delivered (such as operating system and database management system software) must be licensed to the beneficiary that will allow trained personnel of the beneficiary to perform software installation, update/upgrade, repair/debug and/or diagnosis/report activities without supplier assistance in the future.

5.2.13 The Tenderer must be aware that:

· The contractor must provide the necessary measures to prevent any damage during delivery, installation, integration and customization stages. If any damage occurs during delivery, installation, integration and customization stages, it must be appropriately rectified by the Tenderer.

· The contractor must keep the work site(s) clean and safe against any hazard (e.g. fire, etc.) during delivery, installation, integration and customization stages.

· All items supplied, including hardware and software, must be fully operational.

5.2.14 The Tenderer shall provide a proof (certificate or confirmation by the manufacturer) that it or its Subcontractor is approved/authorized distributor of the equipment in question.

5.2.15 Regarding the system software items the Contractor shall provide regular software patches and bug fixes during the warranty period, defined in Article 5.3.3.1 of this document.

5.2.16 Items must conform to relevant applicable technical and safety regulations, such as UL, CSA, FCC or EN, and quality standards including any ISO, CE marking, other domestic or relevant regulations and standards that are applicable to each specific item.

5.2.17 Installation must be performed by contractor or authorized service provider. All the equipment must include all necessary parts (rail kit, cable management arm, mounting kit, etc.), and standards for its installation.

5.2.18 Storage subsystem shall be provided by the Beneficiary. Contractor and Beneficiary shall collaborate during configuration and storage allocation to servers.

5.2.19 High availability configuration for all applicable components must be provided by the Contractor.

5.2.20 The Contractor shall perform all necessary tests to ensure the operational readiness of the installed equipment, together with the Beneficiary, in order to deliver them in full functionality.

5.2.21 Installation and put into operation shall be conducted by authorized personnel of the Contractor or its Subcontractor.

5.2.22 All devices must be installed to rack cabinets, which will be provided by the Beneficiary.

5.2.23 The Supplier shall transport, unload, unpack, assemble, install, start-up, and configure the equipment, and also install the necessary data and electrical cabling in order to deliver the equipment in fully operational condition.

5.2.24 Delivery address for the equipment is the premises of the Beneficiary in Ankara, Turkey.

5.2.25 The Beneficiary shall guarantee the Supplier’s free entrance to the buildings and relevant room(s) during the installation works. All equipment and software should be installed by the Contractor in coordination with the staff of the Beneficiary.

5.2.26 The obligatory documents for the acceptance:

· Original certificate of origin

· Report of Final test in the factory (quality control certificate), where applicable,

· Documents evidencing the applicable certificates/standards

· Warranty document of the manufacturer and/or the supplier,

· Supplier must show that the equipment has authorised service in Turkey,

No acceptance can be pronounced without the presence of the complete set of documents.

5.3. SUSTAINABILITY REQUIREMENTS

In accordance with the overall objective of the Project, that is “Strengthening the Institutional Capacity of the Court of Cassation”, the ultimate goal of this tender is not only to outsource the development of a Case Law Database, but to enable Beneficiary as well, to take over the maintenance responsibility and implement further improvements on the system, through;

· Appropriate number of licenses for all proprietary software, development and test tools and algorithms, in order the Beneficiary to be able to execute, redesign, recompile, maintain, modify, manage and test the Case Law Database and software to be developed by the Contractor.

· Trainings, in order to improve the capacity of the Beneficiary on the tools and techniques employed during the development of the Case Law Database and related software.

· Warranty and maintenance packages of the vendors, including Contractor itself, for all the software/hardware components, in order to provide continuous service and integrity of the Case Law Database.

5.3.1. LICENSES

5.3.1.1 Contractor shall provide appropriate number of licenses, based on the proposed hardware configuration, of all proposed proprietary software, such as operating systems, enterprise editions of the database managements systems, VMware vSphere 7 Enterprise Plus virtualisation software, system management and monitoring tools, etc., in order an unlimited number of public users over internet to access the Case Law Database.

5.3.1.2 Contractor shall provide appropriate number of licenses of the same tools of software development, automated testing and configuration control, including the frameworks, libraries and AI/deep learning algorithms, for a Beneficiary team of at least two developers, in order the Beneficiary to be able to execute, redesign, recompile, maintain, modify, manage and test the Case Law Database and software to be developed by the Contractor.

5.3.1.3 Regarding the software items in the scope of this section, the Contractor shall provide regular software patches and bug fixes, as well as vendor or third party support packages during the warranty period, defined in Article 5.3.3.1 of this document.

5.3.2. TRAININGS

5.3.2.1 Contractor shall provide the following trainings in order the Beneficiary to conduct further improvement and maintenance activities;

No	Content of the Training	No. of Trainees	Estimated Duration
1	System Installation, Configuration and Management (On-the-job Training during the installation of the proposed hardware components)	3-5	-
2	Network and Information Security	3-5	24 hours
3	PostgreSQL Database Management	7-10	24 hours
4	Named Entity Recognition with Deep Learning (On the job training for the development team members assigned by the Beneficiary, with the selected AI algorithms and libraries for the Case Law Database)	2-5	-
5	Content Management	7-10	18 hours
6	Python Programming Language in Artificial Intelligence Applications (With the selected Python suit and libraries for the Case Law Database and software development)	7-10	18 hours
7	Agile Software Development with DevOps	3-5	12 hours
8	Software Development Tools (On the job training for the development team members assigned by the Beneficiary, with the selected tool, front-/back-end frameworks and libraries for the Case Law Database software development)	2-5	-
9	Scenario Based Automated Software Testing (On the job training for the test team members assigned by the Beneficiary, with the selected test suit and techniques for the Case Law Database and software development)	2-5	-
10	Configuration Management Basics (On the job training for the development team members assigned by the Beneficiary, with the selected configuration management tool)	2-5	-
11	Virtualisation	2-5	18 hours
12	End User Training (Classes of 15 trainees) (Please refer to Article 5.3.2.4)	75-100 (Total # of trainees)	3 hours (Each class)

5.3.2.2 Before the commencement of any training, Contractor shall prepare a Training Plan, in English or Turkish, including the schedule, to be reviewed and approved by the Beneficiary. Training Plan will be implemented after the approval.

5.3.2.3 Training Plan shall include the name, CV and proof of competence for each instructor.

5.3.2.4 Contractor shall determine the curriculum, actual number of trainees and actual duration of the trainings in coordination with the Beneficiary. Different end user training curriculum shall be implemented for the Classification Board participants in order to cover their main responsibilities, such as case law selection, categorisation and publishing, in addition to case law inquiry.

5.3.2.5 In principle, class-trainings will be performed on maximum six hours per day basis, at the premises of the Beneficiary, where the Beneficiary shall provide appropriate training rooms. On-the-job trainings, remote or face to face, will be as a part of the implementation.

5.3.2.6 If any class-training will be performed out of the premises of the Beneficiary, all costs related to trainings (transportation costs of the trainer and/or participants, participation fees (if applicable), fees of the vendor trainers and/or accommodation of participants and/or instructors (if applicable) shall be paid by the Contractor.

5.3.2.7 In any case, all training materials shall be provided by the Contractor as hard and soft copy, and handed out for every trainee. The language of the training documents shall be in Turkish or English; if not, interpretation/translation shall be provided and paid by the Contractor. End user trainings and associated material shall be in Turkish.

5.3.2.8 At the end of each training, Contractor shall issue a certificate of participation for each attendant.

5.3.2.9 At the end of each training, Contractor shall distribute a questionnaire to the attendants, about the success of the training, and submit the results to the Beneficiary.

5.3.3. WARRANTY AND MAINTENANCE

5.3.3.1 Warranty period for the hardware and system software components is 2 years from the date of acceptance. Tenderer must provide a detailed description of the organisation of the proposed service.

5.3.3.2 The Contractor must warrant that all items delivered shall be free of defects in materials and workmanship for 2 (two) years of warranty period after acceptance and that in case of reported item malfunction would repair or replace the product at no charge.

5.3.3.3 Warranty for all items in this tender must be on “collect and return” basis, i.e. if an item cannot be repaired on site, the Contractor should organize the transport from the beneﬁciary’s premises to the Contractors/manufacturers authorized service location at its own expense, repair/replace it and return it back to the Beneﬁciary.

5.3.3.4 The technical offer shall include information of how the warranty will be provided including name of the service organization, contact person(s), postal address, telephone and facsimile number and e-mail address.

5.3.3.5 The Contractor shall guarantee the proper operation of the supplies. In the event of failure of the supplies' operability during the warranty period, the Contractor shall restore it, and in case of impossibility to do so, shall replace it with equivalent supplies in terms of the technical characteristics. The replacement shall be performed by the Contractor at its own expense.

5.3.3.6 All repairs and maintenance conducted under the warranty period must be undertaken by service personnel authorised by the relevant manufacturer for these tasks.

5.3.3.7 If any component of the system which is necessary for running of the whole system turns out to be defective during the warranty period, the Contractor is obliged to troubleshoot the problem and/or replace this component with another one possessing the same technical characteristics and quality not later than 24 hours following the receipt of the notification (sent by the Beneficiary) of the Contractor about the failure of the equipment and/or software, at its own expense.

5.3.3.8 If any component of the system turns out to be defective during the warranty period, the Contractor shall respond and intervene the problem within 4 (four) hours after the Contractor takes the receipt of the notification (sent by the Beneficiary), and fully repair and re-integrate within maximum 20 (twenty) working days. If the reparation of broken equipment/part is not possible, Contractor shall replace that equipment/part with another new, unused equipment/part (same equipment with the equipment replaced). Corresponding functional item must be provided until malfunctioning equipment is replaced within 20 days after the Contractor takes the receipt of the notification sent by the Beneficiary, at Contractor’s own expense.

5.3.3.9 The Contractor shall provide the Beneficiary with the telephone numbers and/or online service links of the authorised services, which are active 7 x 24 basis for notification about the failures and reclamations within 20 days after the commencement of the contract. (To ensure the prompt elimination of the potential defects, certificates shall be provided to demonstrate availability of the service centres in Turkey for all the supplied equipment.)

5.3.3.10 Implementation of a basic back-up scenario must be provided by the Contractor.

6. LIST OF DELIVERABLES

Below table lists the project deliverables, approval requirements and due dates, where T0 is the contract signature date;

No	Delivery	Due Date	Review & Approval
1	Project Management Plan	T0 + 2 weeks	1 week
2	Software Requirements Specification	T0 + 10 weeks	2 weeks
3	Software Design Description (final version)	T0 + 8 months	2 weeks
4	Servers (installed and configured) with all manuals and complementary documentation.	T0 + 8 months	1 week
5	Basic Backup Scenario	T0 + 8 months	-
6	Software Source/Executable Codes and Development Tools	T0 + 9 months	-
7	Training Plan	T0 + 2 months	1 week
8	Training Material	According to the training plan
9	Trainings	According to the training plan
10	User Manuals	Before the end user trainings
11	Software Test Procedures	T0 + 8 months	2 weeks
12	Penetration Test Report	T0 + 12 months
13	Revised Source/Executable Codes and Documents	T0 + 12 months	-
14	Monthly Progress Report	5^th working day of the next month	-
15	Meeting Minutes	1 week after each meeting

7. PUBLICITY AND VISIBILITY

The Contracting Authority will provide Contractor with the guidelines concerning publicity and visibility requirements of the Project, after the contract signature.

The Tenderer shall be aware that neither those requirements nor the guidance will bring additional costs to the Contractor.