PROCUREMENT CONTRACT
31.03.2025 nr 2-2/25/144
Estonian Centre for Defence Investments (registry code 70009764, address Järve 34a, 11314 Tallinn,
Estonia), represented by Tiaana Kalda, Head of the Procurement Department (hereinafter the Buyer) on
the one side
and
VAS "Elektroniskie sakari" (registry code 40003021907, Eksporta iela 5 Riga, LV-1010, Latvia),
represented by Laila Līduma, Member of the Management Board (hereinafter the Seller), Buyer and Seller
may also be referred to individually as Party or together as Parties,
concluded a procurement contract (hereinafter the Contract) based on the dynamic procurement system
“Küberturvalisuse, andmeturbe ja kõrgkäideldavuse lahendused, sh riist- ja tarkvara soetamine,
koolitused, konsultatsioonid jm” (reference number 255269) and the quotation submitted in the restricted
procedure “Monitooringu tarkvara litsentsid” (reference number 288047) with respect to the following:
1. SUBJECT AND PRICE OF THE CONTRACT
1.1. The object of this contract is the Radio signal Automatic Detection software for the existing
monitoring system (hereinafter the Goods) as stated in the Seller’s quotation (Annex 1).
1.2. The total price of the Contract is 50 000 euros, excluding VAT.
1.3. The Contract shall enter into force upon signature by the Buyer and shall remain valid until
all contractual obligations are fulfilled.
1.4. The Contract is prepared in English and signed in two original copies, both having equal legal
force. Each Party shall retain one copy.
2. DELIVERY, PACKING AND PAYMENT
2.1. The Goods shall be delivered within 30 calendar days from the date the Contract enters into
force.
2.2. The packaging and marking of the Goods must comply with the requirements set forth in
Annex 2.
2.3. Delivery instructions shall follow the General Terms, Section 6 (Annex 2).
2.4. The contact person for contractual matters is Karin Piiri (e-mail
[email protected],
phone +372 5367 1029).
2.5. The contact person for customs clearance is Jaak Vaabel (e-mail
[email protected],
phone +372 717 2058).
2.6. The invoice shall be submitted in PDF format to
[email protected] and must include the
information specified in the General Terms, Section 7 (Annex 2).
3. ANNEXES
3.1. Annex 1. Seller’s quotation;
3.2. Annex 2. General Terms and Conditions of the Contract;
3.3. Annex 3. Technical specification;
3.4. Annex 4. Security requirements.
4. CONTACT INFORMATION OF THE PARTIES
The Buyer: The Seller:
(signed digitally) (signed digitally)
Tiaana Kalda Laila Līduma
Head of the Procurement Department
2/2
Annex 3
31.03.2025 lepingu
nr 2-2/25/144 juurde
PURPOSE OF PROCUREMENT: The purpose of the procurement is to acquire Radio signal Automatic Detection software for the existing monitoring system to improve the
situational awareness in radio spectrum and to enhance radio monitoring capabilities. To fulfil the objectives the software must have the required functionality and work
together with the existing Rohde & Schwarz Receivers as follows:
EB200, EM200, PR200, PR100, EM550, UMS400 and DDF255.
License quantity 2;
License type perpetual;
All licences are registered for Estonian Defence Forces;
Licences include technical support (warranty) and software updates for two years;
After the end of the warranty period, extending software support is possible.
Software user training on-site for 3 persons is included in price;
Description of the software: The radio signal automatic detection software can control the receivers of existing frequency monitoring network. The monitoring tasks are
entered into the software (the frequency ranges and the parameters) and the measurement cycles are automatically performed according to tasks. The results are stored on
the central server or on local computer as needed. As a result of the procurement, both server software and control software will be procured. Crucial capability of the
software is automatic signal detection to automate the daily work.
Requirements for the software:
No Feature Parameters
1. Purpose Automatic Detection of Radiofrequency Signals
2. Language Estonian or English
1/3
3. Functionality: Automatic The software must be able to distinguish the radio
detection of signals signal from the noise in at least three ways:
a) According to the shape of the signals – The
software must contain samples from well-
known signals.
b) Using the mask method – a signal drawn by
user.
c) Using the machine learning method – a
signal found by the user is used as a
teaching input.
5. Functionality: Automatic At least the following information is recorded
detection of signals about automatically detected signals: a)
Frequency (ITU SM.377-4).
b) Signal bandwidth (ITU SM.443-5).
c) Signal strength (dBµV, dBm).
d) Signal to noise ratio (SNR).
e) Correlation with the compared sample.
6. Functionality: Automatic The system can compare detected signals with EFIS
detection of signals allocations (European Frequency Information
System).
7. Functionality: Demodulation, audio recording and playback of
Demodulation of signals known signals must be possible.
8. Functionality: Data storage The collection of information on the detected
signals is done either on a local computer or on a
central server, as needed.
9. Functionality: Data storage The database of the central server must contain
historical information about measurement results
and be able to visualize it both statistically and as
spectral images through queries.
2/3
10. Functionality: Automation The software must enable the automation and
of measurements scheduling of measurements based on pre-filled
tasks.
11. Compatibility Runs on Windows 10 and 11 operating system.
12. Compatibility Compatible with Rohde & Schwarz Receivers as
follows:
EB200, EM200, PR200, PR100, EM550,
UMS400, DDF255
13. Compatibility Must be able to control a minimum of six (6)
receivers simultaneously, including direction finders.
14. Visualization The geographical location information must be
visualized in the map view.
15. Visualization It must be possible to visualize the spectral shape of
detected radio from data storage.
15. Visualization Must support the waterfall spectrum display format.
16. User rights There must be means that access to the system is
only for authorized users.
3/3
Annex 2
31.03.2025 lepingu
nr 2-2/25/144 juurde
GENERAL TERMS AND CONDITIONS OF THE CONTRACT
1. Basis and subject of the contract
1.1. The procurement contract has been awarded based on the documents of the dynamic
purchasing system „ Küberturvalisuse, andmeturbe ja kõrgkäideldavuse lahendused, sh riist-
ja tarkvara soetamine, koolitused, konsultatsioonid jm “ (reference number 255269) and the
tender submitted by the seller in the related procurement.
1.2. The Estonian Centre of Defense Investments (hereinafter: buyer) has awarded the
procurement contract with the seller based on the seller’s tender, the seller’s statements
and confirmations and assuming in good faith the seller’s professionalism and ability to
properly perform the procurement contract. If subcontactors are used, the seller remains
responsible to the buyer for the proper performance of the procurement contract.
1.3. The seller declares and confirms that:
1.3.1. the seller and the sellers representative have all the rights and authorizations to
enter into the procurement contract;
1.3.2. the seller has examined the procurement contract and related procurement
documents and fully understands the content and consequences of its obligations
and agrees with the conditions set out therein;
1.3.3. the performance of the procurement contract doesn’t harm the rights of third
parties and there are no circumstances that would exclude seller’s rights to enter
into the procurement contract and perform it properly;
1.3.4. the seller has the valid permits, registrations, representation rights and certificates
necessary for the performance of the pr contract and undertakes to extend/renew
them upon their expiry during the period of validity of the procurement contract.
If the extension of the permits, registrations, rights of representation and
certificates is not possible due to circumstances beyond the seller’s control, the
seller is obliged to inform the buyer immediately;
1.3.5. the seller confirms that there are no third-party claims or other rights, which third
parties may be able to enforce in relation to the goods to be delivered to the buyer;
1.3.6. the goods are not subject of international sanctions and don’t originate from a
region under international sanctions within the meaning of the International
Sanctions Act.
1.4. The subject of the procurement contract involves goods and/or services described in the
technical description of the related procurement.
1.5. Based on the general terms of the procurement contract (hereinafter: general terms) and
conditions set out in the procurement contract, the seller undertakes to sell the goods and/or
provide the service to the buyer, and the buyer undertakes to accept the goods or service
and pay to seller the purchase price for the goods and/or service in money. If the goods are
purchased with a life-cycle supporting service or other service, the terms of the service
contracts set out in the Estonian Law of Obligations Act apply to the service to the extent not
regulated in the procurement documents.
1.6. The type or specification of the goods, the quantity, the content of the service, the places of
delivery and the delivery times are set out in the related procurement and/or purchase order
and/or procurement contract(s).
1.7. The goods/services must comply with the conditions of the related procurement, the
invitation to tender and the tender submitted by the seller. The goods/services to be
transferred must meet the conditions, including in terms of quality, type, description and
1/9
quantity. The documents and packaging accompanying the goods/services must also meet
the conditions.
2. Parts of the procurement contract
2.1. Purchasing orders which involve a financial commitment are also considered as procurement
contracts.
2.2. The integral parts of the procurement contract are the invitation to tender, the seller's tender
and its annexes, explanations given during the public procurement procedure, confirmation
letters, notices forwarded between the parties, general terms and conditions and any
modifications to the procurement contract to be awarded.
3. Buyer’s rights and obligations
3.1. The buyer has the right to verify the performace of obligations arising from the procurement
contract and the documents related to the purchase of goods/services.
3.2. The buyer has the right to verify the correctness and accuracy of the invoices, calculations,
and other expenses submitted by the seller. If necessary, the buyer is entitled to request
invoices of subcontractors.
3.3. The buyer has the right to consult with the seller on matters related to the goods/services,
such as the delivery and use of the goods.
3.4. The buyer is obligated to pay for the goods/services received without defects.
4. Seller’s rights and obligations
4.1. The seller is obligated upon the buyer's demand to submit a consolidated statement for
goods and services purchased (including the date of conclusion of procurement contract or
purchase order, the name of the goods, quantity and the value of goods/services (excluding
VAT), the total value of procurement contracts/purchase orders (excluding VAT), etc.) in MS
Excel format or in another format agreed with the buyer, within 10 days after receiving the
request, unless the parties have agreed otherwise.
4.2. The seller is obligated to provide information (quantity and purpose) about subcontractors
upon the buyer’s demand. If the seller has provided such information before awarding the
procurement contract, any subsequent changes in the mentioned individuals must be pre-
approved by the buyer.
4.3. The seller is obligated to inform the buyer of any circumstances preventing the performance
of the procurement contract.
4.4. The seller is obligated to immediately inform the buyer of any cyberattack or cyber incident
against the seller and to provide the buyer with a cyber incident report upon the buyer’s
request.
4.5. The seller is obligated to comply with the terms of fair trade when executing the procurement
contract, to be based on environmentally sustainable principles, and not to use slave and
child labor.
4.6. The seller is obligated to conclude an insurance contract if the parties have agreed on this in
the procurement contract.
4.7. The seller has the right to receive necessary information from the buyer for the performance
of the procurement contract.
5. Packaging and marking of goods
5.1. The seller is obligated to provide the goods with packaging, which ensures the unchanged
condition of the goods during transport and storage.
5.2. The packaging and marking of the goods must comply with the requirements provided by the
buyer’s related procurement.
2/9
6. Delivery and acceptance of goods/service
6.1. The acceptance time for goods/services is generally from Monday to Thursday, between 8:30
and 15:00, excluding national and public holidays, as well as the immediately preceding
working days before these holidays and the last three working days of each month, unless
otherwise specified in the procurement contract to be awarded.
6.2. The seller sends a delivery notice to the buyer about the delivery of the goods or the provision
of the service before the planned delivery at least 5 working days in advance, to the e-mail
address specified in the procurement contract (a copy should be sent to the e-mail address
[email protected]), unless the parties agree otherwise in the procurement contract/purchase
order. To be added to the delivery notice:
6.2.1. name of the goods/services;
6.2.2. procurement contract (purchase order) number;
6.2.3. public procurement reference number 255269;
6.2.4. quantity to be delivered, including number of pallets, containers, etc.;
6.2.5. dimensions of the logistic unit;
6.2.6. method of packaging (film, net, Euro pallet, etc.);
6.2.7. mode of transportation, which is used for delivery (van, lorry etc.), and quantity;
6.2.8. specific requirements or needs for unloading the shipment;
6.2.9. scheduled delivery date and time;
6.2.10. delivery address of destination.
6.3. The seller delivers the goods/provides the service to the buyer and the buyer accepts the
goods/service on agreed terms.
6.4. The seller provides the delivery note together with the delivery notice or at the latest at the
moment of transfering the goods/providing the service. The delivery note must include:
6.4.1. details of the seller;
6.4.2. details of the buyer;
6.4.3. procurement contract (purchase order) number;
6.4.4. public procurement reference number 255269;
6.4.5. product/service name, product code, and quantity.
6.5. In addition to the delivery note, the seller obligates to hand over all documents necessary for
the receipt, possession, use and disposal of the goods/service to the buyer.
6.6. The buyer prepares an act of delivery and receipt, which is signed by both parties and
forwarded to the seller.
6.7. In the event of absence of a delivery note, the buyer has the right to take possession of the
corresponding goods, but the act of delivery and receipt is considered to be performed upon
receiving a correct delivery note.
6.8. More detailed and, if necessary, different conditions for the delivery and receipt of the
goods/service are provided in the related procurement.
7. Payment terms
7.1. The costs arising from the delivery and transport of the goods/service remain at the seller’s
expense until the delivery of the goods/service. The seller is also responsible for any expenses
and charges associated with the goods/service until the delivery, except for costs caused by
the buyer, unless otherwise agreed in the procurement contract.
7.2. The seller issues the invoice in an e-invoice (in machine-readable XML format). If a seller,
registered outside the Republic of Estonia is unable to provide an e-invoice for technical
reasons, they issue a PDF-format invoice to the email address specified in the procurement
contract, unless otherwise agreed in the procurement contract. The seller issues an invoice
with the following information:
3/9
7.2.1. The payer's details are set out in the procurement contract:
Estonian Defence Forces, Juhkentali 58, 15007 Tallinn, Estonia,
registry code 70008641
Other details to be included in the invoice:
contact person’s name (specified in the procurement contract) Karin Piiri;
related procurement reference number 288047;
procurement contract (purchase order) number OTE-0490307;
name and quantity of product/service.
7.2.2. Seller’s bank details:
seller’s bank: AS "Citadele banka" (JSC)
IBAN: LV14PARX0000231601015
SWIFT Code: PARXLV22
7.3. The buyer pays for the accepted and eligible goods/services to the billing account set out in
the invoice within 28 days of receiving an invoice that complies with the terms. The invoice
submission is based on the act of delivery and receipt and delivery note signed by parties,
unless otherwise set out in the procurement contract.
7.4. The buyer will not accept an invoice which does not comply with the terms and conditions of
the contract. In this case, the seller will submit a new invoice within 7 days.
7.5. Before paying the invoice, the value of which is 10 000.00 EUR or more (inclusive of VAT), the
buyer checks for absence of tax arrears via the Estonian Tax and Customs Board website. In
the event of tax arrear of 10 000.00 EUR or more, the buyer informs the Estonian Tax and
Customs Board of the invoice that is due for payment.
8. Force majeure
8.1. Breach of contractual obligations is excusable if the party was in breach of obligations due to
force majeure. The parties consider force majeure to be a circumstance that the breaching
party could not influence and, based on the principle of reasonableness, could not be
expected to take this circumstance into account or to avoid it at the time of awarding the
procurement contract, or overcome an impeding circumstance or its consequence, for
example natural disasters, general power outages, wars, blockade. The parties do not
consider the inability of the seller's third-party contractual partner to perform the
procurement contract as force majeure.
8.2. If any circumstance corresponding the conditions of force majeure led to the non-
performance of the procurementcontract within the deadline specified in the procurement
contract or its annexes, and the effect is temporary, the party who has breached the
obligation arising from the procurement contract is excusable only during the time when
force majeure prevented the performance of the obligation.
8.3. Due to the event of a force majeure, the deadline for the performance of the contractual
obligation is be postponed in accordance with the duration of the force majeure event, but
for no more than 90 days unless otherwise agreed by the parties.
8.4. A party that is not able to perform its obligations due to force majeure must immediately
inform the other party of the occurrence and termination of such a situation. Non-
notification or untimely notification deprives the party of the right to refer to the excusability
of the violation, i.e. the occurrence of force majeure, and the party that breached the
obligation to inform is responsible for the violation of the contractual obligation in
accordance with the provisions of the contract.
8.5. In the event that the effect of force majeure is permanent and does not allow the parties to
perform their contractual obligations in whole or in part, the parties have the right to
terminate the contract or withdraw from the contract by making a corresponding statement
of termination or withdrawal from the contract to the other party.
4/9
8.6. The parties do not treat the consequences of the Covid-19 pandemic as force majeure. In the
event that, after the award of the contract, new unforeseen restrictions related to the Covid-
19 pandemic are introduced and due to which the performance of the contract is not possible
or is prevented, then this may be considered as force majeure.
8.7. The parties shall not consider the impact of import restrictions related to the Russian
Federation and Belarus on the performance of the obligation to supply goods/provision of
services as force majeure if these circumstances existed at the time of awarding the
procurement contract.
9. Warranty obligation
9.1. The warranty obligation applies to goods/services for which it is possible to provide a
warranty.
9.2. The seller with the procurement contract provides a warranty for the goods/services for the
period specified in the technical description or under the conditions set out in the
procurement contract.
9.3. The warranty commences from the day of transfer to the buyer of the goods/service (in the
case of services, from the signing of the act of delivery and receipt, unless otherwise specified
in the procurement contract).
9.4. In the event that the manufacturer's warranty of the goods/services is in any way more
favorable to the buyer (for example, in terms of time) than the warranty obligation specified
in the general terms and conditions or the procurement contract, the seller obligates to
organize the realization of the warranty claim for the buyer in the event of this incident under
conditions more favorable to the buyer, which result from the terms of the manufacturer's
warranty.
9.5. All defects that occur during the warranty period are covered by the warranty, taking into
account normal wear and tear, unless otherwise agreed in the pr contract.
9.6. The buyer is obligated to inform the seller of any defects in the goods/service that arise
during the warranty period to the seller's email address, unless otherwise agreed in the
procurement contract.
9.7. The buyer is obligated to replace defective goods free of charge or eliminate deficiencies in
the services provided within 60 days from the receipt of the buyer's respective reasoned
warranty claim, unless otherwise agreed in the procurement contract.
9.8. The seller bears all costs related to the replacement of defective goods or the rectification of
defects in the provided services.
9.9. Replaced goods or services during the warranty period will be covered by a new warranty of
the same duration as the original warranty.
10. Confidentiality and security requirements
10.1. The parties understand as confidential information any information which becomes known
in the performance of the procurement contract, personal data, security data, clearly marked
documents declared for internal use and other information that, the disclosure of which
could harm the interests of the buyer. Confidential information does not include information
that is requires to be disclosed by law, provided that such disclosure is effected in the most
restrictive manner from among the available options.
10.2. In accordance with the confidentiality requirement, the party undertakes not to disclose the
other party's confidential information during the validity of the procurement contract or later
without the written consent of the other party, including information intended for internal
use. The party protects the confidentiality of the information that became known to him
during the performance of the procurement contract.
10.3. The seller obligates not to use any document or information attached to the procurement
contract without the buyer's written consent, except in cases necessary for the perfomance
of the procurement contract. All documents except the procurement contract and its
annexes, are the property of the buyer, and if the buyer requires is, the seller is obligated to
5/9
return them after the termination of the procurement contract.
10.4. If the seller needs to enter the territory of the area of government of the Ministry of Defense
in order to perform the procurement contract, the seller is obligated to comply with the
applicable security requirements. If the seller uses subcontractors in the said territory, they
must be previously approved in writing by the buyer, and they are also subject to all security
requirements set out in the related procurement. The seller is responsible for ensuring that
subcontractors comply with the security requirements.
10.5. Communication to the public relating to the subject-matter of the procurement contract or
the performance thereof, including press releases, references to the buyer in advertising or
online publications, is permitted only with the express consent of the buyer in a format that
can be reproduced in writing.
11. Intellectual property rights
In the event that the goods or any part thereof (including relevant documentation) are protected by
intellectual property rights, the seller grants the buyer a worldwide irrevocable non-exclusive licence
within the meaning of the Copyright Act, which is valid until the expiration of the copyrights. The
licence is considered transferred from the moment of transfering of the goods or any part thereof
(including the relevant documentation), for which a separate fee is not paid. The terms and
conditions of transfer and use of intellectual property rights may be agreed otherwise in the
procurement contract.
12. Liability
12.1. The parties bear responsibility towards each other in the event of improper performance or
non-performance of the obligations arising from the procurement contract in accordance
with the general terms and conditions, the terms of the related procurement, the provisions
of the procurement contract and applicable legislation.
12.2. Ownership of the goods and the risk of accidental destruction and damage are generally
transferred from the seller to the buyer upon proper handover of the goods, unless the
parties have agreed otherwise in the related procurement.
12.3. The seller is responsible for non-conformity (defects) of the goods or services to the
conditions of the procurement contract, if the non-conformity exists during the transfer of
the risk of accidental destruction and damage to the buyer, and if the non-conformity of the
goods to the conditions of the procurement contract is discovered (i.e. the defects could not
be detected during their normal inspection, so-called hidden defects) after the said risk
transfer to the buyer.
12.4. In the event that the seller performs the procurement contract improperly, the buyer has the
right to refuse to accept the goods and/or service and to perform the obligation to pay the
purchase price, and to submit to the seller a demand for the performance of the obligation
in the manner stipulated in the procurement contract after learning of the breach of the
obligation, giving the seller a reasonable deadline to perform the procurement contract.
Delivery by the seller is considered delayed until the appropriate goods and/or services are
handed over to the buyer.
12.5. The goods do not comply with the terms of the procurement contract, among other things,
if the goods do not have the agreed characteristics, the goods cannot be used for the
intended purpose, a third party has a claim against the goods or other rights that he can
submit, the goods are not packaged in accordance with the terms of the procurement
contract or there is no delivery note.
12.6. The service does not comply with the the terms of procurement contract, among other
things, if the service has not been provided in accordance with the expected quality, the
result of the service does not allow the goods to be used as intended, or if an invoice has not
been submitted for the service.
12.7. The buyer or an authorized representative of the buyer is obligated to inform the seller via
email of any non-conformity with the terms and conditions of the contract for the goods or
6/9
services (i.e., shortage of goods or services) within 60 days from the moment when the buyer
or the buyer’s authorized representative became aware of the non-conformity of the goods
or services with the terms and conditions of the contract. In the notice, the buyer undertakes
to require the seller to perform the obligation, while at the same time granting the seller a
reasonable deadline, which may not normally exceed 30 days.
12.8. If the buyer does not inform the seller of the deficiencies in the goods or services within the
time limit set out in the contract after becoming aware of the defect, the seller is released
from liability for defects in the goods or services, except if the failure to report the
deficiencies was reasonably justifiable.
12.9. In case of the timely non-delivery of the goods or the failure to provide the service, the buyer
has the right to request from the seller a contractual penalty of up to 0.25% of the cost of
the undelivered goods or unprovided service per day for each day delayed, but not exceeding
50% of the contract value.
12.10. Parties have the right, in addition to terminating the procurement contract or withdrawing
from the procurement contract, to demand a contractual penalty for a material breach,
according to the extent of the incurred damage.
12.11. In case the seller breaches any other contractual obligation than timely delivery or service
provision, the buyer has the right to demand a contractual penalty from the seller, up to 10%
of the total cost of the goods or services that are the subject of the entire contract.
12.12. In the event of a breach of confidentiality obligations, the party has the right to demand a
contractual penalty of up to 10 000.00 euros for each corresponding incident from the party
that breached the obligation.
12.13. If the buyer delays the payment of the invoice, the seller has the right to demand from the
buyer an interest as specified in § 113 (1) of the Law of Obligations Act on the unpaid amount
for each day of delay, up to 0.25% per day, provided that the delay has been notified to the
buyer within 30 days of its occurrence. The total amount of interest does not exceed 10% of
the delayed amount.
12.14. The contractual penalty is agreed upon to ensure the performance of the agreed obligation,
not as a substitute for the performance of the obligation. Demanding a contractual penalty
does not deprive the buyer of the right to seek compensation from the seller for the damages
caused by a breach of the procurement contract.
12.15. Contractual penalties and default interest are paid within 28 days of receiving the
corresponding claim. The buyer has the right to deduct sums contractual penalty claims and
the sums of compensation for damages submitted by the buyer from the amount payable for
the seller.
12.16. If the seller fails to perform the procurement contract, the buyer has the right to award a
procurement contract with the next tenderer in the related procurement and to demand
compensation from the seller for the difference in cost between the value of the tender
submitted by the seller and the value of the tender submitted by the new successful
tenderer.
12.17. In the case of a quantity shortage of the goods, the buyer is entitled to accept the goods and
request the seller to deliver the missing quantity of goods to the destination specified by the
buyer within the Republic of Estonia at the seller’s expense.
13. Grounds for termination of the procurement contract
13.1. In the event of termination of or withdrawal from the procurement contract, the buyer grants
the seller a reasonable time for performance of the contract, which generally may not exceed
30 days. The granted time for performance of the procurement contract does not relieve the
party from liability for a breach of obligation.
13.2. After the expiry of the additional time for the performance of the procurement contract, the
buyer may submit a written termination or withdrawal statement to the seller. The
termination of or withdrawal from the procurement contract is considered to have occurred
from the moment the seller receives the termination/withdrawal statement. An application
of termination or withdrawal is not required if the buyer, when granting an additional time,
7/9
has made it clear in writing in advance that the buyer terminates of or withdraw from the
procurement contract if the contractual obligations are not performed within the time. In
this case the procurement contract terminates upon the expiration of the additional time
and on term that the seller has not offered a appropriate performance to the buyer.
13.3. A party is entitled to terminate or withdraw the procurement contract without further notice
if the other party has significantly breached the obligations arising from the procurement
contract (material breach). In this case, one party submits a written termination/withdrawal
statement to the other party within a reasonable time from becoming aware of the material
breach of the contract. The termination/withdrawal of the procurement contract(s) is
considered to have occurred when the party has received the termination/withdrawal
statement. Material breaches of the contract include, among other things, situations where:
13.3.1. obligations arising from the general terms and/or the procurement contract are
violated intentionally or due to gross negligence.
13.3.2. the seller has not performed their obligations within the additional time given by
the buyer;
13.3.3. the seller informs the buyer of the refusal to perform;
13.3.4. false information or falsified data is provided;
13.3.5. there are breaches of the confidentiality obligation;
13.3.6. the breach of obligation gives the party a reasonable ground to believe that the
other party will not perform the obligation in the future.
13.3.7. the seller commits legal violations in the sale of goods or provision of services that
are the subject of the procurement contract during the validity of the contract.
13.3.8. the seller's permits for performing obligations expire, and the seller does not
extend them.
13.3.9. the seller has breached the general terms, related procurement and/or
procurement contract conditions more than five times.
13.4. The buyer has the right to terminate the procurement contract extraordinary if a bankruptcy
decision has been made against the seller or a liquidation process has been initiated, or if the
seller's necessary authorisations for performing obligations expire, and the extension of
authorisatsions is not possible due to circumstances beyond the seller's control.
13.5. The buyer has the right to terminate the procurement contract at any time by informing the
seller at least 90 days in advance.
14. Final provisions
14.1. The procurement contract enters into force upon signing by the Seller, unless otherwise
specified in the procurement contract.
14.2. In the performance of the procurement contract and in the event of disputes arising from
the procurement contract, the legislation of the Republic of Estonia applies, unless the
parties have agreed otherwise.
14.3. The parties have agreed to take all measures to solve any disagreements between them
through negotiations. In the event of not reaching an agreement, the dispute will be settled
in accordance with the legislation of the Republic of Estonia in the Harju County Court, unless
the parties have agreed otherwise.
14.4. The invalidity of a single provision of the procurement contract does not lead to the invalidity
of the entire procurement contract or other provisions.
14.5. Neither party has the right to transfer its contractual rights and obligations to third parties
without the written consent of the other party.
14.6. Modifications to the awarded procurement contract may be agreed upon on basis and scope
specified in the Public Procurement Act.
14.7. Modifications to the procurement contract are valid if they have documented in writing. If
the written form requirement is not followed, the modifications to the contract are void. All
contract modifications enter into force after being signed by the parties or on the date set
8/9
by the parties, unless otherwise agreed.
14.8. All notifications that do not have legal consequences will be submitted by email and must be
addressed to the contract contact persons, unless otherwise agreed in the procurement
contract.
14.9. The party informs the other party immediately by email of any changes in contact person or
other data. This notice shall not be considered as a modification to the procurement contract.
14.10. The transmission of notices and other information with legal significance between the parties
must be done in writing or digitally signed by e-mail. The notice is considered received if it
has been delivered by a postal authority with a return receipt to the address specified in the
procurement contract and five days have passed since the notice was posted. If the notice is
sent by e-mail, the notice is considered received on the next working day.
14.11. Hierarchy of documents: related procurement technical description, procurement contract,
general terms.
9/9
1 / 19
HANKEPASS
Hankepass ehk Euroopa ühtne hankedokument (ESPD) on ettevõtja enda kinnitus, mis on esialgne tõend
ametiasutuste või kolmandate isikute poolt väljastatavate tõendite asemel.
Pakkumus:546457
Ettevõtja: VAS "Elektroniskie sakari"
Roll: lead tenderer
I OSA: HANKE JA HANKIJAGA SEOTUD TEAVE
Teave avaldamise kohta
Teate number ELTs:
-
ELT URL:
Riigi ametlik teataja:
288047
Kui Euroopa Liidu Teatajas hankekuulutust avaldatud ei ole või kui selle avaldamist ei nõuta, peab avaliku
sektori hankija või võrgustiku sektori hankija ise teabe esitama, et hankemenetlust saaks üheselt
identifitseerida (nt viide siseriikliku avaldamise kohta).
Hankija andmed
Ametlik nimi:
Riigi Kaitseinvesteeringute Keskus (70009764)
Riik:
Eesti
Hankija aadress:
Järve tn 34a
Hankija veebiaadress:
https://www.kaitseinvesteeringud.ee/
E-posti aadress:
[email protected]
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
2 / 19
Teave hankemenetluse kohta
Hanke menetlusliik:
Piiratud hankemenetlus
Pealkiri:
Monitooringu tarkvata litsentsid
Lühikirjeldus:
Monitooringu tarkvara litsentside soetus
Avaliku sektori hankija või võrgustiku sektori hankija poolt toimikule antud viitenumber (kui on
asjakohane):
288047
Hanke liik:
Asjad
Hanke CPV-d:
30200000-1 Computer equipment and supplies
48900000-7 Miscellaneous software package and computer systems
50312600-1 Maintenance and repair of information technology equipment
72220000-3 Systems and technical consultancy services
72222300-0 Information technology services
72267000-4 Software maintenance and repair services
Hanke osad
Hanke osade kohta kehtivad järgnevad nõuded:
Tingimuse kirjeldus:
Pakkumusi võib esitada: Kõigile osadele
Maksimaalne osade arv, mille kohta võib pakkumusi esitada:
Maksimaalne osade arv, mille kohta võidakse sõlmida leping ühe pakkujaga:
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
3 / 19
II OSA: ETTEVÕTJAGA SEOTUD TEAVE
A: Teave ettevõtja kohta
Nimi: VAS "Elektroniskie sakari"
Registrikood: 40003021907
Riik: LVA
Aadress: 5 Eksoprta street Riga LV-1010
Üldine veebileht:
Kontaktisikud: Māris Aleksandrovs
Kontaktide e-posti aadressid:
[email protected]
Kontaktide telefoninumbrid: +371 29168983
Ettevõtte suurus: Medium-sized enterprise
Töötajate arv: 98
Käive: 8859028
Valuuta: EUR
Finantsalase võimekuse kirjeldus:
Tehnilise võimekuse kirjeldus:
Teostatud tööde kirjeldus:
Ettevõtja tegevusvaldkond:Radiofrequency spectrum technical administration in Latvia - planning of the
technical use of the RF spectrum etc., measurements of radio signal electromagnetic field intensity, RF
interference and radio signal source investigation, measurements of technical parameters of transmitted signals
and electromagnetic compatibility expertise, experience with 5G and 4G mobile network signal parameters and
ERIP power, Determination of mobile network coverage.
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
4 / 19
ETTEVÕTJA ON KAITSTUD TÖÖKOHT
Ainult reserveeritud hangete puhul: kas ettevõtja puhul on tegemist kaitstud töökohaga, sotsiaalse
ettevõttega või ta täidab lepingut kaitstud tööhõive programmide raames?
Küsimused ettevõtjale:
1. Mis on Teie vastus?
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Ei
ETTEVÕTJA ON KANTUD TUNNUSTATUD ETTEVÕTJATE AMETLIKKU
NIMEKIRJA
Kui see on asjakohane, siis kas ettevõtja on kantud tunnustatud ettevõtjate ametlikku nimekirja
või kas tal on olemas samaväärne tõend (nt riikliku (eel)kvalifitseerimissüsteemi alusel)?
Küsimused ettevõtjale:
1. Mis on Teie vastus?
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Ei
HANKEMENETLUSES KOOS OSALEVAD ETTEVÕTJAD
Kas ettevõtja osaleb hankemenetluses koos teistega?
Küsimused ettevõtjale:
Ettevõtja nimi:VAS "Elektroniskie sakari"
Ettevõtja ID:40003021907
Ettevõtja roll: peapakkuja
4. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Ei
5. URL
Vastus: https://www.vases.lv/en
6. Kood
Vastus: Registration No. 40003021907
TEAVE TEISTE ÜKSUSTE SUUTLIKKUSELE TOETUMISE KOHTA
Kas ettevõtja toetub teiste üksuste suutlikkusele, et täita esitatud valikukriteeriumid ning eeskirjad
(kui neid on)?
Küsimused ettevõtjale:
1. Mis on Teie vastus?
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Ei
6. URL
Vastus: https://riigihanked.riik.ee
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
5 / 19
TEAVE NENDE ALLHANKIJATE KOHTA, KELLE NÄITAJATELE ETTEVÕTJA
EI TUGINE
Kas ettevõtja kavatseb sõlmida lepingu mis tahes osa kohta allhanke kolmanda isikuga?
Küsimused ettevõtjale:
1. Mis on Teie vastus?
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Ei
6. URL
Vastus: https://riigihanked.riik.ee
HANKE OSAD
Hanke osad, mille kohta ettevõtja soovib pakkumuse esitada
Küsimused ettevõtjale:
1. Hanke osa number
Vastus: 1
2. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Jah
3. URL
Vastus: https://riigihanked.riik.ee
4. Kood
Vastus: 255269
5. Väljaandja
Vastus: Riigi Kaitseinvesteeringute Keskus (70009764)
ETTEVÕTJA KINNITUSED MAKSUDE TASUMISE KOHTA
Kas ettevõtja saab esitada tõendi sotsiaalkindlustusmaksete ja maksude tasumise kohta või esitada
teabe, mis võimaldaks avaliku sektori hankijal või võrgustiku sektori hankijal saada sellise teabe
otse ükskõik millise liikmesriigi tasuta andmebaasist?
Küsimused ettevõtjale:
1. Mis on Teie vastus?
Vastus: Jah
2. Kas see teave on elektrooniliselt kättesaadav?
Vastus: Jah
3. URL
Vastus: https://www6.vid.gov.lv/NPAR
4. Kood
Vastus: https://www6.vid.gov.lv/NPAR web page only in Latvian
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
6 / 19
B: Teave ettevõtja esindajate kohta
Eesnimi:
Perekonnanimi:
Sünniaeg:
Sünnikoht:
Aadress:
Linn/vald:
Postiindeks:
Riik:
E-post:
Telefon:
Vajaduse korral esitage üksikasjalik teave esindamise kohta (selle vormid, ulatus, eesmärk, ...):
III OSA: KÕRVALDAMISE ALUSED
A: Kõrvalejätmise alused seoses kriminaalasjas tehtud süüdimõistva otsusega
OSALEMINE KURITEGELIKUS ORGANISATSIOONIS
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
kohtuotsusega süüdi mõistetud kuritegelikus organisatsioonis osalemise eest kõige rohkem
viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise
kohustus endiselt?
Viide seadusele:
RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud kuritegelikus ühenduses osalemise eest". Kui hankemenetlusest
kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud
meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui
tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke
alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
KORRUPTSIOON
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
7 / 19
kohtuotsusega süüdi mõistetud korruptsiooni eest kõige rohkem viimase viie aasta jooksul või
kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt? See
kõrvalejätmise alus hõlmab ka korruptsiooni avaliku sektori hankija (võrgustiku sektori hankija)
või ettevõtja riigi õiguses sätestatud määratluses.
Viide seadusele:
RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud aususe kohustuse rikkumise või korruptiivse teo eest". Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
PETTUS
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
kohtuotsusega süüdi mõistetud kelmuse eest kõige rohkem viimase viie aasta jooksul või kehtib
süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?
Viide seadusele:
RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud kelmuse eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib
ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma
usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
8 / 19
TERRORIAKTI TOIMEPANEK VÕI TERRORISTLIKU TEGEVUSEGA SEOTUD
ÕIGUSRIKKUMISED
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
kohtuotsusega süüdi mõistetud terroriakti toimepaneku või terroristliku tegevusega seotud
õigusrikkumiste eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas
kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?
Viide seadusele:
RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud terroriakti toimepaneku või muu terroristliku tegevusega seotud kuriteo
või sellele kihutamise, kaasaaitamise või selle katse eest". Kui hankemenetlusest kõrvaldamise
alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid
oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
RAHAPESU VÕI TERRORISMI RAHASTAMINE
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
kohtuotsusega süüdi mõistetud rahapesu või terrorismi rahastamise eest kõige rohkem viimase
viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus
endiselt?
Viide seadusele:
RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud rahapesualase süüteo või terrorismi rahastamise eest". Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
9 / 19
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
LASTE TÖÖJÕU KASUTAMINE JA MUUD INIMKAUBANDUSE VORMID
Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused
seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva
kohtuotsusega süüdi mõistetud laste tööjõu kasutamise või muude inimkaubanduse vormide eest
kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud
kõrvalejäämise kohustus endiselt?
Viide seadusele:
RHS § 95 lg 1 p 3 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud laste tööjõu ebaseadusliku kasutamise või inimkaubandusega seotud
teo eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada
tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise
võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või
hankija on selle hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
8. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
B: Kõrvalejätmise alused seoses maksude või sotsiaalkindlustusmaksete tasumisega
MAKSUDE TASUMINE
Kas ettevõtja on rikkunud oma maksude tasumise kohustusi nii asukohariigis kui ka avaliku
sektori hankija või võrgustiku sektori hankija liikmesriigis, kui see erineb asukohariigist?
Viide seadusele:
RHS § 95 lg 1 p 4 „kellel on riikliku maksu, makse või keskkonnatasu maksuvõlg
maksukorralduse seaduse tähenduses või maksuvõlg /…/ tema asukohariigi õigusaktide kohaselt“
Kehtib: Kõik osad
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
10 / 19
Tingimuse kirjeldus:
Piirmäär: 0
Valuuta: EUR
Lisainfo: Maksukorralduse seaduse kohaselt ei väljasta maksuhaldur maksuvõlgade tõendit juhul,kui
maksukohustuslasel olev kõikide sama maksuhalduri hallatavate maksude võlg, arvestamata
haldusaktiga kindlaksmääramata intressi, on väiksem kui 100 eurot või kui maksuvõla tasumine on
ajatatud. Välismaise ettevõtja puhul väljastatakse maksuvõlgade tõend tema asukohariigi õigusaktide
kohaselt.
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
12. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
SOTSIAALKINDLUSTUSMAKSETE TASUMINE
Kas ettevõtja on rikkunud oma sotsiaalkindlustusmaksete tasumise kohustusi nii asukohariigis
kui ka avaliku sektori hankija või võrgustiku sektori hankija liikmesriigis, kui see erineb
asukohariigist?
Viide seadusele:
RHS § 95 lg 1 p 4 „kellel on riikliku /…/ makse /…/ maksuvõlg maksukorralduse seaduse
tähenduses või sotsiaalkindlustusemaksete võlg tema asukohariigi õigusaktide kohaselt
Kehtib: Kõik osad
Tingimuse kirjeldus:
Piirmäär: 0
Valuuta: EUR
Lisainfo: Maksukorralduse seaduse kohaselt ei väljasta maksuhaldur maksuvõlgade tõendit juhul,kui
maksukohustuslasel olev kõikide sama maksuhalduri hallatavate maksude võlg, arvestamata
haldusaktiga kindlaksmääramata intressi, on väiksem kui 100 eurot või kui maksuvõla tasumine on
ajatatud. Välismaise ettevõtja puhul väljastatakse maksuvõlgade tõend tema asukohariigi õigusaktide
kohaselt.
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
12. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
C: Kõrvalejätmise alused seoses maksejõuetusega, huvide konfliktiga või ametialaste
käitumisreeglite rikkumisega
KESKKONNAÕIGUSE VALDKONNAS KOHALDATAVATE KOHUSTUSTE TÄITMATA
JÄTMINE
Kas ettevõtja on enda teada rikkunud keskkonnaõiguse valdkonnas kohaldatavaid kohustusi?
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
11 / 19
Viide seadusele:
RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid
keskkonnaõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus
esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma
usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
SOTSIAALÕIGUSE VALDKONNAS KOHALDATAVATE KOHUSTUSTE TÄITMATA
JÄTMINE
Kas ettevõtja on enda teada rikkunud sotsiaalõiguse valdkonnas kohaldatavaid kohustusi?
Viide seadusele:
RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid
sotsiaalõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus
esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma
usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
TÖÖÕIGUSE VALDKONNAS KOHALDATAVATE KOHUSTUSTE TÄITMATA
JÄTMINE
Kas ettevõtja on enda teada rikkunud tööõiguse valdkonnas kohaldatavaid kohustusi?
Viide seadusele:
RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid tööõiguse
valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib
ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma
usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
12 / 19
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
PANKROT
Kas ettevõtja on pankrotis?
Viide seadusele:
RHS § 95 lg 4 p 3 „kes on pankrotis, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud
juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral
esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks.
Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava
hankega või hankija on selle hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
MAKSEJÕUETUS
Kas ettevõtja suhtes on algatatud maksejõuetus- või likvideerimismenetlus?
Viide seadusele:
RHS § 95 lg 4 p 3 „kes on likvideerimisel või kelle suhtes on algatatud pankrotimenetlus, välja
arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest
kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud
meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui
tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke
alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
13 / 19
KOKKULEPE VÕLAUSALDAJATEGA
Kas ettevõtja on sõlminud kokkuleppe võlausaldajatega?
Viide seadusele:
RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt,
välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
SISERIIKLIKU ÕIGUSE KOHANE SAMALAADNE OLUKORD, NÄITEKS PANKROT
Kas ettevõtja on siseriiklike õigusnormide alusel toimuva samalaadse menetluse tõttu
samalaadses olukorras?
Viide seadusele:
RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt“,
välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel. Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
VARA HALDAB LIKVIDEERIJA
Kas ettevõtja vara haldab likvideerija või kohus?
Viide seadusele:
RHS § 95 lg 4 p 3 „kes on pankrotis, likvideerimisel või kelle suhtes on algatatud
pankrotimenetlus või kes on muus sellesarnases olukorras tema asukohamaa õigusaktide
kohaselt, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
14 / 19
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
ÄRITEGEVUS ON PEATATUD
Kas ettevõtja äritegevus on peatatud?
Viide seadusele:
RHS § 95 lg 4 p 3 „kelle äritegevus on peatatud, välja arvatud asjade ostmisel RHS § 49 lõikes 4
sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja
soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse
taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära
ületava hankega või hankija on selle hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
4. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
SÜÜDI AMETIALASTE KÄITUMISREEGLITE OLULISES RIKKUMISES
Kas ettevõtja on süüdi ametialaste käitumisreeglite olulises rikkumises? Vt siseriiklikud
õigusaktid, asjaomane teade või hankedokumendid, kui see on asjakohane.
Viide seadusele:
RHS § 95 lg 4 p 4 „kes on raskelt eksinud ametialaste käitumisreeglite vastu ja see muudab tema
aususe küsitavaks“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral
esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks.
Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava
hankega või hankija on selle hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
15 / 19
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
KONKURENTSI MOONUTAMISE EESMÄRGIL TEISTE ETTEVÕTJATEGA
SÕLMITUD KOKKULEPPED
Kas ettevõtja on teiste ettevõtjatega sõlminud kokkuleppeid, mille eesmärk on moonutada
konkurentsi?
Viide seadusele:
RHS § 95 lg 4 p 5 „konkurentsi kahjustava kokkuleppe, ettevõtjate ühenduse otsuse või
kooskõlastatud tegevuse tõttu“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja
soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse
taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära
ületava hankega või hankija on selle hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
HANKEMENETLUSES OSALEMISEGA KAASNEV HUVIDE KONFLIKT
Kas ettevõtja on teadlik hankemenetluses osalemisega kaasnevast mis tahes huvide konfliktist
siseriikliku õiguse, asjakohase teatise või hankedokumentide kohaselt?
Viide seadusele:
RHS § 95 lg 4 p 6 „kui huvide konflikti ei ole muude vahenditega võimalik vältida“. Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
3. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
16 / 19
OTSENE VÕI KAUDNE OSALEMINE KÄESOLEVA HANKEMENETLUSE
ETTEVALMISTAMISEL
Kas ettevõtja või temaga seotud ettevõtja on nõustanud avaliku sektori hankijat või võrgustiku
sektori hankijat hankemenetluse ettevalmistamisel või olnud muul viisil seotud hankemenetluse
ettevalmistamisega?
Viide seadusele:
RHS § 95 lg 4 p 7 „kelle pakkumuse või taotluse koostamisel on osalenud isik, kes on osalenud
sama riigihanke ettevalmistamisel või on muul viisil hankijaga seotud, ja sellele isikule seetõttu
teadaolev info annab talle eelise teiste riigihankes osalejate eest ning sellest tingitud konkurentsi
moonutamist ei ole muude vahendistega võimalik vältida“. Kui hankemenetlusest kõrvaldamise
alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid
oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on
rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette
näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
3. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
ENNETÄHTAEGNE LÕPETAMINE, KAHJUTASU VÕI VÕRRELDAVAD
SANKTSIOONID
Kas ettevõtja on kogenud, et varasem riigihankeleping või võrgustiku sektori hankijaga sõlmitud
varasem hankeleping või varasem kontsessioonileping on lõpetatud enneaegselt, või on määratud
kahjutasu või sellega võrreldavad sanktsioonid seoses kõnealuse varasema lepinguga?
Viide seadusele:
RHS § 95 lg 4 p 8 „kes on oluliselt või pidevalt rikkunud eelnevalt sõlmitud hankelepingu olulist
tingimust või hankelepingute olulisi tingimusi nii, et rikkumise tulemusena on lepingust
taganetud või leping üles öeldud, hinda alandatud, hüvitatud kahju või makstud leppetrahvi". Kui
hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud. Alates 1.09.2017 alustatud hangete tulemusena sõlmitud
riigihankelepingute kohta leiab infot riigihangete registrist.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
5. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
17 / 19
SÜÜDI VALEANDMETE ESITAMISES, ON JÄTNUD TEAVET ESITAMATA, EI SUUDA
NÕUTUD DOKUMENTE ESITADA, HANKINUD KÄESOLEVA MENETLUSE KOHTA
KONFIDENTSIAALSET TEAVET
Kas ettevõtja on olnud ühes järgmistest olukordadest:
a) ta on kõrvalejätmise aluste puudumise või valikukriteeriumide täitmise kontrollimiseks
nõutava teabe esitamisel esitanud valeandmeid;
b) ta on jätnud sellist teavet esitamata;
c) ta ei ole esitanud viivitamata avaliku sektori hankija või võrgustiku sektori hankija nõutud
täiendavad dokumendid, ja
d) ta on tegutsenud eesmärgiga mõjutada lubamatul viisil avaliku sektori hankija või võrgustiku
sektori hankija otsustusprotsessi, et saada konfidentsiaalseid andmeid, mis võivad anda talle
põhjendamatu eelise hankemenetluses, või hooletusest esitanud eksitavat teavet, mis võib
oluliselt mõjutada kõrvalejätmise, valiku või lepingu hindamise kohta tehtavaid otsuseid?
Viide seadusele:
RHS § 95 lg 4 p 9 „kes on esitanud valeandmeid käesolevas paragrahvis sätestatud või RHS §-
des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele vastavuse kohta“;
RHS § 95 lg 4 p 9 „kes on jätnud andmed käesolevas paragrahvis sätestatud või käesoleva
seaduse §-des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele
vastavuse kohta esitamata“;
RHS § 95 lg 4 p 9 „kes on jätnud käesoleva seaduse § 104 lõigete 7 ja 8 alusel hankija nõutud
täiendavad dokumendid esitamata“;
RHS § 95 lg 4 p 10 „kes on tegutsenud eesmärgiga mõjutada hankijat või esitanud hooletusest
eksitavat teavet, mis on võinud mõjutada hankija otsuseid riigihankes, või on tegutsenud
eesmärgiga saada konfidentsiaalset teavet, mis on võinud anda talle põhjendamatu eelise teiste
riigihankes osalejate ees“.
Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
2. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
D: Ainult siseriiklikest õigusaktidest tulenevad kõrvalejätmise alused
AINULT SISERIIKLIKEST ÕIGUSAKTIDEST TULENEVAD KÕRVALEJÄTMISE
ALUSED: RAHVUSVAHELISE SANKTSIOONI SUBJEKT
Kas ettevõtja on rikkunud RHS § 95 lg 1 p-st 5 tuleneva kõrvalejätmise alusega seotud kohustusi?
Viide seadusele:
RHS § 95 lg 1 p 5. Alates 14.08.2022 kontrollib hankija kõrvaldamise aluse puudumist pakkuja
või taotleja kinnituse alusel. Hankija võib põhjendatud kahtluse korral nõuda pakkujalt või
taotlejalt täiendavate andmete või tõendite esitamist, mis võimaldavad kõrvaldamise alust
kontrollida (RHS § 96 lg 2.1).
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
18 / 19
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
2. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
AINULT SISERIIKLIKEST ÕIGUSAKTIDEST TULENEVAD KÕRVALEJÄTMISE
ALUSED: SEADUSLIKU ALUSETA VIIBIVALE VÄLISMAALASELE TÖÖTAMISE
VÕIMALDAMISE EEST
Kas ettevõtja on rikkunud RHS § 95 lg 1 p-st 2 tuleneva kõrvalejätmise alusega seotud kohustusi?
Viide seadusele:
RHS § 95 lg 1 p 2 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või
muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda
kontrollida, on karistatud riigis ilma seadusliku aluseta viibivale välismaalasele töötamise
võimaldamise või välismaalase Eestis töötamise tingimuste rikkumise võimaldamise, sealhulgas
seaduses sätestatud töötasu määrast väiksema töötasu maksmise eest“. Kohustuslik kõrvaldamise
alus.
Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
2. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
AINULT SISERIIKLIKEST ÕIGUSAKTIDEST TULENEVAD KÕRVALEJÄTMISE
ALUSED: KARISTATUD MAKSUALASTE SÜÜTEGUDE EEST
Kas ettevõtja on rikkunud RHS § 95 lg 4 p-st 11 tuleneva kõrvalejätmise alusega seotud
kohustusi?
Viide seadusele:
RHS § 95 lg 4 p 11 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget või muud
seaduslikku esindajat on karistatud maksualaste süütegude eest“. Vabatahtlik kõrvaldamise alus.
Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle
kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on
ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle
hanke alusdokumentides ette näinud.
Kehtib: Kõik osad
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
19 / 19
Ettevõtjalt oodatavad vastused:
1. Mis on Teie vastus? (Radio button with "Yes/No" options)
Vastus: Ei
2. Kas see teave on elektrooniliselt kättesaadav? (Radio button with "Yes/No" options)
Vastus: Ei
Concluding statements
The economic operator formally declares that the information stated is accurate and correct and that it has been
set out in full awareness of the consequences of serious misrepresentation. The undersigned formally declare to
be able, upon request and without delay, to provide the certificates and other forms of documentary evidence
referred to. The undersigned formally consent to the Buyer gaining access to documents supporting the
information, which has been provided in this document.
Kinnituse andja nimi:
Koostatud 05.03.2025 12:57:43
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
PAKKUMUS
HINDAMISKRITEERIUMID JA HINNATAVAD NÄITAJAD
Viitenumber: 288047
Hankija: Riigi Kaitseinvesteeringute Keskus (70009764)
Hange: Monitooringu tarkvata litsentsid
Pakkumus: 546457
Ettevõtja: VAS "Elektroniskie sakari" (40003021907), roll: peapakkuja
OSA 1 – TOOTEGRUPI PÕHISED SOETUSED
Pakkumuse maksumust hinnatakse - Ilma maksudeta
1. Pakkumuse kogumaksumus käibemaksuta / Total Cost of the Tender without VAT
Tüüp ja hindamismeetod: Maksumus, vähim on parim
Osakaal: 100%
Hindamismetoodika kirjeldus: Madalaima väärtusega pakkumus saab maksimaalse arvu punkte. Teised pakkumused saavad punkte arvutades valemiga:
"osakaal" - ("pakkumuse väärtus" - madalaim väärtus") / "suurim väärtus" * "osakaal".
Kogus Ühik Ühiku hind Maksumus KM% Maksumus KM-ga Märkused
EUR 50000,000 50000,000 22 61000,000
Osa maksumus kokku KM-ta: 50000,000
Osa maksumus kokku KM-ga: 61000,000
Pakkumuse maksumus kokku
Maksumus kokku KM-ta: 50000,000
Maksumus kokku KM-ga: 61000,000
Koostatud 05.03.2025 12:57:44 1/1 https://riigihanked.riik.ee/rhr-web/#/procurement/
8162184/general-info
1/2
PAKKUMUS
VASTAVUSTINGIMUSED
Viitenumber: 288047
Hankija: Riigi Kaitseinvesteeringute Keskus (70009764)
Hange: Monitooringu tarkvata litsentsid
Pakkumus: 546457
Ettevõtja: VAS "Elektroniskie sakari" (40003021907), roll: peapakkuja
OSA 1: TOOTEGRUPI PÕHISED SOETUSED
PAKKUMUSE ESITAMINE / SUBMITTING AN OFFER
Pakkumuse esitamise aluseks on Tehniline kirjeldus (vt Lisa 1).
Pakkumuse palume esitada Maksumuse vormil (vt Lisa 2).
Tabeli palume täita vastavalt juhistele.
Pakkumus peab olema jõus vähemalt 60 kalendripäeva.
Pakkumus peab olema allkirjastatud pakkuja seadusjärgse esindaja või volitatud esindaja poolt.
Pakkuja esitab vajadusel esindusõigust tõendava volikirja.
/
The basis for submitting a bid is the Technical Description (see Annex 3).
Please submit the offer on the Cost form (see Annex 4).
Please fill in the form according to the instructions.
The offer must be valid for at least 60 calendar days.
The tender must be digitally signed by the tenderer's legal representative or authorized
representative. If necessary, the provider submits a power of attorney proving the right of
representation.
Ettevõtjalt oodatavad vastused:
1. Kas pakkuja kinnitab, et pakkumus kehtib vähemalt 60 kalendripäeva? (Raadionupp valikutega
"Jah/Ei")
Vastus: Jah
2. Kas pakkuja kinnitab, et on nõuetekohaselt täitnud Maksumuse vormi ja on selle pakkumusega
kaasa lisanud? / Does the tenderer confirm that he has properly filled out the Cost Form and has
included it with the offer (Excel) (Raadionupp valikutega "Jah/Ei")
Vastus: Jah
ÜHISPAKKUJATE VOLIKIRI
Ühispakkujad nimetavad riigihankega ning hankelepingu sõlmimise ja täitmisega seotud
toimingute tegemiseks endi seast volitatud esindaja.
Ettevõtjalt oodatavad vastused:
1. Kas tegemist on ühispakkumusega? (Raadionupp valikutega "Jah/Ei")
Vastus: Ei
2. Kui tegemist on ühispakkumusega, kas olete lisanud pakkumuse "Lisadokumentide" lehele
ühispakkujate volikirja? Kui tegemist ei ole ühispakkumusega, vastake "Ei"". (Raadionupp
valikutega "Jah/Ei")
Koostatud 05.03.2025 12:57:44
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
2/2
Vastus: Ei
ÄRISALADUS
Pakkuja märgib pakkumuses, milline teave on pakkuja ärisaladus ning põhjendab teabe
määramist ärisaladuseks.
Teabe ärisaladuseks määramisel lähtutakse ebaausa konkurentsi takistamise ja ärisaladuse kaitse
seaduse § 5 lõikes 2 sätestatust. Pakkuja ei või ärisaladusena märkida:
1) pakkumuse maksumust ega osamaksumusi;
2) teenuste hankelepingute puhul lisaks punktis 1 nimetatule muid pakkumuste hindamise
kriteeriumidele vastavaid pakkumust iseloomustavaid numbrilisi näitajaid;
3) asjade ja ehitustööde hankelepingute puhul lisaks punktis 1 nimetatule muid pakkumuste
hindamise kriteeriumidele vastavaid pakkumust iseloomustavaid näitajaid (RHS § 46.1).
Ettevõtjalt oodatavad vastused:
1. Kirjeldage lühidalt pakkumuses sisalduvat ärisaladust ja lisage selle määramise põhjendus või
märkige, et pakkumus ei sisalda ärisaladust. (Suur sisestusala (max pikkus 4000 tähemärki))
Vastus: The offer does not contain a trade secret.
EL NÕUKOGU SANKTSIOON. ALLTÖÖVÕTJAD, TARNIJAD JA TUGINETAVAD
ISIKUD.
Pakkuja kinnitab, et ta ei kaasa üle 10% hankelepingu maksumusest hankelepingu täitmisele
alltöövõtjaid, tarnijaid ega tugine kvalifitseerimistingimuste täitmisel selliste ettevõtjate
näitajatele, kes on:
1. Vene Föderatsiooni kodanik, resident või Vene Föderatsioonis asutatud ettevõtja, sh füüsilisest
isikust ettevõtja, juriidiline isik, asutus või muu üksus;
2. rohkem kui 50% ulatuses otseselt või kaudselt punktis 1 nimetatud isiku, asutuse või muu
üksuse omandis;
3. punktis 1 või 2 nimetatud isiku, asutuse või muu üksuse esindaja või tegutseb sellise isiku
juhiste alusel.
Hankija lükkab tagasi pakkumuse, mille alusel sõlmitav hankeleping oleks RSanS § 7 lg 1 alusel
tühine.
NÕUKOGU MÄÄRUS (EL) 2022/576, 8. aprill 2022, millega muudetakse määrust (EL) nr
833/2014, mis käsitleb piiravaid meetmeid seoses Venemaa tegevusega, mis destabiliseerib
olukorda Ukrainas. Määrust kohaldatakse riigihangetele alates rahvusvahelisest piirmäärast.
Ettevõtjalt oodatavad vastused:
1. Pakkuja kinnitab, et ta ei kaasa üle 10% hankelepingu maksumusest hankelepingu täitmisele
alltöövõtjaid, tarnijaid ega tugine kvalifitseerimistingimuste täitmisel selliste ettevõtjate
näitajatele, kes on: 1. Vene Föderatsiooni kodanik, resident või Vene Föderatsioonis asutatud
ettevõtja, sh füüsilisest isikust ettevõtja, juriidiline isik, asutus või muu üksus; 2. rohkem kui 50%
ulatuses otseselt või kaudselt punktis 1 nimetatud isiku, asutuse või muu üksuse omandis; 3.
punktis 1 või 2 nimetatud isiku, asutuse või muu üksuse esindaja või tegutseb sellise isiku juhiste
alusel. (Raadionupp valikutega "Jah/Ei")
Vastus: Jah
RAHVUSVAHELISE SANKTSIOONI OBJEKT
Pakkuja kinnitab, et pakutav kaup ei ole rahvusvahelise sanktsiooni objektiks või pärit
sanktsiooni all olevatest piirkondadest. Hankija lükkab tagasi pakkumuse, mille alusel sõlmitav
hankeleping oleks RSanS § 7 lg 1 alusel tühine.
Ettevõtjalt oodatavad vastused:
1. Pakkuja kinnitab, et pakutav kaup ei ole rahvusvahelise sanktsiooni objektiks ega pärit
sanktsiooni all olevatest piirkondadest. (Raadionupp valikutega "Jah/Ei")
Vastus: Jah
Koostatud 05.03.2025 12:57:44
https://riigihanked.riik.ee/rhr-web/#/procurement/8162184/general-info
<?xml version="1.0" encoding="UTF-8"?>
<QualificationApplicationResponse xmlns="urn:X-test:UBL:Pre-award:QualificationApplicationResponse" xmlns:ns6="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:ns5="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2" xmlns:ns8="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:ns7="http://data.europa.eu/p27/eforms-ubl-extension-aggregate-components/1" xmlns:cac="urn:X-test:UBL:Pre-award:CommonAggregate" xmlns:cbc="urn:X-test:UBL:Pre-award:CommonBasic" xmlns:ns9="http://data.europa.eu/p27/eforms-ubl-extensions/1" xmlns:ns4="http://data.europa.eu/p27/eforms-ubl-extension-basic-components/1">
<cbc:UBLVersionID schemeAgencyID="OASIS-UBL-TC">2.2</cbc:UBLVersionID>
<cbc:CustomizationID schemeAgencyID="CEN-BII" schemeVersionID="3.0">urn:www.cenbii.eu:transaction:biitrdm092:ver3.0</cbc:CustomizationID>
<cbc:ProfileID schemeAgencyID="CEN-BII" schemeVersionID="2.0">4.1</cbc:ProfileID>
<cbc:ID schemeAgencyID="RHR">20e7a79a-19e2-4297-a0dc-0a2bdb4db56c</cbc:ID>
<cbc:CopyIndicator>false</cbc:CopyIndicator>
<cbc:UUID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="4">0fddbf2d-1e33-4267-b04f-52b59b72ccb6</cbc:UUID>
<cbc:ContractFolderID schemeAgencyID="RHR">288047</cbc:ContractFolderID>
<cbc:IssueDate>2025-03-05</cbc:IssueDate>
<cbc:IssueTime>12:57:45</cbc:IssueTime>
<cbc:VersionID schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1.0</cbc:VersionID>
<cbc:ProcedureCode listID="ProcedureType" listAgencyID="EU-COM-OP" listVersionID="1.0">OTHER</cbc:ProcedureCode>
<cbc:QualificationApplicationTypeCode listID="QualificationApplicationType" listAgencyID="EU-COM-GROW" listAgencyName="DG GROW (European Commission)" listVersionID="2.0.2">SELFCONTAINED</cbc:QualificationApplicationTypeCode>
<cac:ContractingParty>
<cac:Party>
<cbc:WebsiteURI>https://www.kaitseinvesteeringud.ee/</cbc:WebsiteURI>
<cac:PartyIdentification>
<cbc:ID schemeAgencyID="RHR">70009764</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>Riigi Kaitseinvesteeringute Keskus</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:StreetName>Järve tn 34a</cbc:StreetName>
<cbc:CityName> Tallinn</cbc:CityName>
<cbc:PostalZone>11314</cbc:PostalZone>
<cac:Country>
<cbc:IdentificationCode listID="CountryCodeIdentifier" listAgencyID="ISO" listVersionID="1.0">EE</cbc:IdentificationCode>
<cbc:Name>Eesti</cbc:Name>
</cac:Country>
</cac:PostalAddress>
<cac:Contact>
<cbc:Name>KARIN PIIRI</cbc:Name>
<cbc:Telephone>+372 55945463</cbc:Telephone>
<cbc:ElectronicMail>
[email protected]</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:ContractingParty>
<cac:EconomicOperatorParty>
<cac:QualifyingParty>
<cbc:EmployeeQuantity>98</cbc:EmployeeQuantity>
<cac:BusinessClassificationScheme>
<cbc:ID schemeAgencyID="RHR">323fd8d4-a773-4a53-adc9-c0c2f09f2b39</cbc:ID>
<cbc:Description languageID="ET">Radiofrequency spectrum technical administration in Latvia - planning of the technical use of the RF spectrum etc., measurements of radio signal electromagnetic field intensity, RF interference and radio signal source investigation, measurements of technical parameters of transmitted signals and electromagnetic compatibility expertise, experience with 5G and 4G mobile network signal parameters and ERIP power, Determination of mobile network coverage.</cbc:Description>
<cac:ClassificationCategory/>
</cac:BusinessClassificationScheme>
<cac:FinancialCapability>
<cbc:ValueAmount currencyID="EUR">8859028</cbc:ValueAmount>
</cac:FinancialCapability>
</cac:QualifyingParty>
<cac:EconomicOperatorRole>
<cbc:RoleCode listID="EORoleType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">SCLE</cbc:RoleCode>
<cbc:RoleDescription languageID="ET">peapakkuja</cbc:RoleDescription>
</cac:EconomicOperatorRole>
<cac:Party>
<cbc:IndustryClassificationCode listID="EOIndustryClassificationCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">MEDIUM</cbc:IndustryClassificationCode>
<cac:PartyIdentification>
<cbc:ID schemeAgencyID="RHR">40003021907</cbc:ID>
</cac:PartyIdentification>
<cac:PartyName>
<cbc:Name>VAS "Elektroniskie sakari"</cbc:Name>
</cac:PartyName>
<cac:PostalAddress>
<cbc:CityName>Riga</cbc:CityName>
<cbc:PostalZone>LV-1010</cbc:PostalZone>
<cac:AddressLine>
<cbc:Line>5 Eksoprta street</cbc:Line>
</cac:AddressLine>
<cac:Country>
<cbc:IdentificationCode listID="CountryCodeIdentifier" listAgencyID="ISO" listVersionID="1.0">LV</cbc:IdentificationCode>
<cbc:Name>Läti</cbc:Name>
</cac:Country>
</cac:PostalAddress>
<cac:Contact>
<cbc:Name>Māris Aleksandrovs</cbc:Name>
<cbc:Telephone>+371 29168983</cbc:Telephone>
<cbc:ElectronicMail>
[email protected]</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:EconomicOperatorParty>
<cac:ProcurementProject>
<cbc:Name>Monitooringu tarkvata litsentsid</cbc:Name>
<cbc:Description languageID="ET">Monitooringu tarkvara litsentside soetus</cbc:Description>
<cbc:ProcurementTypeCode listID="ProjectType" listAgencyID="EU-COM-OP" listVersionID="1.0">SUPPLIES</cbc:ProcurementTypeCode>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>48900000-7</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>30200000-1</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>50312600-1</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>72220000-3</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>72222300-0</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
<cac:MainCommodityClassification>
<cbc:ItemClassificationCode>72267000-4</cbc:ItemClassificationCode>
</cac:MainCommodityClassification>
</cac:ProcurementProject>
<cac:ProcurementProjectLot>
<cbc:ID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ID>
</cac:ProcurementProjectLot>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6a21c421-5c1e-46f4-9762-116fbcd33097</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.CA_DATA.LOTS_SUBMISSION</cbc:CriterionTypeCode>
<cbc:Name>Hanke osad</cbc:Name>
<cbc:Description languageID="ET">Hanke osade kohta kehtivad järgnevad nõuded:</cbc:Description>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">03cff8d1-4d22-4435-82fa-d6361af84be6</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">847829aa-e70a-45e1-b4d3-e11c3ffaf7a0</cbc:ID>
<cbc:Description languageID="ET">Pakkumusi võib esitada</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CODE</cbc:ValueDataTypeCode>
<cbc:ExpectedCode listID="BidType" listAgencyID="EU-COM-OP" listVersionID="1.0">LOT_ALL</cbc:ExpectedCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dceddc28-0ac8-471b-b954-c376a862ea30</cbc:ID>
<cbc:Description languageID="ET">Maksimaalne osade arv, mille kohta võib pakkumusi esitada</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
<cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4b710530-abea-4ed0-b3fb-f324919c2d62</cbc:ID>
<cbc:Description languageID="ET">Maksimaalne osade arv, mille kohta võidakse sõlmida leping ühe pakkujaga</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUANTITY_INTEGER</cbc:ValueDataTypeCode>
<cbc:ExpectedValueNumeric>1</cbc:ExpectedValueNumeric>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">005eb9ed-1347-4ca3-bb29-9bc0db64e1ab</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.PARTICIPATION_IN_CRIMINAL_ORGANISATION</cbc:CriterionTypeCode>
<cbc:Name>Osalemine kuritegelikus organisatsioonis</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud kuritegelikus organisatsioonis osalemise eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud kuritegelikus ühenduses osalemise eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 1 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud kuritegelikus ühenduses osalemise eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8a42266c5fb24e32ff421942459d66ac-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f37dbede2411eb4a8fe4e65f2b4e0bc-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f37dbede2411eb4a8fe4e65f2b4e0bc-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f37dbede2411eb4a8fe4e65f2b4e0bc-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0f37dbede2411eb4a8fe4e65f2b4e0bc-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c0750b31f837dc0a061f4b08cfbff932-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fcf54563bb12424d74c6eab13b3bff3e-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7498d35783aaf5b55a3d4b5b1f7995d2-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">03a11607d1053d3bf94f29fdae2d8519-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c27b7c4e-c837-4529-b867-ed55ce639db5</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.CORRUPTION</cbc:CriterionTypeCode>
<cbc:Name>Korruptsioon</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud korruptsiooni eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt? See kõrvalejätmise alus hõlmab ka korruptsiooni avaliku sektori hankija (võrgustiku sektori hankija) või ettevõtja riigi õiguses sätestatud määratluses.</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud aususe kohustuse rikkumise või korruptiivse teo eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud aususe kohustuse rikkumise või korruptiivse teo eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">94bafa958a57a2f5fa7af1f5c03b1e54-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e02a375844ffeed61bf8e900d79fdac-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e02a375844ffeed61bf8e900d79fdac-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e02a375844ffeed61bf8e900d79fdac-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e02a375844ffeed61bf8e900d79fdac-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">349df04fcc0fc67f069277acb8c9dbc6-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f40dcf93e5a4c45cbe614d6e548ef291-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">07df47ce65627207b1b045f7a91524fe-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2f83fb0e402357838fb6473a22095ad0-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">297d2323-3ede-424e-94bc-a91561e6f320</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.FRAUD</cbc:CriterionTypeCode>
<cbc:Name>Pettus</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud kelmuse eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud kelmuse eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud kelmuse eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">664e928718e7857cd0a1f6f4ce5d5e78-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9aecbda897b5af788719bf9785379d9a-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9aecbda897b5af788719bf9785379d9a-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9aecbda897b5af788719bf9785379d9a-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9aecbda897b5af788719bf9785379d9a-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">339e6fdf2845953de42156e24c396a3c-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0ddc4872e3fcfe77a5981c65b9277fb6-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e63f6d15c35d9de0ca7ce2f47548ba6-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">465acd61bc65f51b8be110b516ebe3c0-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d486fb70-86b3-4e75-97f2-0d71b5697c7d</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.TERRORIST_OFFENCES</cbc:CriterionTypeCode>
<cbc:Name>Terroriakti toimepanek või terroristliku tegevusega seotud õigusrikkumised</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud terroriakti toimepaneku või terroristliku tegevusega seotud õigusrikkumiste eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud terroriakti toimepaneku või muu terroristliku tegevusega seotud kuriteo või sellele kihutamise, kaasaaitamise või selle katse eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud terroriakti toimepaneku või muu terroristliku tegevusega seotud kuriteo või sellele kihutamise, kaasaaitamise või selle katse eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">85d57d4b7fa89f637f91d9d8b027405c-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d0a0120138d89be004580e67f236998a-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d0a0120138d89be004580e67f236998a-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d0a0120138d89be004580e67f236998a-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d0a0120138d89be004580e67f236998a-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0370883c347256e5a0135b8a84fd760b-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">17aedd2261f7feab717cb32c3b5aeb29-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2d902c8235ebefb9296053f5363306ef-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fa2df2255415653c837e2025a50cfb0a-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">47112079-6fec-47a3-988f-e561668c3aef</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.MONEY_LAUNDERING</cbc:CriterionTypeCode>
<cbc:Name>Rahapesu või terrorismi rahastamine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud rahapesu või terrorismi rahastamise eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud rahapesualase süüteo või terrorismi rahastamise eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 1 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud rahapesualase süüteo või terrorismi rahastamise eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2d056d00bb0a19f4805cac08dcf7a67d-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52cacf5f0daca4e3430d7251c0c7da1d-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52cacf5f0daca4e3430d7251c0c7da1d-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52cacf5f0daca4e3430d7251c0c7da1d-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52cacf5f0daca4e3430d7251c0c7da1d-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1c90295ec86cb799a8c1232d8e420c01-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c8178fa1450e3748f0725690078c2c62-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">db96b332d0df0d7ce653977d80137c3e-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e9226efb7961e6beeb7ab8e273e95028-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d789d01a-fe03-4ccd-9898-73f9cfa080d1</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONVICTIONS.CHILD_LABOUR-HUMAN_TRAFFICKING</cbc:CriterionTypeCode>
<cbc:Name>Laste tööjõu kasutamine ja muud inimkaubanduse vormid</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja ise või tema haldus-, juht- või järelevalveorgani liige või isik, kellel on volitused seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on lõpliku süüdimõistva kohtuotsusega süüdi mõistetud laste tööjõu kasutamise või muude inimkaubanduse vormide eest kõige rohkem viimase viie aasta jooksul või kehtib süüdimõistvas kohtuotsuses sätestatud kõrvalejäämise kohustus endiselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 3 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud laste tööjõu ebaseadusliku kasutamise või inimkaubandusega seotud teo eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 3 ja lg 2 "keda või kelle haldus-, juhtimis- või järelevalveorgani liiget, prokuristi või muud isikut, kellel on volitus seda ettevõtjat esindada, tema nimel otsuseid teha või teda kontrollida, on karistatud laste tööjõu ebaseadusliku kasutamise või inimkaubandusega seotud teo eest". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c637c0c-7703-4389-ba52-02997a055bd7</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c97dab162756613157478a51204f9c86-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">83022e29557557a368016539d73d38bb-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">83022e29557557a368016539d73d38bb-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Põhjus</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">83022e29557557a368016539d73d38bb-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Kes süüdi mõisteti?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">83022e29557557a368016539d73d38bb-1.1.4</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4978772-3126-4ded-bc30-f50da8c3a038</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ed85f82954382b639f1eaf50017a064e-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c19c11d54efe2c12b6e51dba2a083519-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">036d42bf0ba523328b09842e95e5a483-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">49fbdd637d5d0872abb6062ade6f09e8-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b61bbeb7-690e-4a40-bc68-d6d4ecfaa3d4</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONTRIBUTIONS.PAYMENT_OF_TAXES</cbc:CriterionTypeCode>
<cbc:Name>Maksude tasumine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on rikkunud oma maksude tasumise kohustusi nii asukohariigis kui ka avaliku sektori hankija või võrgustiku sektori hankija liikmesriigis, kui see erineb asukohariigist?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 4 „kellel on riikliku maksu, makse või keskkonnatasu maksuvõlg maksukorralduse seaduse tähenduses või maksuvõlg /…/ tema asukohariigi õigusaktide kohaselt“</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 4 „kellel on riikliku maksu, makse või keskkonnatasu maksuvõlg maksukorralduse seaduse tähenduses või maksuvõlg /…/ tema asukohariigi õigusaktide kohaselt“</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">591b6f30ce0753042d115e2cc81bf72f-1.1</cbc:ID>
<cbc:Description languageID="ET">Piirmäär</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</cbc:ValueDataTypeCode>
<cbc:ExpectedAmount currencyID="EUR">0</cbc:ExpectedAmount>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">591b6f30ce0753042d115e2cc81bf72f-1.2</cbc:ID>
<cbc:Description languageID="ET">Lisainfo</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
<cbc:ExpectedDescription>Maksukorralduse seaduse kohaselt ei väljasta maksuhaldur maksuvõlgade tõendit juhul,kui maksukohustuslasel olev kõikide sama maksuhalduri hallatavate maksude võlg, arvestamata haldusaktiga kindlaksmääramata intressi, on väiksem kui 100 eurot või kui maksuvõla tasumine on ajatatud. Välismaise ettevõtja puhul väljastatakse maksuvõlgade tõend tema asukohariigi õigusaktide kohaselt.</cbc:ExpectedDescription>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">098fd3cc-466e-4233-af1a-affe09471bce</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d2b922c3afdd52c13d295e3333eafa67-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f8499787-f9f8-4355-95e2-9784426f4d7b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6e0837518cbfb4371e9e83fccd266ab3-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Asjaomane riik või liikmesriik</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CODE_COUNTRY</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6e0837518cbfb4371e9e83fccd266ab3-1.1.1.2</cbc:ID>
<cbc:Description languageID="ET">Asjaomane summa</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c2aec9f-4876-4c33-89e6-2ab6d6cf5d02</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3850a15a4a07b298d461d08e23b39837-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas see kohustuste rikkumine on tuvastatud muude vahenditega kui kohtu- või haldusotsusega?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">80633323-a7b6-4206-9728-e4534eaad8b2</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">99537009354605a4395aa686ead557a2-1.1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage kasutatud vahendeid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">536417dc-8130-4981-85c5-fceba5541c58</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONFALSE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">113999e18124b44c72e77ada9dd4b8a8-1.1.1.1.2.1</cbc:ID>
<cbc:Description languageID="ET">Kui kohustuste rikkumine tuvastati kohtu- või haldusotsusega, märkige, kas see otsus on lõplik ja siduv.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8aaac22d-1b59-442e-9210-a6e70ec05962</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fa9ea46b75af4d23c4e5dc8d8fc11224-1.1.1.1.2.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fa9ea46b75af4d23c4e5dc8d8fc11224-1.1.1.1.2.1.2</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a49e6e25-0059-47da-9397-72c2db5fd5b1</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">599ae929bd55fd657520932db9f31bc6-1.1.1.1.3.1</cbc:ID>
<cbc:Description languageID="ET">Kas ettevõtja on täitnud oma kohustused tasumisele kuuluvate maksude või sotsiaalkindlustusmaksete tasumisega või siduva kokkuleppe sõlmimisega tasumisele kuuluvate maksude või sotsiaalkindlustusmaksete, sealhulgas vajaduse korral kogunenud intresside ja viiviste tasumise kohta?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">42a44eb9-b8c9-4a67-8776-e77fc5356efe</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7bc8a3613be0efa08f1a1e6aeb2de593-1.1.1.1.3.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e5f319d2c9fe7a95fde7de1281fac693-1.2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">671f28fb772390c67435047894df84da-1.2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7d85e333-bbab-49c0-be8d-c36d71a72f5e</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONTRIBUTIONS.PAYMENT_OF_SOCIAL_SECURITY</cbc:CriterionTypeCode>
<cbc:Name>Sotsiaalkindlustusmaksete tasumine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on rikkunud oma sotsiaalkindlustusmaksete tasumise kohustusi nii asukohariigis kui ka avaliku sektori hankija või võrgustiku sektori hankija liikmesriigis, kui see erineb asukohariigist?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 1 p 4 „kellel on riikliku /…/ makse /…/ maksuvõlg maksukorralduse seaduse tähenduses või sotsiaalkindlustusemaksete võlg tema asukohariigi õigusaktide kohaselt</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 1 p 4 „kellel on riikliku /…/ makse /…/ maksuvõlg maksukorralduse seaduse tähenduses või sotsiaalkindlustusemaksete võlg tema asukohariigi õigusaktide kohaselt</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">53c9aad8-dc80-48f8-85d9-755c2aab8e95</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">44ba5e05d88564516899a6caa5014f45-1.1</cbc:ID>
<cbc:Description languageID="ET">Piirmäär</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</cbc:ValueDataTypeCode>
<cbc:ExpectedAmount currencyID="EUR">0</cbc:ExpectedAmount>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">44ba5e05d88564516899a6caa5014f45-1.2</cbc:ID>
<cbc:Description languageID="ET">Lisainfo</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">REQUIREMENT</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
<cbc:ExpectedDescription>Maksukorralduse seaduse kohaselt ei väljasta maksuhaldur maksuvõlgade tõendit juhul,kui maksukohustuslasel olev kõikide sama maksuhalduri hallatavate maksude võlg, arvestamata haldusaktiga kindlaksmääramata intressi, on väiksem kui 100 eurot või kui maksuvõla tasumine on ajatatud. Välismaise ettevõtja puhul väljastatakse maksuvõlgade tõend tema asukohariigi õigusaktide kohaselt.</cbc:ExpectedDescription>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">098fd3cc-466e-4233-af1a-affe09471bce</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a798f5c4df3b296808ec367318de88e5-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f8499787-f9f8-4355-95e2-9784426f4d7b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5dbfb3a91a6e078f0443d416b526bd2b-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Asjaomane riik või liikmesriik</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CODE_COUNTRY</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5dbfb3a91a6e078f0443d416b526bd2b-1.1.1.2</cbc:ID>
<cbc:Description languageID="ET">Asjaomane summa</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">AMOUNT</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7c2aec9f-4876-4c33-89e6-2ab6d6cf5d02</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8546e692e09bc12544954a34bac569e8-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas see kohustuste rikkumine on tuvastatud muude vahenditega kui kohtu- või haldusotsusega?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">80633323-a7b6-4206-9728-e4534eaad8b2</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8464a199433494573513c685259522d6-1.1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage kasutatud vahendeid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">536417dc-8130-4981-85c5-fceba5541c58</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONFALSE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f31a7e715511387237a9a0e9d9367cab-1.1.1.1.2.1</cbc:ID>
<cbc:Description languageID="ET">Kui kohustuste rikkumine tuvastati kohtu- või haldusotsusega, märkige, kas see otsus on lõplik ja siduv.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8aaac22d-1b59-442e-9210-a6e70ec05962</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">16479b3ac96f8f8b5399c4ad36a10881-1.1.1.1.2.1.1</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistmise kuupäev</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DATE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">16479b3ac96f8f8b5399c4ad36a10881-1.1.1.1.2.1.2</cbc:ID>
<cbc:Description languageID="ET">Süüdimõistvas otsuses sõnaselgelt esitatud kõrvalejätmise kestus.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERIOD</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a49e6e25-0059-47da-9397-72c2db5fd5b1</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">92ff80c7de4626861254e250bbe19ea8-1.1.1.1.3.1</cbc:ID>
<cbc:Description languageID="ET">Kas ettevõtja on täitnud oma kohustused tasumisele kuuluvate maksude või sotsiaalkindlustusmaksete tasumisega või siduva kokkuleppe sõlmimisega tasumisele kuuluvate maksude või sotsiaalkindlustusmaksete, sealhulgas vajaduse korral kogunenud intresside ja viiviste tasumise kohta?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">42a44eb9-b8c9-4a67-8776-e77fc5356efe</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">81d96d9e2996738bfa585ef23cd27356-1.1.1.1.3.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">06238c8b82047ad5f649f64687cfed04-1.2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">29eb41abb32b80f2eaee7c1119ad2de7-1.2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a80ddb62-d25b-4e4e-ae22-3968460dc0a9</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.SOCIAL.ENVIRONMENTAL_LAW</cbc:CriterionTypeCode>
<cbc:Name>Keskkonnaõiguse valdkonnas kohaldatavate kohustuste täitmata jätmine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on enda teada rikkunud keskkonnaõiguse valdkonnas kohaldatavaid kohustusi?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid keskkonnaõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid keskkonnaõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">976b5acb-c00f-46ca-8f83-5ce6abfdfe43</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d71f2afecb0aec233e2f178327ac18d1-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">64a2102c-4af1-4ecb-97b3-0c41907ec0f6</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1ff6a9b11f304e371d19a71696b40692-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3b7d89cfcf10f74aa676e483995c16fd-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0bdd2a3f426dd4905973701b1a1f6d92-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">795818013abcd8fa0b614f8ab21ae90b-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4013da9224d17002f76e00d9412b180c-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a261a395-ed17-4939-9c75-b9ff1109ca6e</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.SOCIAL.SOCIAL_LAW</cbc:CriterionTypeCode>
<cbc:Name>Sotsiaalõiguse valdkonnas kohaldatavate kohustuste täitmata jätmine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on enda teada rikkunud sotsiaalõiguse valdkonnas kohaldatavaid kohustusi?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid sotsiaalõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid sotsiaalõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">976b5acb-c00f-46ca-8f83-5ce6abfdfe43</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dced61ca05d4b6509ba11c848f7efc58-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">64a2102c-4af1-4ecb-97b3-0c41907ec0f6</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">17fe0dcaaf85a079d239d6fafa8dc1d3-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">686813b025a645cc4d0b1d7fcb0ba9f6-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">39332400589476c7707f21c8e0c2b54e-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0cc2de07ff96b1169913b554d5735478-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a682002a8a80a80d183259605439ec4d-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a34b70d6-c43d-4726-9a88-8e2b438424bf</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.SOCIAL.LABOUR_LAW</cbc:CriterionTypeCode>
<cbc:Name>Tööõiguse valdkonnas kohaldatavate kohustuste täitmata jätmine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on enda teada rikkunud tööõiguse valdkonnas kohaldatavaid kohustusi?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid tööõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 2 „kes on rikkunud õigusaktidest või kollektiivlepingust tulenevaid tööõiguse valdkonnas kohaldatavaid kohustusi“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">976b5acb-c00f-46ca-8f83-5ce6abfdfe43</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">db41347baa09a8c0a5cae4ca70927e9d-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">64a2102c-4af1-4ecb-97b3-0c41907ec0f6</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bdc15f1fd5cb7d2fdf337938f94532a0-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ffdc8a5b7494a18912169cfd794a75e9-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">474e8f18919316713aabbf2229006484-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ece600a9097944288e11a1b6699fb6bb-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5cd1931d64fae933e71cf960ece3e7f5-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d3732c09-7d62-4edc-a172-241da6636e7c</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.BANKRUPTCY</cbc:CriterionTypeCode>
<cbc:Name>Pankrot</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on pankrotis?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kes on pankrotis, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kes on pankrotis, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">056f8a7d83e7385f1028c51aa00aa34b-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">84295052d2d27a0dcbd585edbb05be50-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">84295052d2d27a0dcbd585edbb05be50-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">de8e758fa6893cfd64668285fa226847-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">224dd6120f91e22d17b778928fea1886-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">396f288a-e267-4c20-851a-ed4f7498f137</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.INSOLVENCY</cbc:CriterionTypeCode>
<cbc:Name>Maksejõuetus</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja suhtes on algatatud maksejõuetus- või likvideerimismenetlus?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kes on likvideerimisel või kelle suhtes on algatatud pankrotimenetlus, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kes on likvideerimisel või kelle suhtes on algatatud pankrotimenetlus, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8d66094d6187fbeb250bc18bf2899a37-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4358a8a9070a246e426e3427d85d0711-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4358a8a9070a246e426e3427d85d0711-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8bc3c952560f6ad78eb65c5373517e78-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4e2ff0e2165c44a6eebfb787e2860295-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">68918c7a-f5bc-4a1a-a62f-ad8983600d48</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.CREDITORS_ARRANGEMENT</cbc:CriterionTypeCode>
<cbc:Name>Kokkulepe võlausaldajatega</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on sõlminud kokkuleppe võlausaldajatega?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5a10919abd31fa6f8738ed8e2bfc2c30-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2c7ffedaa22412614e54b2c73f32ba1f-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2c7ffedaa22412614e54b2c73f32ba1f-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0da3567bd1587969627a71cc637bf3ff-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">24bfa7ce46068d5a8d31e88dde804e66-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">daffa2a9-9f8f-4568-8be8-7b8bf306d096</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.BANKRUPTCY_ANALOGOUS</cbc:CriterionTypeCode>
<cbc:Name>Siseriikliku õiguse kohane samalaadne olukord, näiteks pankrot</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on siseriiklike õigusnormide alusel toimuva samalaadse menetluse tõttu samalaadses olukorras?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt“, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt“, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">476a15b9d9f85459a63cadc3e3b73460-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fd166074bd97f8be871238ee0a3472df-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fd166074bd97f8be871238ee0a3472df-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">699c2f5f4ae65e623002d40bb3ee7ee9-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bd91129f6a3774fbe6d0215a59cf966c-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8fda202a-0c37-41bb-9d7d-de3f49edbfcb</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.LIQUIDATOR_ADMINISTERED</cbc:CriterionTypeCode>
<cbc:Name>Vara haldab likvideerija</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja vara haldab likvideerija või kohus?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kes on pankrotis, likvideerimisel või kelle suhtes on algatatud pankrotimenetlus või kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kes on pankrotis, likvideerimisel või kelle suhtes on algatatud pankrotimenetlus või kes on muus sellesarnases olukorras tema asukohamaa õigusaktide kohaselt, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67b088a852a32478afb7cc8fd19d3fb5-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">896385ffd24ec34f1c414abfc97e0541-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">896385ffd24ec34f1c414abfc97e0541-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3c0b4f12a3e8a3f4f4023932e10ed8a9-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">116e9a32beda1ed6e51a9f70a9b5350b-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">166536e2-77f7-455c-b018-70582474e4f6</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.BUSINESS.ACTIVITIES_SUSPENDED</cbc:CriterionTypeCode>
<cbc:Name>Äritegevus on peatatud</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja äritegevus on peatatud?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 3 „kelle äritegevus on peatatud, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 3 „kelle äritegevus on peatatud, välja arvatud asjade ostmisel RHS § 49 lõikes 4 sätestatud juhul ja tingimustel“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d91c11a1-f19e-4b83-8ade-c4be2bf00555</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b1f1dc7c01597a65463e2c18253f83c0-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aeef523b-c8fc-4dba-9c34-03e34812567b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e467bed89b7031d88fb3001fdc28ad5a-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e467bed89b7031d88fb3001fdc28ad5a-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Märkige põhjused, miks lepingu täitmine on sellest hoolimata võimalik. Seda teavet ei ole tarvis esitada, kui ettevõtja kõrvalejätmine on kohaldatava siseriikliku õiguse alusel muudetud konkreetsel juhul kohustuslikuks ja puudub võimalus teha erandit, isegi kui ettevõtja suudab lepingut täita.</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">962c3b6715f062c66fb25afbefe1360a-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ea6187efebc1a1857977d16abc945fc2-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">514d3fde-1e3e-4dcd-b02a-9f984d5bbda3</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.MISCONDUCT.MC_PROFESSIONAL</cbc:CriterionTypeCode>
<cbc:Name>Süüdi ametialaste käitumisreeglite olulises rikkumises</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on süüdi ametialaste käitumisreeglite olulises rikkumises? Vt siseriiklikud õigusaktid, asjaomane teade või hankedokumendid, kui see on asjakohane.</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 4 „kes on raskelt eksinud ametialaste käitumisreeglite vastu ja see muudab tema aususe küsitavaks“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 4 „kes on raskelt eksinud ametialaste käitumisreeglite vastu ja see muudab tema aususe küsitavaks“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e84b04d9cced34ecb51466b1045b0324-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2cbcf978-765c-40aa-996b-b1d082485cef</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7ab1f28d8861d49aa1c1dbfc1997d3b0-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8bfe32ac76744c6049299eb020f85ef6-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6744a0ed579ff20ba20322faee3ee894-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1ee9e1dfca8300341b206644744d8fe0-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5003c2b1f82b8e2b422f49b35ce79fff-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">56d13e3d-76e8-4f23-8af6-13e60a2ee356</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.MISCONDUCT.MARKET_DISTORTION</cbc:CriterionTypeCode>
<cbc:Name>Konkurentsi moonutamise eesmärgil teiste ettevõtjatega sõlmitud kokkulepped</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on teiste ettevõtjatega sõlminud kokkuleppeid, mille eesmärk on moonutada konkurentsi?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 5 „konkurentsi kahjustava kokkuleppe, ettevõtjate ühenduse otsuse või kooskõlastatud tegevuse tõttu“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 5 „konkurentsi kahjustava kokkuleppe, ettevõtjate ühenduse otsuse või kooskõlastatud tegevuse tõttu“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8486f521e63eee007f5f05abbddcaae9-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2cbcf978-765c-40aa-996b-b1d082485cef</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">72c96332968ed78a89a12a5c216709a0-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f9f09f7-f701-432c-9fdc-c22c124a74c9</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a52c3fb0a59b96a1caff33f76f2f8810-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">78c7691916ecc30f63e0ac9736967fb5-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">03299642dcd03d0b74e6fcec1d941d60-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6d4c134c796c2ea86c7c641ce0c2b5bd-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b1b5ac18-f393-4280-9659-1367943c1a2e</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.PROCEDURE_PARTICIPATION</cbc:CriterionTypeCode>
<cbc:Name>Hankemenetluses osalemisega kaasnev huvide konflikt</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on teadlik hankemenetluses osalemisega kaasnevast mis tahes huvide konfliktist siseriikliku õiguse, asjakohase teatise või hankedokumentide kohaselt?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 6 „kui huvide konflikti ei ole muude vahenditega võimalik vältida“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 6 „kui huvide konflikti ei ole muude vahenditega võimalik vältida“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">762dc3a323dc6704cf8944168406e22a-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">780c0fd2e78afa0975228976830a65a3-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">354daa93c73508e8eceb357ca3a9475a-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d67d6ca6bf8276440a77447c332e1972-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">61874050-5130-4f1c-a174-720939c7b483</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.PROCEDURE_PREPARATION</cbc:CriterionTypeCode>
<cbc:Name>Otsene või kaudne osalemine käesoleva hankemenetluse ettevalmistamisel</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja või temaga seotud ettevõtja on nõustanud avaliku sektori hankijat või võrgustiku sektori hankijat hankemenetluse ettevalmistamisel või olnud muul viisil seotud hankemenetluse ettevalmistamisega?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 7 „kelle pakkumuse või taotluse koostamisel on osalenud isik, kes on osalenud sama riigihanke ettevalmistamisel või on muul viisil hankijaga seotud, ja sellele isikule seetõttu teadaolev info annab talle eelise teiste riigihankes osalejate eest ning sellest tingitud konkurentsi moonutamist ei ole muude vahendistega võimalik vältida“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 7 „kelle pakkumuse või taotluse koostamisel on osalenud isik, kes on osalenud sama riigihanke ettevalmistamisel või on muul viisil hankijaga seotud, ja sellele isikule seetõttu teadaolev info annab talle eelise teiste riigihankes osalejate eest ning sellest tingitud konkurentsi moonutamist ei ole muude vahendistega võimalik vältida“. Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a3e8a6e67e44334c5f2afdd4e7562fa7-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0061708149ea470bdbbabfe4419df655-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a8999a4d1b62c66814d34ecfebb4c1ae-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f841acfbfb1d4890cf6a40e5f4ac215e-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3293e92b-7f3e-42f1-bee6-a7641bb04251</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.EARLY_TERMINATION</cbc:CriterionTypeCode>
<cbc:Name>Ennetähtaegne lõpetamine, kahjutasu või võrreldavad sanktsioonid</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on kogenud, et varasem riigihankeleping või võrgustiku sektori hankijaga sõlmitud varasem hankeleping või varasem kontsessioonileping on lõpetatud enneaegselt, või on määratud kahjutasu või sellega võrreldavad sanktsioonid seoses kõnealuse varasema lepinguga?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 8 „kes on oluliselt või pidevalt rikkunud eelnevalt sõlmitud hankelepingu olulist tingimust või hankelepingute olulisi tingimusi nii, et rikkumise tulemusena on lepingust taganetud või leping üles öeldud, hinda alandatud, hüvitatud kahju või makstud leppetrahvi". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud. Alates 1.09.2017 alustatud hangete tulemusena sõlmitud riigihankelepingute kohta leiab infot riigihangete registrist.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 8 „kes on oluliselt või pidevalt rikkunud eelnevalt sõlmitud hankelepingu olulist tingimust või hankelepingute olulisi tingimusi nii, et rikkumise tulemusena on lepingust taganetud või leping üles öeldud, hinda alandatud, hüvitatud kahju või makstud leppetrahvi". Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud. Alates 1.09.2017 alustatud hangete tulemusena sõlmitud riigihankelepingute kohta leiab infot riigihangete registrist.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67362ec7-cec3-4cb8-a38e-5d7a2a31e6d8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">88f454ed56cf088fa5cd0eb926751769-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">73f0fe4c-4ed9-4343-8096-d898cf200146</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3a97fb9147ccaa40e15fdea13f565e3f-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">20c5361b-7599-4ee6-b030-7f8323174d1e</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9e99ebf957680af144d88b6c9fa3f90c-1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kas olete võtnud meetmeid, et tõendada oma usaldusväärsust („Self-Cleaning”)?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">74e6c7b4-757b-4b40-ada6-fad6a997c310</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fe85fa176b7dbacd117f0d19f7611fb5-1.1.1.1.1</cbc:ID>
<cbc:Description languageID="ET">Kirjeldage neid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">24f26f42d53a913959ce42027dc14bb1-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">398000286b23baf64b55b4bc0665b84d-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">696a75b2-6107-428f-8b74-82affb67e184</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.CONFLICT_OF_INTEREST.MISINTERPRETATION</cbc:CriterionTypeCode>
<cbc:Name>Süüdi valeandmete esitamises, on jätnud teavet esitamata, ei suuda nõutud dokumente esitada, hankinud käesoleva menetluse kohta konfidentsiaalset teavet</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on olnud ühes järgmistest olukordadest:
a) ta on kõrvalejätmise aluste puudumise või valikukriteeriumide täitmise kontrollimiseks nõutava teabe esitamisel esitanud valeandmeid;
b) ta on jätnud sellist teavet esitamata;
c) ta ei ole esitanud viivitamata avaliku sektori hankija või võrgustiku sektori hankija nõutud täiendavad dokumendid, ja
d) ta on tegutsenud eesmärgiga mõjutada lubamatul viisil avaliku sektori hankija või võrgustiku sektori hankija otsustusprotsessi, et saada konfidentsiaalseid andmeid, mis võivad anda talle põhjendamatu eelise hankemenetluses, või hooletusest esitanud eksitavat teavet, mis võib oluliselt mõjutada kõrvalejätmise, valiku või lepingu hindamise kohta tehtavaid otsuseid?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">RHS § 95 lg 4 p 9 „kes on esitanud valeandmeid käesolevas paragrahvis sätestatud või RHS §-des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele vastavuse kohta“;
RHS § 95 lg 4 p 9 „kes on jätnud andmed käesolevas paragrahvis sätestatud või käesoleva seaduse §-des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele vastavuse kohta esitamata“;
RHS § 95 lg 4 p 9 „kes on jätnud käesoleva seaduse § 104 lõigete 7 ja 8 alusel hankija nõutud täiendavad dokumendid esitamata“;
RHS § 95 lg 4 p 10 „kes on tegutsenud eesmärgiga mõjutada hankijat või esitanud hooletusest eksitavat teavet, mis on võinud mõjutada hankija otsuseid riigihankes, või on tegutsenud eesmärgiga saada konfidentsiaalset teavet, mis on võinud anda talle põhjendamatu eelise teiste riigihankes osalejate ees“.
Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Title>
<cbc:Description languageID="ET">RHS § 95 lg 4 p 9 „kes on esitanud valeandmeid käesolevas paragrahvis sätestatud või RHS §-des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele vastavuse kohta“;
RHS § 95 lg 4 p 9 „kes on jätnud andmed käesolevas paragrahvis sätestatud või käesoleva seaduse §-des 98-101 sätestatu alusel hankija kehtestatud kvalifitseerimise tingimustele vastavuse kohta esitamata“;
RHS § 95 lg 4 p 9 „kes on jätnud käesoleva seaduse § 104 lõigete 7 ja 8 alusel hankija nõutud täiendavad dokumendid esitamata“;
RHS § 95 lg 4 p 10 „kes on tegutsenud eesmärgiga mõjutada hankijat või esitanud hooletusest eksitavat teavet, mis on võinud mõjutada hankija otsuseid riigihankes, või on tegutsenud eesmärgiga saada konfidentsiaalset teavet, mis on võinud anda talle põhjendamatu eelise teiste riigihankes osalejate ees“.
Kui hankemenetlusest kõrvaldamise alus esineb, võib ettevõtja soovi korral esitada tõendeid selle kohta, et ta on võtnud meetmeid oma usaldusväärsuse taastamiseks. Heastamise võimalus on ettevõtjal juhul, kui tegemist on rahvusvahelist piirmäära ületava hankega või hankija on selle hanke alusdokumentides ette näinud.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f3a6836d-2de2-4cd1-81ca-fb06178d05c5</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e5651c9fcebc0f9e0b6c2adea0f6ae0a-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">797467a9cd053779f8189cc09b53cd15-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8906d536a55e83e14c0fa8af7e18529a-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2043338f-a38a-490b-b3ec-2607cb25a017</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.SHELTERED_WORKSHOP</cbc:CriterionTypeCode>
<cbc:Name>Ettevõtja on kaitstud töökoht</cbc:Name>
<cbc:Description languageID="ET">Ainult reserveeritud hangete puhul: kas ettevõtja puhul on tegemist kaitstud töökohaga, sotsiaalse ettevõttega või ta täidab lepingut kaitstud tööhõive programmide raames?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6febbe4a-e715-427c-a2b1-19cfabadaef0</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">916ab5ce762c49fbffd04765384d9195-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a5e33369-e2b5-45f7-9969-ddb1c3ae17c8</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4ce62b05d3766bb39de778d0137f6854-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Milline on puudega või ebasoodsas olukorras olevate töötajate osakaal?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">PERCENTAGE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4ce62b05d3766bb39de778d0137f6854-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Kui seda on nõutud, täpsustage, millisesse puudega või ebasoodsas olukorras olevate töötajate kategooriasse või kategooriatesse asjaomased töötajad kuuluvad?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8511a8ee6a5fe826b0c1c6759cc36403-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">223fa7313710bdb119eb9d1350d79d32-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9b19e869-6c89-4cc4-bd6c-ac9ca8602165</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.REGISTERED_IN_OFFICIAL_LIST</cbc:CriterionTypeCode>
<cbc:Name>Ettevõtja on kantud tunnustatud ettevõtjate ametlikku nimekirja</cbc:Name>
<cbc:Description languageID="ET">Kui see on asjakohane, siis kas ettevõtja on kantud tunnustatud ettevõtjate ametlikku nimekirja või kas tal on olemas samaväärne tõend (nt riikliku (eel)kvalifitseerimissüsteemi alusel)?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">64162276-7014-408f-a9af-080426bfe1fd</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9ec5f8c89b9cfb663ec773102d3d63ea-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9026e403-3eb6-4705-a9e9-e21a1efc867d</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f2d7fc19dc0a371b177d7d52cc641649-1.1.1</cbc:ID>
<cbc:Description languageID="ET">a) Vajaduse korral märkige asjakohane registreerimis- või sertifitseerimisnumber:</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f2d7fc19dc0a371b177d7d52cc641649-1.1.2</cbc:ID>
<cbc:Description languageID="ET">c) Viited, millele registreerimine või sertifitseerimine tugineb ja vajaduse korral ametlikus nimekirjas omistatud klassifikatsioon:</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f2d7fc19dc0a371b177d7d52cc641649-1.1.3</cbc:ID>
<cbc:Description languageID="ET">d) Kas registreerimine või sertifitseerimine hõlmab kõiki nõutud valikukriteeriume?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8474ff05cd1affe49977b11837ffc832-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7f182a877442795f199f19e30c2f4cb1-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ee51100f-8e3e-40c9-8f8b-57d5a15be1f2</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.TOGETHER_WITH_OTHERS</cbc:CriterionTypeCode>
<cbc:Name>Hankemenetluses koos osalevad ettevõtjad</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja osaleb hankemenetluses koos teistega?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d939f2c6-ba25-4dc4-889c-11d1853add19</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b084ef65294946d13ab11527833322a8-1.1</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja nimi</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b084ef65294946d13ab11527833322a8-1.2</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja ID</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b084ef65294946d13ab11527833322a8-1.3</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja roll</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67abefe9c6becc08ff7027f880cf8e58-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">431420fc0327c7dfc0c8e338db661a4f-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0d62c6ed-f074-4fcf-8e9f-f691351d52ad</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.RELIES_ON_OTHER_CAPACITIES</cbc:CriterionTypeCode>
<cbc:Name>Teave teiste üksuste suutlikkusele toetumise kohta</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja toetub teiste üksuste suutlikkusele, et täita esitatud valikukriteeriumid ning eeskirjad (kui neid on)?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f6b858925af7cad9dee2869edd4ff60c-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">50e9a74e-969e-4d79-8e19-8af71cb7c54a</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fe96fce0e7baaa249d8559a7af0f3212-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja nimi</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fe96fce0e7baaa249d8559a7af0f3212-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja ID</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fe96fce0e7baaa249d8559a7af0f3212-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja roll</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9715cfa07bc54f829aa383179c605554-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6833f9ee60ab7d82b44c62c2da533ff0-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">72c0c4b1-ca50-4667-9487-461f3eed4ed7</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.SUBCONTRACTS_WITH_THIRD_PARTIES</cbc:CriterionTypeCode>
<cbc:Name>Teave nende allhankijate kohta, kelle näitajatele ettevõtja ei tugine</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja kavatseb sõlmida lepingu mis tahes osa kohta allhanke kolmanda isikuga?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bf6b522598fc8784858a6712851f7fa2-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">50e9a74e-969e-4d79-8e19-8af71cb7c54a</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f7918353a4a25b03e4d1ad59de641e39-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja nimi</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f7918353a4a25b03e4d1ad59de641e39-1.1.2</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja ID</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f7918353a4a25b03e4d1ad59de641e39-1.1.3</cbc:ID>
<cbc:Description languageID="ET">Ettevõtja roll</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">DESCRIPTION</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6c3dc3029e6128b5025c2727085b8a67-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9895d63fec57f19d41d599f8db9cdf91-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8b9700b7-b13c-41e6-a220-6bbf8d5fab31</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.LOTS_TENDERED</cbc:CriterionTypeCode>
<cbc:Name>Hanke osad</cbc:Name>
<cbc:Description languageID="ET">Hanke osad, mille kohta ettevõtja soovib pakkumuse esitada</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a8f39f21f1a4f61006839d17c48d58c3-1.1</cbc:ID>
<cbc:Description languageID="ET">Hanke osa number</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">130b632716c48f4b7f69f61016f3ef5c-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">557c987e3ce67681b7c884af3c38f3f4-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5a8dea31-5db9-4e03-862b-07810aa6a7fd</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.OTHER.EO_DATA.CONTRIBUTIONS_CERTIFICATES</cbc:CriterionTypeCode>
<cbc:Name>Ettevõtja kinnitused maksude tasumise kohta</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja saab esitada tõendi sotsiaalkindlustusmaksete ja maksude tasumise kohta või esitada teabe, mis võimaldaks avaliku sektori hankijal või võrgustiku sektori hankijal saada sellise teabe otse ükskõik millise liikmesriigi tasuta andmebaasist?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET"/>
<cbc:Description languageID="ET"/>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">289f39b3-2a15-421a-8050-a29858031f35</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">642c63e9ae63a12207197f19f3d6a53e-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e2eb7a88e019a3caf911d6a20865d056-2.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">560e5e7ef0d3d163430768039c402848-2.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterion>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">63adb07d-db1b-4ef0-a14e-a99785cf8cf6</cbc:ID>
<cbc:CriterionTypeCode listID="CriteriaTypeCode" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CRITERION.EXCLUSION.NATIONAL.OTHER</cbc:CriterionTypeCode>
<cbc:Name>Ainult siseriiklikest õigusaktidest tulenevad kõrvaldamise alused</cbc:Name>
<cbc:Description languageID="ET">Kas ettevõtja on rikkunud asjaomases teates või hankedokumentides sätestatud ainult siseriiklikest õigusaktidest tulenevate kõrvalejätmise alustega seotud kohustusi?</cbc:Description>
<cac:Legislation>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c753a2c5-59e6-4970-b6eb-27224e96bf76</cbc:ID>
<cbc:Title languageID="ET">Avaliku sektori hankemenetlustes kohalduvad RHS § 95 lg 1 p-d 2 ja 5 ning § 95 lg 4 p-d 1 ja 11. Avaliku sektori erihangetes kohalduvad RHS § 95 lg 1 p-d 2 ja 5 ning vabatahtlike kõrvaldamise aluste kohaldamist täpsustab hankija hanke alusdokumentides.
Võrgustiku sektori hangetes täpsustab hankija hanke alusdokumentides, milliseid siseriiklikke kõrvaldamise aluseid ta kohaldab.
Siseriiklikud kõrvaldamise alused RHS-is on järgnevad:
§ 95 lg 1 p 2 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget või muud seaduslikku või asjaomase riigihankega seotud lepingulist esindajat on karistatud riigis ilma seadusliku aluseta viibivale välismaalasele töötamise võimaldamise või välismaalase Eestis töötamise tingimuste rikkumise võimaldamise, sealhulgas seaduses sätestatud töötasu määrast väiksema töötasu maksmise eest“ (kohustuslik kõrvaldamise alus);
RHS § 95 lg 1 p 5 „kes või kelle haldus-, juhtimis- või järelevalveorgani liige on rahvusvahelise sanktsiooni subjekt rahvusvahelise sanktsiooni seaduse tähenduses“ (kohustuslik kõrvaldamise alus);
RHS § 95 lg 4 p 1 „kellel on hankija asukohajärgse kohaliku maksu maksuvõlg maksukorralduse seaduse tähenduses“ (vabatahtlik kõrvaldamise alus);
RHS § 95 lg 4 p 11 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget või muud seaduslikku esindajat on karistatud maksualaste süütegude eest (vabatahtlik kõrvaldamise alus)“.</cbc:Title>
<cbc:Description languageID="ET">Avaliku sektori hankemenetlustes kohalduvad RHS § 95 lg 1 p-d 2 ja 5 ning § 95 lg 4 p-d 1 ja 11. Avaliku sektori erihangetes kohalduvad RHS § 95 lg 1 p-d 2 ja 5 ning vabatahtlike kõrvaldamise aluste kohaldamist täpsustab hankija hanke alusdokumentides.
Võrgustiku sektori hangetes täpsustab hankija hanke alusdokumentides, milliseid siseriiklikke kõrvaldamise aluseid ta kohaldab.
Siseriiklikud kõrvaldamise alused RHS-is on järgnevad:
§ 95 lg 1 p 2 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget või muud seaduslikku või asjaomase riigihankega seotud lepingulist esindajat on karistatud riigis ilma seadusliku aluseta viibivale välismaalasele töötamise võimaldamise või välismaalase Eestis töötamise tingimuste rikkumise võimaldamise, sealhulgas seaduses sätestatud töötasu määrast väiksema töötasu maksmise eest“ (kohustuslik kõrvaldamise alus);
RHS § 95 lg 1 p 5 „kes või kelle haldus-, juhtimis- või järelevalveorgani liige on rahvusvahelise sanktsiooni subjekt rahvusvahelise sanktsiooni seaduse tähenduses“ (kohustuslik kõrvaldamise alus);
RHS § 95 lg 4 p 1 „kellel on hankija asukohajärgse kohaliku maksu maksuvõlg maksukorralduse seaduse tähenduses“ (vabatahtlik kõrvaldamise alus);
RHS § 95 lg 4 p 11 „keda või kelle haldus-, juhtimis- või järelevalveorgani liiget või muud seaduslikku esindajat on karistatud maksualaste süütegude eest (vabatahtlik kõrvaldamise alus)“.</cbc:Description>
<cac:Language>
<cbc:LocaleCode listID="LanguageCodeEU" listAgencyName="EU-COM-GROW" listVersionID="2.0.2">ET</cbc:LocaleCode>
</cac:Language>
</cac:Legislation>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2"></cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">30048e48-16c4-4150-aa2c-939965f6f91c</cbc:ID>
<cbc:Description languageID="ET"/>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CAPTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">NONE</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2"></cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ee6d410c25e2dc277d8cc35caa8089e8-1.1</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2"></cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ee6d410c25e2dc277d8cc35caa8089e8-1.2</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2"></cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ee6d410c25e2dc277d8cc35caa8089e8-1.3</cbc:ID>
<cbc:Description languageID="ET">Mis on Teie vastus?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2"/>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
<cac:TenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7458d42a-e581-4640-9283-34ceb3ad4345</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ON*</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a531f251e54c354ff4934abc376d6301-1.1</cbc:ID>
<cbc:Description languageID="ET">Kas see teave on elektrooniliselt kättesaadav?</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">INDICATOR</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
<cac:SubsidiaryTenderingCriterionPropertyGroup>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41dd2e9b-1bfd-44c7-93ee-56bd74a4334b</cbc:ID>
<cbc:PropertyGroupTypeCode listID="PropertyGroupType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">ONTRUE</cbc:PropertyGroupTypeCode>
<cac:TenderingCriterionProperty>
<cbc:ID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1fe6f352b8fce36ae55b86fb37f488d4-1.1.1</cbc:ID>
<cbc:Description languageID="ET">Tõendid</cbc:Description>
<cbc:TypeCode listID="CriterionElementType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">QUESTION</cbc:TypeCode>
<cbc:ValueDataTypeCode listID="ResponseDataType" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">EVIDENCE_IDENTIFIER</cbc:ValueDataTypeCode>
</cac:TenderingCriterionProperty>
</cac:SubsidiaryTenderingCriterionPropertyGroup>
</cac:TenderingCriterionPropertyGroup>
</cac:TenderingCriterion>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">55e00336-d835-4177-be8d-a48cc6901795</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a8f39f21f1a4f61006839d17c48d58c3-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a4b55ad4-c362-440a-94a1-05c2d4d0d1f6</cbc:ID>
<cbc:ResponseID schemeAgencyID="EU-COM-GROW">Lot1</cbc:ResponseID>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">62ebffac-57be-41c4-a773-2f6abbd13872</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">85d57d4b7fa89f637f91d9d8b027405c-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">278a0407-c681-47f9-958f-e8a0ae895632</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">573fe430-4420-4ed9-b7d8-d0cb185b01db</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2d902c8235ebefb9296053f5363306ef-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cb18e16c-12f0-4c79-abba-f194c863a09c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f4b64f98-7a72-4635-8b12-8d200a7a6296</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a3e8a6e67e44334c5f2afdd4e7562fa7-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5f2fe0a1-661c-4ef8-83e5-f439037c179b</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">918a38e7-3924-4eb2-b734-786861811093</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a8999a4d1b62c66814d34ecfebb4c1ae-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">40895e0f-dc11-4564-9fc1-94003f2d1f5d</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">691437fd-dc1c-4b09-8f9e-6cc029c62048</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67b088a852a32478afb7cc8fd19d3fb5-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7d21f125-389a-4e9c-9e77-7556b58be377</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3897540d-f7bb-4dd0-8e3c-d1fd946cf224</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3c0b4f12a3e8a3f4f4023932e10ed8a9-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8e9d7a70-1d24-4669-838d-5b2d143db7c2</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">95b7d1a9-e7ee-416d-a335-4297a7f8ae4c</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">762dc3a323dc6704cf8944168406e22a-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a35b7c0d-ca16-447f-b7cf-4eb6e8cc3793</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9ef07fe0-f0b7-44e3-be49-440c180cdc27</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">354daa93c73508e8eceb357ca3a9475a-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c963b98d-788e-4535-ac31-4a460464e675</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2372b9db-95c2-4840-90fa-1712d91a0fc1</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">db41347baa09a8c0a5cae4ca70927e9d-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">308b1f00-7020-42d7-8222-4f37cd654ee2</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">52768ad3-6890-49fb-83af-4c86c62fc494</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ece600a9097944288e11a1b6699fb6bb-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">507ce59e-d25f-4fbd-9f7f-8497fe7ff40b</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5d686038-b406-414d-bfd6-9233bc4874fd</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">94bafa958a57a2f5fa7af1f5c03b1e54-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">520afa43-2529-4a2a-8ee5-dbd45fee2798</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">059dd160-499e-4b76-90c4-07102c1007e6</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">07df47ce65627207b1b045f7a91524fe-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c3665e2d-a0f5-4049-b7cb-bdb045cf643d</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">271e9458-3fb6-42eb-ba6f-562f15840868</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">056f8a7d83e7385f1028c51aa00aa34b-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e471af7b-10c0-47f2-83e4-0595208e10b4</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">70dc1dd1-8442-4e4f-b325-31b1e46991fa</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">de8e758fa6893cfd64668285fa226847-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">28b9cd14-ada6-484f-b9ae-75bc3a1e9e42</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">096d29c8-9f00-4599-ac00-51c9d87ca31e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a531f251e54c354ff4934abc376d6301-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3982f3e6-7b8d-4fc5-8e63-1612c0fe565c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a61dbac4-8c80-4b39-81ac-91a3a5cba0e6</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ca0dd639-8723-46a4-ba7f-db34739289b3</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">54f185c0-a9f0-421f-8abb-ea641cb05378</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f6b858925af7cad9dee2869edd4ff60c-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e97e4562-efae-4384-af4e-ec6f96cca8ab</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">eca306bd-24d0-4c9d-a20c-a5a55c3e51a4</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9715cfa07bc54f829aa383179c605554-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">080d6b42-34ac-4a71-8268-e0db5db7c1ee</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">00697fd3-b818-4b24-836e-774a58758403</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6833f9ee60ab7d82b44c62c2da533ff0-2.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:EvidenceSupplied>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6833f9ee60ab7d82b44c62c2da533ff0-2.1.1</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">37fbe440-532b-40c7-8271-16cd64b1dc2e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e5651c9fcebc0f9e0b6c2adea0f6ae0a-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bc59ed74-a33a-4589-b163-47ae49861282</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b5fd00f2-dde9-401b-a62b-c9666a8c99a5</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">797467a9cd053779f8189cc09b53cd15-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">43d6526e-f784-4bbd-b94d-ac57fe463494</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">45431bb3-b3d1-4649-a2f9-8827631e1492</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">88f454ed56cf088fa5cd0eb926751769-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c1f57494-24f0-48b2-a3a3-2d3007625752</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f2a869fd-13af-4b76-b9fe-fce47fc5edce</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">24f26f42d53a913959ce42027dc14bb1-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">81895f2b-fd7c-4069-bb38-72fce8cc96c3</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">03917b1b-4240-4207-a48c-f41b60d0ca99</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c97dab162756613157478a51204f9c86-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ce8d5677-89c2-475a-a1eb-19a322be96ec</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">80e6580e-b8b1-489f-93e4-5a55199bd27f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">036d42bf0ba523328b09842e95e5a483-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">94e1712c-edb4-4cb9-a2fd-3f2c74324ab5</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">edea1c3a-7ac5-48d2-beac-a4a9fd2f4b0f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">130b632716c48f4b7f69f61016f3ef5c-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">25ed04e9-6971-44fc-bd85-624c39e9694c</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d04c8fd0-93a8-467c-a6c4-d7328d2d86f9</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">557c987e3ce67681b7c884af3c38f3f4-2.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:EvidenceSupplied>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">557c987e3ce67681b7c884af3c38f3f4-2.1.1</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">41475034-0333-42b4-bf48-7c9cf629886e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dced61ca05d4b6509ba11c848f7efc58-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f122de04-ef49-4bc0-828a-c763b3c49e09</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b33feac5-7f51-4f60-a4f2-fa2cef2b349e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0cc2de07ff96b1169913b554d5735478-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">108df19f-e04c-4987-9d38-01e6ae3672da</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cc7efa1c-a843-4291-9c06-c41fa0bbd715</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">916ab5ce762c49fbffd04765384d9195-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5115d3b3-32a6-4f74-a7ea-a430f585464d</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ff9997df-8102-472e-af91-e9d75302a7d0</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8511a8ee6a5fe826b0c1c6759cc36403-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d36d4225-7c6a-43ac-84bc-4ca5a7e7e5af</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ef5d1d45-745d-45d1-a206-3d5c55f294be</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a798f5c4df3b296808ec367318de88e5-1.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c0a3adc9-2d51-441e-8310-7c6d3c77efb1</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">787a1499-841e-4f30-ac12-6f5b41ac0f75</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">06238c8b82047ad5f649f64687cfed04-1.2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9a8910b2-d807-43ee-95a0-57fb15335aff</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bc5dd7e7-673c-4ee3-bb86-73d91ef74e88</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">67abefe9c6becc08ff7027f880cf8e58-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">df74e765-53a7-44ee-9781-b89083ff3857</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">94b13233-6dc5-4431-8483-3a9fecef8ab7</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">431420fc0327c7dfc0c8e338db661a4f-2.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:EvidenceSupplied>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">431420fc0327c7dfc0c8e338db661a4f-2.1.1</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">447f119f-0993-40d8-9851-c37d975e4359</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">bf6b522598fc8784858a6712851f7fa2-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">58c1fb46-f134-49d2-af20-e82688ec74bc</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">955dce60-14b9-4353-9b2f-19780e04d223</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6c3dc3029e6128b5025c2727085b8a67-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">68c42339-bced-4b38-b390-50a33e3e531e</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4cc587ae-49f6-4ef9-bae3-930f0cf6880c</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9895d63fec57f19d41d599f8db9cdf91-2.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:EvidenceSupplied>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9895d63fec57f19d41d599f8db9cdf91-2.1.1</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">157cc516-0476-4f64-9d4b-257a425187cd</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8a42266c5fb24e32ff421942459d66ac-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2a011f93-21f1-4ca8-882a-bf64f1ef1a29</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9092d6bc-b2e2-42f3-8afd-f4447ce12868</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">7498d35783aaf5b55a3d4b5b1f7995d2-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f14f4e41-8b1d-4d25-8fcf-3a04060bd798</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0a4260d3-50ce-4139-9dbf-e31f770af93e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9ec5f8c89b9cfb663ec773102d3d63ea-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">c6dcddb9-1c9a-4c5e-b2ff-29a5b094c8e0</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b12017ea-d803-45a7-80ac-1160e58f0b64</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8474ff05cd1affe49977b11837ffc832-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f73d55b3-e23a-4ec9-95f7-66eb5f2e4d54</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">61d05db0-c584-495c-94d4-84b90ef8e015</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">664e928718e7857cd0a1f6f4ce5d5e78-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">033f90f9-1fb6-432f-ac32-3e6df8cea91f</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">be7c9688-10ee-49a8-8c3b-74349adce894</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5e63f6d15c35d9de0ca7ce2f47548ba6-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d8962bed-659c-42c0-bbaf-ae2091178d3c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">fac48ec7-72bd-4e16-bef9-24fc11d67493</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5a10919abd31fa6f8738ed8e2bfc2c30-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0e0d7229-e647-46d6-9bf7-656daf22a9d9</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ff3ee14d-7bea-4b85-9144-c309abe0b942</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">0da3567bd1587969627a71cc637bf3ff-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">48d8142d-0bcc-4040-aff3-e4e85bab5f9a</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">418fb22d-5cec-4824-94fc-18e1759b5fa8</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">476a15b9d9f85459a63cadc3e3b73460-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">656e46c9-f5cd-4e39-9b22-b5d515ea6b6f</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">850d02fe-a202-4715-92c6-bd10ab7b19a3</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">699c2f5f4ae65e623002d40bb3ee7ee9-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">cdbe53e8-8c80-4c2c-93a7-5501a65caf18</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">28e309a0-d1f0-43b0-84ee-d940a7ac0f7c</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8d66094d6187fbeb250bc18bf2899a37-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dd905be8-a9e3-43a9-96a1-c2adb9a73af5</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">dd28d00a-a455-4ace-80be-3ae952701a01</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8bc3c952560f6ad78eb65c5373517e78-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a0dbd5db-30de-4a99-816a-2ccb81d0efa5</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8680dddd-358b-4c5d-94b0-800669aa63b4</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2d056d00bb0a19f4805cac08dcf7a67d-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">3f4f3e3e-6fae-422d-a292-a8a164067d81</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d281e5b7-db04-4214-9a81-0cc7c19751be</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">db96b332d0df0d7ce653977d80137c3e-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">a34ef5a3-a9fc-46d6-bb21-aca2a4ad20ab</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">5befbd2c-ffef-4484-8038-29e33761b5a8</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e84b04d9cced34ecb51466b1045b0324-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9ab8c32b-b187-4bca-8b4f-936c6841f7be</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d1f4a312-1b7a-4d2f-b4a6-2bbf92c62b9e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1ee9e1dfca8300341b206644744d8fe0-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">998f571e-202b-4978-a389-9a07d9098130</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">2eb691aa-c321-4cdb-b5db-5cca327636bf</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">642c63e9ae63a12207197f19f3d6a53e-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">63566a7f-9fb9-4cf3-814c-47d0fa7341dc</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b6a19918-3866-4bc7-bdc1-7f55d2c8c188</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e2eb7a88e019a3caf911d6a20865d056-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4fd167c6-ac40-40fb-8e0b-e14ad7c935b2</cbc:ID>
<cbc:ResponseIndicator>true</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">ca50926f-08b7-4f4f-b61b-c1922aeda557</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">560e5e7ef0d3d163430768039c402848-2.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:EvidenceSupplied>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">560e5e7ef0d3d163430768039c402848-2.1.1</cbc:ID>
</cac:EvidenceSupplied>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">165e67ae-2c7a-4ce5-90ae-2f5059d3fc77</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d71f2afecb0aec233e2f178327ac18d1-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">1a128d06-026c-4465-952c-ea6418c710fd</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">39a56aa1-ea3d-4b71-bc51-eebf7ec1d84e</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">795818013abcd8fa0b614f8ab21ae90b-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">db3c8e92-5948-4430-afbf-8422f4030960</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">9746841e-a391-4174-ba54-bbbc85539b63</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b1f1dc7c01597a65463e2c18253f83c0-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">aee2dcac-7989-499b-8842-67de71ff53f5</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">754ebb99-ec91-4718-955c-b9562dd09563</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">962c3b6715f062c66fb25afbefe1360a-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">90ca6e08-54bb-4690-b6f5-2d942922259c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">482615cd-dd74-4860-8fe5-99533960760f</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">8486f521e63eee007f5f05abbddcaae9-1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">6b85f8dc-dc68-428e-a504-ea7f95334036</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">b2e73e94-1864-4e5f-b5a1-ddd05b879a03</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">03299642dcd03d0b74e6fcec1d941d60-2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">09c7156a-245b-427f-9959-a5e5325ead5c</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">115374a0-486e-4b48-ad0f-34707a4b2c13</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">d2b922c3afdd52c13d295e3333eafa67-1.1.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">190ca9ff-bdd5-4508-902c-9fdf25e29af2</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:TenderingCriterionResponse>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">f809b034-3a44-42f4-b609-a03e3b777f8b</cbc:ID>
<cbc:ValidatedCriterionPropertyID schemeID="CriteriaTaxonomy" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">e5f319d2c9fe7a95fde7de1281fac693-1.2.1</cbc:ValidatedCriterionPropertyID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:ResponseValue>
<cbc:ID schemeID="ISO/IEC 9834-8:2008" schemeAgencyID="EU-COM-GROW" schemeVersionID="2.0.2">4d70c153-2129-42d9-a908-231e4ad1082d</cbc:ID>
<cbc:ResponseIndicator>false</cbc:ResponseIndicator>
</cac:ResponseValue>
</cac:TenderingCriterionResponse>
<cac:Evidence>
<cbc:ID schemeAgencyID="EU-COM-GROW">6833f9ee60ab7d82b44c62c2da533ff0-2.1.1</cbc:ID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:DocumentReference>
<cbc:ID schemeAgencyID="EU-COM-GROW"></cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://riigihanked.riik.ee</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:DocumentReference>
</cac:Evidence>
<cac:Evidence>
<cbc:ID schemeAgencyID="EU-COM-GROW">557c987e3ce67681b7c884af3c38f3f4-2.1.1</cbc:ID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:DocumentReference>
<cbc:ID schemeAgencyID="EU-COM-GROW">255269</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://riigihanked.riik.ee</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
<cac:IssuerParty>
<cac:PartyName>
<cbc:Name>Riigi Kaitseinvesteeringute Keskus (70009764)</cbc:Name>
</cac:PartyName>
</cac:IssuerParty>
</cac:DocumentReference>
</cac:Evidence>
<cac:Evidence>
<cbc:ID schemeAgencyID="EU-COM-GROW">431420fc0327c7dfc0c8e338db661a4f-2.1.1</cbc:ID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:DocumentReference>
<cbc:ID schemeAgencyID="EU-COM-GROW">Registration No. 40003021907</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://www.vases.lv/en</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:DocumentReference>
</cac:Evidence>
<cac:Evidence>
<cbc:ID schemeAgencyID="EU-COM-GROW">9895d63fec57f19d41d599f8db9cdf91-2.1.1</cbc:ID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:DocumentReference>
<cbc:ID schemeAgencyID="EU-COM-GROW"></cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://riigihanked.riik.ee</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:DocumentReference>
</cac:Evidence>
<cac:Evidence>
<cbc:ID schemeAgencyID="EU-COM-GROW">560e5e7ef0d3d163430768039c402848-2.1.1</cbc:ID>
<cbc:ConfidentialityLevelCode listID="ConfidentialityLevel" listAgencyID="EU-COM-GROW" listVersionID="2.0.2">CONFIDENTIAL</cbc:ConfidentialityLevelCode>
<cac:DocumentReference>
<cbc:ID schemeAgencyID="EU-COM-GROW">https://www6.vid.gov.lv/NPAR web page only in Latvian</cbc:ID>
<cac:Attachment>
<cac:ExternalReference>
<cbc:URI>https://www6.vid.gov.lv/NPAR</cbc:URI>
</cac:ExternalReference>
</cac:Attachment>
</cac:DocumentReference>
</cac:Evidence>
</QualificationApplicationResponse>
PURPOSE OF PROCUREMENT: The purpose of the procurement is to acquire Radio signal Automatic Detection software for the existing monitoring system to improve the situational awareness in radio spectrum and to enhance radio monitoring capabilities. To fulfil the objectives the software must have the required functionality and work together with the existing Rohde & Schwarz Receivers as follows: EB200, EM200, PR200, PR100, EM550, UMS400 and DDF255 . License quantity 2 ; License type perpetual ; All licences are registered for Estonian Defence Forces ; Licences includ e technical support (warranty) and software updates for two years ; After the end of the warranty period, extending software support is possible. Software user training on -site for 3 persons is included in price; Description of the software : The radio signal automatic detection software can control the receivers of existing frequency monitoring network. The monitoring tasks are entered into the software (the frequency ranges and the parameters) and the measurement cycles are automatically performed according to tasks. The results are stored on the central server or on local computer as needed. As a result of the procurement, both server software and control software will be procured. Crucial capability of the software is automatic signal detection to automate the daily work. Requirements for the software: No Feature Parameters 1. Purpose Automatic Detection of Radiofrequency Signals 2. Language Estonian or English English, user interface can be translated to any language 3. Functionality: Automatic detection of signals The software must be able to distinguish the radio signal from the noise in at least three ways: According to the shape of the signals – The software must contain samples from well-known signals. Using the mask method – a signal drawn by user. Using the machine learning method – a signal found by the user is used as a teaching input. Software SKUDRA module Patrol can detect radio signals by: Shape of the signals, SKUDRA provides library of signal shapes and it can be extended with user created signal shapes; User defined mask; Using the machine learning method; 5 . Functionality: Automatic detection of signals At least the following information is recorded about automatically detected signals: a) Frequency (ITU SM.377-4). Signal bandwidth (ITU SM.443-5). Signal strength ( dBµV , dBm). Signal to noise ratio (SNR). Correlation with the compared sample. For each detected signal, there is recorded fallowing parameters: Frequency; Signal to noise ratio; Correlation; Field strength; Bandwidth; Occupancy; Possible frequency user; EFIS classification; 6 . Functionality: Automatic detection of signals The system can compare detected signals with EFIS allocations (European Frequency Information System). For detected signals there is calculated possible frequency user according to license database, and also EFIS allocation classification for given frequency. 7 . Functionality: Demodulation of signals Demodulation, audio recording and playback of known signals must be possible. Monitoring software SKUDRA module Skudra target allows to record and decode (analogue signal) audio. 8 . Functionality: Data storage The collection of information on the detected signals is done either on a local computer or on a central server, as needed. All measurement data is stored on local computer and by user request can be uploaded to central server (SKUDRA Server). 9 . Functionality: Data storage The database of the central server must contain historical information about measurement results and be able to visualize it both statistically and as spectral images through queries. All SKUDRA Patrol uploaded measurements are stored in SKUDRA Server, where all information is searchable and sortable by different criteria. 10 . 924687 -30977 Functionality: Automation of measurements The software must enable the automation and scheduling of measurements based on pre-filled tasks. SKUDRA modules allows task planning for all Skudra Patrol instances from single user interface point. See Skudra Server section “Scheduler” screenshots 1 1 . Compatibility Runs on Windows 10 and 11 operating system. Yes, SKUDRA Patrol and Target modules work on windows versions 7, 10 and 11 . 1 2 . Compatibility Compatible with Rohde & Schwarz Receivers as follows: EB200, EM200, PR200, PR100, EM550, UMS400, DDF255 See Skudra Target manual section “1.2 Supported devices” and Skudra Patrol manual section “1.1.2 Supported receivers”, “1.1.4 Supported direction finders” 1 3 . Compatibility Must be able to control a minimum of six (6) receivers simultaneously, including direction finders. One SKUDRA licenses provides simultaneous control of 3 (three) receivers. 2 (Two) SKUDRA licenses provides simultaneous control of 6 (six) receivers in total. 1 4 . Visualization The geographical location information must be visualized in the map view. SKUDRA modules all modules provides data visualisation on map. Skudra server provides functionality of map layer switching, where WMS and TMS web services can be defined in Skudra server configuration section. 1 5 . Visualization It must be possible to visualize the spectral shape of detected radio from data storage. It is possible to visualize the spectral shape of detected radio from data storage. See SKUDRA Patrol screenshot 15. Visualization Must support the waterfall spectrum display format. SKUDRA software modules provides functionality to display spectrum in waterfall format, see screenshots: 16. User rights There must be means that access to the system is only for authorized users. SKUDRA modules and their data is accessible to authorized user only, user authorization can be integrated with company active directory LDAP service. For SKUDRA module TARGET it is possible to configure limited “guest” user access. SIA „Elektroniskie sakari” "Electronic Communications Office of Latvia" Ltd Reģ. Nr. 40003021907 R egistry code: 40003021907 A drese : Eksporta iela 5, R ī ga , Latvija , LV-1010 Address: Eksporta street 5, Riga , Latvia, LV-1010 Name: Jānis Bārda Position: Chairman of the Management Board Signature * Name: Laila Līduma Position: Member of the Management Board Signature * Name: Jurgis Porins Position: Member of the Management Board Signature * * THIS DOCUMENT HAS BEEN SIGNED WITH E SECURE ELECTRONIC SIGNATURE AND CONTAINS A TIME STAMP
USER MANUAL
v.4.7.3 20.08.2024
Content
Initial Setup ............................................................................... 6
Setting up the software ............................................................ 6
Computer configuration requirements...................................... 7
Supported receivers ........................................................... 7
UMS100 support ................................................................ 7
1.1.3.1 Installation of SkudraUMS100 service ....................................... 8
1.1.3.2 Settings of SkudraUMS100 service ......................................... 11
1.1.3.3 Removal and update of SkudraUMS100 service .......................... 12
Supported direction finders ................................................ 13
Licence protection ........................................................... 13
Network configuration ............................................................ 13
Firewall settings ............................................................. 14
IPv6 support .................................................................. 17
Software update ................................................................... 17
Software update in special cases .......................................... 17
Insignificant software updates ............................................. 18
Short Tutorial ........................................................................... 19
Commencing measurements ..................................................... 19
Measurement process control ................................................... 19
Measurement result analysis ..................................................... 19
Editing Measurement Results .................................................... 23
Actions with the Receiver during monitoring ................................. 24
Stopping measurements, saving results and storing them in the database 25
Description of the Software User Interface ......................................... 28
Measurement section ............................................................. 28
Stored measurements settings .................................................. 30
Settings section.................................................................... 32
Range definition section ......................................................... 34
Sample spectra section ........................................................... 36
Machine learning section ......................................................... 38
Masks section ...................................................................... 39
Description of Complete Functionality .............................................. 40
Measurement control and visualization ........................................ 40
Starting, stopping and interrupting measurements ..................... 40
2
Saving and opening the results ............................................ 41
Automatic saving of results................................................. 42
Upload results to Skudra Server ........................................... 42
Closing measurements results and the software ........................ 44
Informative messages ....................................................... 45
Measurement ranges ........................................................ 45
Signal detection result list ................................................. 45
Explanation of Signal Determination Result Parameters ............... 46
4.1.9.1 Notification of unauthorised emissions ................................... 48
Signal Search Result List Context Menu .................................. 49
Cumulated spectrum of signals ............................................ 50
Bandwidth breakdown graph ............................................... 51
The frequency range’s spectrum .......................................... 51
The frequency range’s spectrum: Markers ............................... 53
Field strength and occupancy time graph ................................ 54
Map: Frequency Assignments ............................................... 55
Map: Direction finding results .............................................. 56
Direction finding override .................................................. 58
Spectrogram (Spectrum Waterfall) graph ................................ 59
Examining spectrum lines of spectrogram ............................... 61
Aural monitoring ............................................................. 62
Reporting frequency usage statistics to Skudra Server ................. 63
The Functionality of Settings .................................................... 65
Saving settings ............................................................... 65
System Settings .............................................................. 65
4.2.2.1 Current settings of DF equipment ......................................... 68
Editing of measurement session type for saved measurements ....... 71
Configuration and import of licence database .......................... 72
Frequency use licence recalculation (update of results) .............. 73
The List of Specific Frequencies ........................................... 74
Interaction with Skudra Server ............................................ 76
Map storage ................................................................... 76
Measurement Ranges functionality ............................................. 78
Receiver settings ............................................................. 78
Licence detection configuration ........................................... 80
Narrowband signal detection configuration .............................. 80
Mask signal detection configuration ...................................... 81
3
Jammer detection configuration .......................................... 82
Broadband signal detection configuration ............................... 82
Statistics and spectrogram configuration ................................ 83
DF scanning configuration .................................................. 83
Triggered DF configuration ................................................. 84
DF equipment settings ...................................................... 85
Editing the range setting list ............................................... 86
The Sample Spectra Functionality .............................................. 87
Adding and Displaying Sample Spectra ................................... 87
Sample spectra source: Spectrogram ..................................... 89
The list of sample spectra .................................................. 89
Editing the sample spectra list and exchanging it with Skudra Server 91
The functionality of the frequency assignment database ................... 92
Functionality of Machine Learning .............................................. 93
Generation of Machine Learning models ................................. 93
Functionality of Mask Detection ................................................ 99
Mask generation .............................................................. 99
Mask manipulation .......................................................... 101
Mask administration ........................................................ 103
Functionality of Remote Control ............................................... 105
Software operating principles ....................................................... 106
Measurement of range spectra ................................................. 106
Signal detection .................................................................. 106
Narrow band detection .................................................... 106
Broadband detection ....................................................... 107
Mask detection .............................................................. 108
Jammer detection .......................................................... 109
Direction finding ................................................................. 111
Direction finder settings changed by Skudra PATROL ................. 112
Direction finding override ................................................. 113
Dynamic bearing and location correction by Compass and GNSS .... 113
Direction finding: Report DF results to Skudra Server ...................... 114
The storage of signals detected ................................................ 115
The establishment of signal parameters ...................................... 115
File formats ............................................................................ 116
The file format of the antenna factor and cable attenuation ........ 116
4
The file format of the licence database ................................. 116
The format of the specific frequency file ............................... 117
The file of radiofrequency applications ................................. 117
CSV file of radiofrequency applications ................................. 118
5
Initial Setup
Setting up the software
No installation is necessary for the software Skudra – just copy the software folder
from the USB stick to the desired folder in the computer. For user convenience a
shortcut may be created.
It is important to designate the correct value of start in. By default start in should
be correct, but in the event of copying the shortcut from another computer it may
occur that the start in value should be corrected.
6
Computer configuration requirements
Technical requirements for the running the software:
• OS: Microsoft Windows 7, 10, 11 with Microsoft.NET Framework 4.7.2 or later;
• CPU: Intel Core i5;
• RAM: 4GB;
• HDD: 100GB;
• Screen resolution: 1280 x 720 px;
Supported receivers
R&S EB200; R&S ESMB; R&S EB500; R&S ESMD; R&S DDF255; R&S PR100; R&S EM100;
R&S EB510; Narda SignalShark; R&S DDF107; R&S DD205; R&S EM550; R&S UMS100;
R&S PR200; R&S EM200; R&S DDF550 (and derived devices e.g. R&S UMS300 and
UMS400).
UMS100 support
R&S UMS100 support is provided through SkudraUMS100 windows service installed on
UMS100 embedded computer. Installation files are provided with copy of Skudra
Patrol. SkudraUMS100 requires Microsoft.NET Framework 2.0 to be installed on
UMS100 embedded computer.
7
SkudraUMS100 service forwards commands sent to and received from embedded
UMS100 receiver to external TCP connection, that is accessible on UMS100 IP address
and port set in during installation of service. Thus, when configurating Skudra Patrol,
external IP address of R&S UMS100 and port set during the installation of service has
to set as receiver IP (port) in settings panel.
As Skudra Patrol requires OS and Microsoft.NET framework far newer than that
achievable on UMS100 system, only way to run Skudra Patrol with UMS100 is using
Skudra Patrol on remote computer with SkudraUMS100 service installed on UMS100.
1.1.3.1 Installation of SkudraUMS100 service
• Installation of SkudraUMS100 service has to be done on R&S embedded
computer;
• As later possible configuration or removal of service is possible only with same
application that installs service, it is advisable to run installation
(SkudraUMS100comLoader.exe) from folder that will be accessible
throughout the lifetime of service;
• Installation of SkudraUMS100 service is started with running the file
SkudraUMS100comLoader.exe. After that following screen appears:
8
• Functionality to install service is provided in tab “Service”;
• To install SkudraUMS100 service, it is first necessary to press “Remove
SkudraUMS100 service”. Doing that performs check whether service is
installed and if installed uninstalls service;
• After ensuring that service is not installed, Install SkudraUMS100 service is
enabled:
9
• By pressing “Install Skudra UMS100 service” service will install with defined
settings. After successful installation following message box will be displayed:
10
• After service is installed it will start every time as the system starts and block
use of set Serial (COM) port by any other application. To unblock serial port
to be used by another application, Skudra Service has to be uninstalled or
stopped (temporarily) using Windows services functionality.
1.1.3.2 Settings of SkudraUMS100 service
• Serial (COM) port related settings is dependant of actual internal
configuration of UMS100, however settings shown in this manual may be
considered as default;
• As used serial (COM) port may not be visible in UMS100 device manager, it
can be found using Serial port communications software (like PuTTy) by
checking which port responds to connection requests;
• After restart of receiver Baud rate is set to 19200 (and such must be used
when communicating through PuTTY), however SkudraUMS100 service sets
Baud rate to selected in settings. Value of 115200 is recommended, as it
provides faster data connection;
• For Skudra Patrol to recognize SkudraUMS100 service as UMS100 receiver, it
is required to set Device name to “UMS100”;
11
• TCP port has to be set to free port. Generally Skudra software uses ports in
range 19005 to 19100, therefore it may be practical to use port in this range,
as use of them already may be allowed by network administrator. However it
is possible to use any free port of UMS100 computer, provided that network
is configured to allow communication on selected port;
• Read and Write timeouts defines time how long service waits before request
from Skudra Patrol is considered unsuccessful. Setting High values (in range
of 1000 ms) is only necessary if network between Skudra Patrol and UMS100
frequently experiences comparable delays. High timeout values comes with
drawback of longer communication retry times. However setting small (in
range of tens of ms) response timeout maybe too short for receiver to perform
sweep and return results.
1.1.3.3 Removal and update of SkudraUMS100 service
• Removal of SkudraUMS100 service can be done by installation
(SkudraUMS100comLoader.exe);
• To stop and remove SkudraUMS100 service from UMS100 user has to press
“Remove SkudraUMS100 service”. After following message boxes will be
displayed:
12
• After SkudraUMS100 service is uninstalled, it can be updated (installed
again with different settings). See 1.1.3.1
Supported direction finders
R&S DDF255, R&S DD205; R&S EB500; R&S ESMD; R&S PR200; Narda SignalShark
Licence protection
The software is protected from unlicensed use by a USB dongle. To start and use the
software Skudra, the dongle accompanying the software licence agreement must be
plugged into a USB port.
No manual driver installation is necessary for the dongle. The driver is installed by
the Windows operating system when the dongle is first plugged in.
If the software is started without the dongle a warning message appears.
One dongle licenses three instances of Skudra running simultaneously.
Network configuration
The software Skudra uses the Transmission Control Protocol (TCP) and User Datagram
Protocol (UDP) to communicate with the receiver or Skudra Server Database.
Thus typically (however receiver can be configured to use different ports), Skudra
should be allowed appropriate access to:
• Outgoing connection (from Skudra to receiver) on ports:
13
o 5555 (TCP) for all supported receivers except SignalShark and UMS100
o 5300 (TCP) for Narda SignalShark receivers
o 19050 (TCP) or other for UMS100 service (see. 1.1.3 )
o 5563 (TCP) for R&S DDF550 in addition to 5555 (TCP)
• Outgoing connection (from Skudra to receiver) for TCP streaming on ports:
o 5565 for receivers R&S EB500, ESMD, DDF255, R&S EB510, EM550,
PR200, EM200, DDF550 (and derived devices e.g. R&S UMS300 and
UMS400)
• Incoming connection (from receiver to Skudra) for UDP streaming on ports:
o 19005 – 19100 (UDP) for R&S EB200, PR100; R&S EM100, DDF107,
EM550 only. Often this functionality is firewall-blocked by default,
and must be manually allowed. In case UDP packets are blocked, the
connected receiver model may be determined, but monitoring
spectrum is not acquired.
• In order to save monitoring results, as well as upload and save spectrum
samples and spectrum usage statistics in the Skudra Server Database, a TCP
connection is necessary (port 80 or 443).
Connecting via VPN and tunnelling, etc. is supported, but the delay involved may
slow down the speed of scanning.
Firewall settings
Following is relevant to R&S EB200, PR100; R&S EM100, DDF107 and EM550 only.
Initial use of Skudra software, depending on the computer configuration, may require
unblocking Skudra access to arriving receiver UDP data.
14
To allow access, it is necessary to define in which networks access to receiver data
is licensed – work/home, public (sometimes, domain). The choice must be made
according to the network connection indicator.
If there is no pop-up message concerning blocking of the software, you may need to
check if Windows is set up to alert on the change of settings:
15
An alternative method is adding Skudra to the programs allowed to communicate
through the Windows firewall or to alter the Skudra entry according to the used
network.
16
IPv6 support
Skudra Patrol supports IPv6 addressing. IPv6 address can be provided in formats
[2001:db8:85a3:8d3:1319:8a2e:370:7348]:443 or
2001:db8:85a3:8d3:1319:8a2e:370:7348:443. However, for address IPv6 to work it is
necessary that receiver supports IPv6 also.
Software update
Most often software updates are done by substituting the files in the core folder of
Skudra with the updated ones. In special cases, when noted in the information
accompanying the update, it may be necessary to change all the content of the core
folder as explained in the next section.
After such updates the software will keep the setup intact and it will be possible to
open earlier saved result files.
If old result files are not needed any more, their support may terminated to make
the software operation more effective.
Software update in special cases
If the description of the software update states that all of the core folder files should
be changed, in order not to lose the software settings, prior to the change the
following core files should be saved in a temporary folder of the user’s choice:
• cfg_applications.xml
• cfg_licence_db.xml
• cfg_licence_spec.xml
• cfg_meas.xml
• cfg_paraugspektri.xml
• cfg_ranges.json
• cfg_user.xml
• cfg_viz.xml
• karte (folder)
The file “cfg_paraugspektri.xml” contains sample spectra. If the user has never
appended the sample spectra, using “cfg_paraugspektri.xml” from the update should
be considered, as this already contains sample spectra that enable optimal signal
determination in the software developer’s measurement environment. Similarly the
17
folder karte (map) update should be considered, because it contains the current map
of Latvia, the update of which by software tools is time consuming.
Continuing the update, all content of the core folder should be deleted. If the old
files remain, the software may not work properly. Further, all core files from the
update should be copied to the computer’s Skudra core folder and the earlier saved
configuration files in the temporary folder should also be copied back to the
computer’s Skudra core folder.
! This special update procedure should also be used updating from a version earlier
than 4.0.9 to 4.1.0 and higher.
Insignificant software updates
Doing insignificant software updates, if the accompanying information does not
require otherwise, it suffices to substitute the computer Skudra core files with the
ones in the update.
Most often updated are the files “skudra.exe”, “skudra.exe.dp64.dll” and
“language.cfg”. Prior to substituting these the software should be closed.
18
Short Tutorial
Commencing measurements
To begin measurements, start the software either from the shortcut (1) or directly
from the folder “\core\skudra.exe”.
The software Skudra will start with last session’s settings.
If no changes are needed in the measurement settings, monitoring can be
commenced immediately by clicking the measurement start button (A.1). If changes
are necessary, they should be applied in the settings section (0).
To start the software for the first time it is necessary to define at least the receiver’s
IP address and port (5555) in the appropriate window (3.3).
Parameters most often changed in day-to-day operations:
• Geographical coordinates of the monitoring site (Error! Reference source n
ot found. and Error! Reference source not found.);
• Monitoring range (D.1);
• Licence database file download (Error! Reference source not found. and
REF _Ref508629959 \r \hError! Reference source not found.);
• Skudra Server authorisation (Error! Reference source not found. un Error! Re
ference source not found.)
Measurement process control
An ongoing measurement can be paused by clicking the button “PAUSE” (A.1) or
completely stopped by clicking the button “STOP” (A.2).
Settings can not be changed during an ongoing measurement.
Measurement result analysis
The software constantly visualizes the measurement process regardless if the
measurement is underway, paused or stopped completely, thus the user can observe
ongoing events as they develop.
During measurement, bands checked in the settings section are scanned. Bands are
scanned consecutively and cyclically. The progress of each range scan is displayed in
parentheses after the range.By clicking the name of the range, the spectrum of the
19
respective range is visualized. It should be taken in account that, to see the spectrum
,the button “Spectrum” should be clicked.
The bands spectrum graph can be zoomed in by drawing the frame over the part of
interest. The displayed spectrum central frequency can be changed (to sequently
review the spectrum) by clicking the graph with the left mouse button. Zooming out
to see the complete spectrum is done by clicking the graph with the right-hand
mouse button.
Signal detection results from all scanned ranges are presented in the list of results.
The results are aggregated by frequency channel and monitoring range. Each entry
can have multiple parameters, which may be revealed or hidden by clicking the right-
hand mouse button on the column title.
Explanation of signal detection result values:
Frequency - The frequency channel (MHz), where the signal was found.
Depending on the range set, the channel step may be 100 kHz or 6.25 kHz;
Range - The name of the user-determined measurement range where the
signals were detected;
Corr. - Average correlation value (see section ) of all signal events in the
frequency channel;
Lev. – Field strength dBµV/m (see section );
Diff. – The difference between the theoretically calculated and the measured
field strength. Positive values are assigned to field strength that exceeds
theoretically calculated, but negative – strength that is less than theoretically
20
calculated. Zero is displayed when the measurement is equal to the theoretical
value or theoretical calculations show there should not be any signals at the
monitoring site;
Dist. – Distance in kilometres from the monitoring site to the possible licence
coordinates. Zero is displayed if by theoretical calculations the transmitter
should not be received;
BW – the emission’s bandwidth in kHz (see section4.1.8);
% - Frequency occupancy (%) as the number of instances of signals determined
over the number of scans, expressed in percent;
Count – Number of instances of signals determined;
Em. class – The class of emission most often determined, found by comparing
the received signal with the sample spectra;
Licence – most probable licence (it’s holder);
Lic.Nr – The number of the most probable licence;
Application – Radiofrequency application according to EFIS;
Notes – User added comment. Text input in this field will be linked to the saved
entry in the Skudra file as well as the Skudra database.
By highlighting an entry in the signal determination result list, it is possible to
show the corresponding licence on the map, the cumulated spectrum of the
frequency channel, bandwidth breakdown and the time-level or occupancy
graph of signals determined in the frequency channel.
Click the button “map” to display the map.
The map shows licences corresponding the frequency channel. The large blue marker
shows the monitoring site. A small blue marker shows the most probable licence at
the monitoring site, other licences are shown by grey markers. Clicking on the
marker, a menu opens with licence owner and number, theoretically calculated level
21
and it’s difference with the measurement result, distance to the monitoring site,
emission class and the option to mark the licence as most probable. On the
monitoring site marker it is possible to mark the most probable licence (owner)
without linking coordinates.
To visualize the observed signal’s cumulated spectrum and bandwidth breakdown in
the frequency channel, the buttons ”Spectrum” and “Bandwidth” should be pressed
accordingly. The graphs show most often observed frequency – level pairs (or
correspondingly, bandwidth - level pairs) with a hue that is closer to red. Less often
observed values are shown with a hue closer to blue.
To view the detected signal field strength/time or occupancy/time graphs of the
frequency channel the buttons “Field strength” or “Occupancy” should be
correspondingly clicked. The graphs are shown alternatively – opening one, the
second is closed. The occupancy graph shows the number of signal detections in 15
minute intervals.
22
Both the field strength and occupancy graphs may be zoomed into by drawing the
frame over the spot of interest and zoomed out by right-click of the mouse on the
graph.
Editing Measurement Results
Results may be edited during measurements, after measurements have stopped, or
opening an earlier saved result file.
The following editing actions are possible:
• Delete entries (frequency channels);
• Change licences designated as most probable;
• Recalculate most probable licences for all the signal determination result list,
using modified monitoring site coordinates, updated licence database and
other frequency licence input and range settings.
No other edits are foreseen, e.g., bandwidth or level time graph.
Signal detection result list entries may be deleted highlighting the entry and choosing
“Delete selected” (delete highlighted) from the mouse right-click menu.
Alternatively “delete” may be pressed on the keyboard. Entries may be deleted one
by one or several at a time by highlighting them pressing and holding the keys “Shift”
or “Ctrl”.
23
Licences found as most probable, can be changed only one by one. Licences included
in the licence database or the list of specific frequencies can be chosen on the map,
and on the marker menu clicking “set as actual”. In cases when the licence will not
be listed in the database, the corresponding frequency/user pair can be saved to the
specific frequency file, opening the mouse context menu by right-click, choosing
“Store in specific freq.” (to the specific frequency list), inputting the user
information and clicking “Save”.
Complete recalculation of the most probable licence, radio communication system,
difference between theoretical and measured level of the signal determination list
can be done by clicking the button “Recalculate results” in the “Stored measurement
settings” section (B.4).
The results will be updated according to the current settings: “Coordinates,
”Rec. antenna height”, ”Environment”, ”Licence database file”, “Specific
frequencies’ file” and it’s changes, ”Application file”, as well as the newly set “Min.
field strength” and “Guaranteed distance”.
Actions with the Receiver during monitoring
While the software Skudra is carrying out measurements, the receiver may be
disconnected from the software. In this case the software will stand by until the
receiver is reconnected or the measurement is manually stopped.
24
On disconnecting the receiver from the software it is safe to change any receiver
settings (except the IP address and port). Upon reconnecting the receiver with the
software, all settings necessary for the functioning of the software will restore their
correct value.
Correction of software settings necessary for the operation of the software is not
done constantly, but in specific moments (e.g., upon loosing connection). Therefore,
while the receiver allows it, parameter change during the operation of the software
may give unforeseen results. The following settings have direct impact on the
measurement results and software operation: IP configuration, IF spectrum display,
duration of measurement, IF Span, IF spectrum accumulation mode, IF spectrum
width – SPAN, RF attenuation, IF mode (Lowdist/Normal/LowNoise) and for individual
receivers spectrum point width (Sharp/Narrow/Normal).
Stopping measurements, saving results and storing
them in the database
Measurement may be stopped by clicking the “STOP” button (A.2).
After interrupting the measurement, buttons will be shown to erase the active
results from the software memory, saving and sending them to the database.
By clicking the save button (A.4), the results will be saved in the result folder
indicated in the settings section (Error! Reference source not found.). The result f
ile will be named automatically. The name will consist of the start date of
monitoring, name of the measurement session, start and stop frequencies, a serial
number based on the previous criteria and a version serial number in the sequence
hereby listed.
Upon clicking the upload to database button (A.5), the results will be uploaded to
Skudra Server. If successful, a link to the saved result will be shown in the
measurement sections lower left corner, but in the case of failure a pop-up error
message will be displayed.
25
User authorization is required for any interaction with Skudra Server. Authorization
is done by entering the user’s name and password and clicking “accept” button below
password box or just pressing “Enter” key in password box.
Access tokens received after successful authorisation are stored in Windows
credential manager for each instance (separate executable file) of Skudra Patrol
separately.
Normally continuous access to Skudra is maintained (if requested) by automatically
retrying every 30 seconds.
Expander in the middle of the message box contains additional information about
connection error.
However in cases when connection is refused because of invalid or non-existent
access token user is prompted for username and password.
26
The saved token may be deleted clicking the button with the cross in the group
“Skudra SERVER paths”.
27
Description of the Software User Interface
Measurement section
28
A.1. Combined functionality measurement start and A.15. Marker showing licences assumed less posible;
measurement pause button; A.16. Menu showing information corresponding to the
A.2. Combined functionality measurement interrupting and marker;
saved measurement opening button; A.17. Menu to change the highlighted licence as most
A.3. Button to close current (indicated) measurement results; probably corrresponding to the signal;
A.4. Button to save current (indicated) measurement results; A.18. Blue marker showing most probable licences;
A.5. Button to upload the current (indicated) measurement A.19. Light blue marker showing the monitoring sitei;
results to the database (Skudra Server); A.20. Selected range’s spectrum maximum value curve
A.6. Bands in which monitoring will be done; (MaxHold);
A.7. Measurement cycle range scan progress; A.21. Selected range’s spectrum instantanious value curve
A.8. Signal detection results column title, that may comprise (ClrWrt);
Frequency, Range name, Correlation, Level, theoretical A.22. Button to display and hide the map of licences
level Difference, Distance to transmitter, emission corresponding to the frequency;
occupied Bandwidth, how often the signal is detected A.23. Button to display and hide the range spectrum graph;
(%), Number of emissions detected, Owner of the A.24. List of signal detection results;
licence, Number of the licence, Radio communication A.25. Cumulated signal spectrum for an entry chosen from
application and user Notes; the list of signal detection results;
A.9. Menu to delete the highlighted entry from the list of A.26. Bandwidth/level two dimensional breakdown for an
signal detection results; entry chosen from the list of signal detection results;
A.10. Menu to add the highlighted entry to the list of A.27. Frequency time/level occupancy graph for an entry
specific frequencies; chosen from the list of signal detection results;
A.11. Menu to copy the list of signal detection results to the A.28. Button to display and hide the cumulated spectrum;
clipboard; A.29. Button to display and hide the signal bandwidth/level
A.12. Menu to adjust the receiver’s volume while Paused; two dimensional diagram;
A.13. Area to display information on the working of the A.30. Button to display the level/time graph;
software; A.31. Button to display the occupancy/time graph.
A.14. Map showing licences corresponding to the frequency;
29
Stored measurements settings
30
B.1. Treeview to select stored or ongoing mesasurement session
settings to be view in field on right;
B.2. Display of measurement ranges list (choise selected in
treeview on the left) of current or stored measurement
session;
B.3. Licence detection’s minumum field strength input field to
be used for Recalculation of results;
B.4. Licence detection’s guaranteed distance input field to be
used for Recalculation of results
B.5. Button for recalculation of the signal detection result list for
an updated theoretically possible detectable transmitter list
at the monitoring site
31
Settings section
32
C.1. System settings(4.2.2)
C.2. Map storage settings(4.2.8)
C.3. List of frequencies specific to monitoring site(4.2.6)
C.4. Licence database configuration(4.2.4)
C.5. Interaction with Skudra server(4.2.7)
33
Range definition section
34
D.1. Measurement ranges editing list (4.3.11) D.7. Range broadband (machine learning) detection
D.2. Range receiver settings(4.3.1) settings(4.3.6)
D.3. Range licence detection settings(4.3.2) D.8. Range statistics and spectrogram settings(4.3.7)
D.4. Range narrowband (correlation) detection settings(4.3.3) D.9. Range direction finding triggering settings(4.3.9)
D.5. Range mask detection settings(4.3.4) D.10. Range direction finder’s settings(4.3.10)
D.6. Range jammer detection settings(4.3.5)
35
Sample spectra section
36
E.1. Sample spectra list; E.14. Button to add the highlighted potential sample
E.2. Sample spectra display and defining graph; spectrum to the sample spectra list;
E.3. Sample spectra usage statistics graph; E.15. Button to visualize the statistics of all frequencies
E.4. Sample spectrum highlighted in the list; where the signal was determined to be close to the selected
E.5. The highlighted entry’s (in the signal detection list) sample spectrum including number of occurrences;
cumulated spectrum quasi mode value; E.16. Button to delete the highlighted sample from the
E.6. A potential sample curve of values of 200 kHz wide software’s list of sample spectra;
spectrum; E.17. Button to erase all unsaved changes to the list of
E.7. A potential sample curve of values of 25 kHz wide sample spectra;
spectrum; E.18. Button to add remotely stored (Skudra Server)
E.8. A potential sample curve of values of 12.5 kHz wide sample spectra to the local sample spectra list;
spectrum; E.19. Button to upload the highlighted entry in the list of
E.9. Sample spectra which have been determined as sample spectra to Skudra Server;
closest to the highlighted entry in the signal determination E.20. Button to save changes to the list of the local sample
result list and how often they have been observed; spectra;
E.10. Button for manual fine tuning of the middle E.21. Information on the deviation of the user added
frequency of the highlighted potential sample spectrum to a frequency offset points of the potential sample spectrum
lower value; from the sample spectrum middle frequency;
E.11. Button for manual fine tuning of the middle E.22. Information on the additional number of necessary
frequency of the highlighted potential sample spectrum to a correlations to the potential sample spectrum (each with an
higher value; additional frequency deviation of one point);
E.12. Button to obtain quasi-mode spectrum and potential E.23. Information on the number of offset points of the
sample spectrum from the highlighted entry in the signal automatically determined potential sample spectra central
detection result list; frequency.
E.13. Button to cancel the manual changes to potential
sample spectra;
37
Machine learning section
38
Masks section
39
Description of Complete Functionality
Measurement control and visualization
Starting, stopping and interrupting measurements
• To start measurements click the typical multimedia design button “Play”
(A.1), to stop – “Stop”(A.2);
• It is possible to pause the measurement by clicking the button “Pause” (A.1),
and restart by clicking the button “Play”. During the paused measurement
the receiver may be used for aural monitoring, and other purposes, including
disconnecting from the software. After clicking the button “Play” monitoring
will resume and the results will not be fragmented.
• If prior to commencing measurements the software contains unsaved
measurement data or unsaved open measurement results, the software will
offer to save the existing results, not save/discard changes or cancel opening
of the result file.
• If any active (set as used) measurement range has DF triggering enabled
(4.3.9), “DF ON” / ”DF OFF” button is visible in “Control” group. Also
Direction finding record together with currently active DF-ied frequency is
shown in “Ranges” group.
• When starting measurement session button is in “DF ON” state, indicating
that direction finding is in progress. Direction finding can be interrupted by
setting (clicking) button to “DF OFF” state, and continued by setting
(clicking) to “DF ON” state. During the interruption direction finder can be
used for any other task. However, by interrupting DF process, all DF requests
40
enqueued (5.3), yet not DFied will be lost. DF requests completed are not
influenced;
• “Direction finding: On hold” message is displayed in “Ranges” group if
direction finding in not performed by several reasons:
o User has pressed “DF OFF” button,
o Receiver is being used for frequency scanning, when same equipment
is used as receiver and direction finder,
o All frequencies on direction finding queue have been DF-ied.
• It is possible to run Skudra Patrol in remote control mode (4.8), when
measurement ranges are configured, measurements started and stopped, and
results saved automatically by Skudra Server. This mode is enabled and
disabled by toggling “REMOTE” button;
• Remote control mode can be enabled only if no measurements are active and
Signal detection results are cleared.
Saving and opening the results
• Upon stopping the measurements the result may be saved in a file by clicking
the button “Save” (A.4);
• The result will be saved together with the setting information in a “zip” file
which is automatically named by a sequence of the monitoring start date,
measurement session name, start and stop frequencies, a serial number
based on the previous criteria and a version serial number in the sequence
hereby listed. The result file will be saved in the folder specified in the
settings section (Error! Reference source not found.);
41
• The result file may be opened clicking the button “Archive” (A.2) and
selecting the appropriate file. Opening the file, full functionality is restored
as it was after stopping the measurement;
• If prior to opening a result file the software already contains unsaved
measurement results or unsaved changes of open measurement results, prior
to opening the new file the software will offer to save the existing results,
not save/discard changes or cancel opening of the result file.
Automatic saving of results
• During measurement and introducing changes to either earlier saved or
unsaved results, results are automatically saved in an internal software file.
The goal for this automatic saving is to prevent loss of the results in case of
incorrect closure of the software, e.g., unforeseen shutdown of the
computer;
• In cases of it’s incorrect closure, the software will inform the user and offer
to save the automatically saved results;
• If the software was closed correctly, it is not possible to restore unsaved
results.
Upload results to Skudra Server
• After stopping measurements, the signal detection results may be uploaded
to Skudra Server by clicking the button “upload” (A.5) in the measurement
section;
42
• To enable uploading the results, the software must have access to the Skudra
Server access key (see section 4.2.7);
• The following information is sent to Skudra Server: monitoring coordinates,
time of monitoring, measurement session type, measurement range limits,
the contents of the signal search result list (all columns), the cumulated
spectra of each entry, bandwidth breakdown, signal level change with time,
DF results (if available);
• The upload progress during uploading the results is shown in the bottom left
corner of the software window;
• When upload is complete a link to the saved result is displayed in the bottom
left corner of the software window. It is possible to copy the link to the
uploaded result to the clipboard by right-clicking the link and choosing
“copy”.
• If measurement has been set-up, with options that performs periodic updates
to Skudra (DF reporting to Skudra server, statistics, waterfall spectrogram
storage to server) and corresponding measurement has been deleted from
Skudra server, measurement upload to server will result in error “Storing to
Skudra Server not complete The remote server returned an error: (500)
Internal Server Error. DoesNotExist at /api/events/ranges/…”. To avoid that
Skudra server measurement reference at Skudra Patrol has to be cleared at
“Stored measurement settings” panel’s (3.2) “Server ranges reference”
selection by clicking “Clear ranges refences”.
43
Closing measurements results and the software
• The results displayed by the software may be closed clicking the button “X”
(A.3) in the group of control buttons;
• The software may be closed by clicking the button “X” in the software
window’s upper right corner;
• If there remains unsaved measurement data or unsaved open measurement
results when closing the data file or the software, the software will offer to
save the existing results, not save/discard changes or cancel closing of the
result file or software.
• If there is no warning displayed, there have been no unsaved results in
the software.
44
Informative messages
• Most error messages and other information that will occur while running
the software will appear in the area for informative messages (A.13) at
the lower left of the software window;
• These messages may be copied to the clipboard or cleared by clicking the
right mouse button and choosing “copy” or “clear” respectively.
Measurement ranges
• By clicking the measurement start button (A.1) measurements are started in
the ranges (A.6) that are displayed in the group “Ranges”. Measurement
ranges and parameters should be defined in the measurement range list in
the settings section (D.1);
• If any of measurement ranges is set up to trigger direction finding, currently
active direction finding task or direction finding status will be shown as last
record in “Ranges” group.
• At each range the appropriate scanning progress of the measurement cycle is
shown (A.7);
• During measurements or while reviewing earlier measurement results, by
clicking the left mouse button over the range, the appropriate range’s
spectrum will be displayed.
Signal detection result list
• The signal search result list (A.24) shows entries of all frequency channels
where signals were observed;
45
• Detecting a signal in a frequency channel where previously no signal was
detected (no entry in the list), a new entry appears top of the list. If the
signal is detected repeatedly, content of the entry is appended;
• The result list may be arranged in an ascending or descending order for every
shown value by clicking the left mouse button on the columns title (A.8);
• The result list’s columns may be displayed or hidden by clicking the columns
title (A.8) with the right mouse button and choosing the appropriate columns
out of the context menu appearing;
• Highlighting an entry to the result list, the appropriate cumulated spectrum
(A.25), bandwidth breakdown (A.26), licences corresponding to the frequency
including map coordinates (A.14) and the time or occupancy graph (A.27) is
displayed. Highlighting several entries, information will be displayed for the
last highlighted entry.
• Introduced changes to the signal determination list can be saved to new result
file or uploaded to the database. Already saved result files and database
entries will not be edited.
• The size of the signal search result list may be changed by dragging the lists
top and right-hand borders. Column size (respecting the system design
minimum) may changed by dragging the column title borderlines.
Explanation of Signal Determination Result Parameters
Frequency – The frequency channel (MHz), where the signal was found. Depending
on the range setting (D.1), the channel step may be 100 kHz or 6.25 kHz;
Range – The name of the user determined measurement range where the signals
were found;
46
Corr. – Average value of detection quality of all registered signal events in the
frequency channel. However, different signal detection types have different
meaning for this parameter:
• For narrow band detection - maximum Pearson correlation coefficient
squared (determination coefficient) among correlations of all sample spectra;
• For broadband detection – Selected ML model output from 0 to 1;
• For jammer detection – Maximum of Carrier specificity in dB, in specified
spacing range;
• For mask detection – maximum mask overshoot/undershoot value in dB;
Lev. – Maximum electromagnetic field strength dbµv/m exceeding 2% of events of
signal detection. The field strength is calculated by adding the antenna factor and
cable attenuation (see 4.2.2 ) to the signal level. The signal level of each detection
is calculated as the maximal value of spectrum in the signal bandwidth. The 100 kHz
channel step FFT resolution is 2.5 kHz, 6.25 kHz – 125 Hz, Blackman windowing.;
Diff. – The difference between the theoretically calculated and the measured field
strength. Positive values are assigned to field strength that exceeds theoretically
calculated, but negative – field strength that is less than theoretically calculated.
Zero is displayed when the measurement is equal to the theoretical value or
theoretical calculations show there should not be any signals at the monitoring site;
Dist. – Distance in kilometres from the monitoring site to the possible licence
coordinates. Zero is displayed if by theoretical calculations the transmitter should
not be received;
BW – the emission’s maximum bandwidth in kHz exceeded in 5% of signal detections
at a signal to noise ratio at least 30 dB. If the signal to noise ratio has never exceeded
30 dB, the bandwidth is calculated as maximum of unique bandwidth level
combination pairs exceeding 5% of signal observations. The signal bandwidth in each
detection event is determined by the 1% β (99% power in bandwidth) method, and
by the mid-level between the maximum level and noise level if the signal to noise
ratio does not exceed 30 dB;
Count – Number of instances of signals detected;
DF cnt. – Number of direction finding attempts that successfully returned direction
Em. class – For narrowband detection the class of emission of the sample spectrum
that most often correlates most with the signal in the specific frequency channel.
For broadband, jammer and mask detection field is always filled with “broadband”,
“jammer” and “mask” respectively;
Licence – The holder of the most probable licence of the signal received at the
montoring site. The addressees or users that are not linked to coordinates are shown
in parantheses;
47
Lic. Nr. – The number of most probable licence of the signal received at the
monitoring site;
Application – Radiofrequency application relevant to frequency in the EFIS classifier
according to the downloadable file from www.efis.dk which has been set in the
settings section as radiofrequency application file (6.1.5);
Notes – User added comment. Text input in this field will be linked to the entry in
the signal determination result file.
4.1.9.1 Notification of unauthorised emissions
Signal detection result(4.1.8) list contains information, whether detected signal is
authorised according to frequency assignment database (4.5,) filtered by set licence
detection parameters (4.3.2), and whether emissions on particular frequency
overshoot set spectrum mask(4.3.3).
• In all detection modes, if, for particular frequency channel, frequency
assignment in particular monitoring site is considered invalid or there is no
assignment for frequency at all, Licence field for related record in signal
detection results list contains key “-” – no assignment;
• In mask detection mode, Emission class field contains keywords “mask+” or
“mask-” – emission has overshoot or undershoot mask. Mask detection is
independent of unauthorised signal detection, thus signal can be both –
unauthorized and spectrum mask, just one or none.
48
Licence (unauthorised emission) and mask detection (overshoot) events are sent to
Skudra Server, if at least one of measurement options are enabled: Report statistics
(4.1.22), Report DF to Skudra Server (5.4), Remote control with automatic upload to
Skudra Server (4.8), or if results are manually uploaded to Skudra Server.
Signal Search Result List Context Menu
Right-clicking the mouse on an entry in the signal search result list opens a menu
providing the following functionality:
• “Delete selected” – the highlighted entry and all associated information
about the signals observed on the frequency will be erased. The task may be
carried out by clicking the key “delete”. If multiple entries are highlighted,
all will be deleted;
• “Clear DF Results” – All direction finding results for highlighted entry(-ies)
will be erased. If multiple entries are highlighted, DF results for each entry
will be erased;
• “To specific list” – the highlighted entry’s frequency may be added to the list
of specific frequencies (setting section, list of specific frequencies (Error! R
eference source not found.). The frequency user should be entered and
confirmed by clicking the button “Save”;
• “Copy list” – All entries of the signal search result list are copied to the
clipboard in “csv” format to be pasted in any word or spreadsheet processor.
49
Cumulated spectrum of signals
• The cumulated spectrum of signals corresponding to the highlighted entry in
the signal detection result list is displayed to the right of list (A.25). If
multiple entries are highlighted, the last cumulated spectrum will be
displayed;
• The cumulated spectrum graph may be displayed or hidden by clicking the
button (A.28) on the panel below the cumulated spectrum or the time graph,
if the cumulated spectrum is hidden;
• In the cumulated spectrum, all observed signal spectra in the frequency
channel are shown. Spectra containing no signal, only noise, are not included.
All signal spectra are overlayed. The number of appearances of the relevant
frequency-level pair is colour-coded from red (maximum, though often less
than 100%) to green, to blue (once);
• The cumulated spectrum characterizes how often the signal is detected –
whether on the frequency operates one or several transmitters, what the
base station/repeater spectrum looks like.
• The cumulated spectra at the channel step of 100 kHz are displayed in a band
of 500 kHz, but at the step of 6.25 kHz in a 31.25 kHz range;
• The cumulated spectra graph can be resized by dragging the graph’s top
border. The cumulated spectra contains 200x300 values. When resizing, the
aspect ratio 2:3 is kept unchanged;
• Marker of cumulative spectrum value, currently mouse hovering on, is
displayed in mouse tooltip.
50
Bandwidth breakdown graph
• Right of the signal search list is the two dimensional display of the signal
level/strength (A.26) relevant to the highlighted entry in the list. When
multiple entries are marked, the cumulated spectrum of the last highlighted
entry is displayed;
• The Bandwidth breakdown graph may be displayed or hidden by clicking the
button “Bandwidth” (A.29) in the panel under the bandwidth breakdown
graph or the time graph if the bandwidth breakdown is hidden;
• All combination pairs of signal bandwidth/level detected in a single frequency
channel of a measurement range are displayed in the bandwidth breakdown
graph. Bandwidth measurements with signal to noise ratios no less than 30 dB
(measurements are done with the 1% β method – 99% power in the bandwidth)
are displayed colour-coded from red (maximum) to green, to blue (a single
event). Combination pairs with a signal to noise ratio less than 30 dB (by
spectrum width in the middle between maximum and noise level) are
displayed grey. The frequency of equal results are not cumulated for the
latter;
• The bandwidth breakdown graph helps to determine the field strength of a
specific bandwidth signal – what is the field strength of a repeater, what is
the field strength of a base station;
• The bandwidth breakdown at the channel step of 100 kHz is displayed in a
band up to 500 kHz, but at the step of 6.25 kHz – up to 31.25 kHz;
• The bandwidth breakdown graph can be resized by dragging the graph’s top
border. The cumulated spectra contains 200x300 or 250x300 values. When
resizing, the aspect ratio is kept unchanged.
The frequency range’s spectrum
• The range’s spectrum graph is displayed on the right-hand side of the
measurement panel. The graph shows spectrum of the range highlighted in
the measurement panel’s list (A.6);
• Several spectrum traces are available at frequency range spectrum chart
51
o Maximum Hold spectrum (Max), Minimum Hold (Min) and Current value
(ClrWrt) – available for every measurement,
o Spectrum mask above (Mask+) and/or spectrum mask below (Mask-) –
available if corresponding detection is set for selected range,
o Spectrum trace from spectrogram (WF) – available if selected from
spectrogram (4.1.20)
• Colour and line width of each trace can be set by right click on legend’s
corresponding item. Selected values will retained for every spectrum range,
including mask definition chart (also after restart):
• Every spectrum trace available on frequency range spectrum chart can be
temporally hidden, by right clicking on corresponding legends item.
• The bands spectrum graph may be zoomed in on the abscissa by left-mouse
drag on the necessary limits. Right-click of the mouse, performs 4x zoom-out.
By left-click of the mouse the central frequency may be set without changing
the zoom, thus gradually reviewing all the spectrum under magnification;
• The bands spectrum graph may be zoomed in on the ordinate by left-mouse
drag on the necessary limits while holding “shift” key. The maximum range
may be restored by right-click of the mouse, while holding “shift” key;
• Maximum Hold spectrum (Max) can be cleared by selecting “Clear” in tooltip
menu on graph’s legend;
• The bands spectrum graph may be displayed or hidden clicking the button
“Spectrum” (A.22) under the spectrum graph or the frequency’s licence map
if the band’s spectrum graph is hidden;
• The bands spectrum graph may be resized by hiding or displaying the
frequency’s licence map, or dragging the bottom border under the button
“Spectrum” (A.22);
• Spectrum trace value, currently mouse hovering on, is displayed in mouse
tooltip.
52
The frequency range’s spectrum: Markers
Marker functionality is added to frequency range spectrum to aid reading spectrum
values.
• Markers can be added either by mouse left-click while holding “Ctrl” key or
by holding mouse left-click for longer than 1 second;
• Markers can be removed either by mouse right-click while holding “Ctrl” key
or by holding mouse right-click for longer than 1 second;
• In total 3 markers can be added. Adding 4-th marker, the marker will be set
in place of marker which is closest to clicked position;
• When added, marker is set on spectrum trace with value closest to clicked
position;
• All markers are always set on same spectrum trace. If new marker is added
to trace another than that of previous markers, previous markers are set to
trace of new marker;
• If no more than 2 markers added:
o first marker shows selected frequency and field strength value,
o second marker shows frequency and level difference to first marker;
• If 3 markers added:
o Third marker (e.g. last marker changed) shows frequency and field
strength of marker and frequency difference between marker of
highest frequency and marker of lowest frequency,
53
o First and second marker shows frequency and level difference to
third marker (e.g. last marker added).
Field strength and occupancy time graph
• The field strength or frequency occupancy time graph is displayed in the
measurement section’s lower right corner. The displayed graph may be
chosen by clicking the button “Field strength” (A.30) or “Occupancy” (A.1);
• The graph displays data of the highlighted entry in the signal determination
list;
• The frequencies signal level is displayed as the ordinate, and the time is
displayed as the abscissa. In the case no signal was observed during search,
the ordinate displayed is minimal. If the process of measurement has been
stopped or interrupted, the time graph will show a gap;
• If the occupancy graph option is chosen it is generated from the percentage
how often the signal appears in 15 minute intervals according to Recommen-
dation ITU-R SM.1880;
54
• Both the field strength graph and occupancy graph may be zoomed in on the
abscissa by left-mouse drag the necessary time limits. Right-click of the
mouse, performs 8x zoom-out.
• Both the field strength graph and occupancy graph may be zoomed in on the
ordinate by left-mouse drag on the necessary limits while holding “shift” key.
The maximum range may be restored by right-click of the mouse, while
holding “shift” key;
• The graph may be resized displaying or hiding the cumulated spectrum and
occupancy graphs, as well dragging the graphs top border.
Map: Frequency Assignments
• Map in measurement panel is used for two functionalities: display of
frequency assignments and display of direction finding results;
• The frequency assignment map can be shown or hidden by toggling “Map”
button in centre-right part of measurements tab;
• The frequency assignment map (A.14) displays all available licence infor-
mation on the highlighted frequency in the signal detection list;
• Monitoring site location is displayed on map as large blue marker. Position of
marker is updated as soon as coordinates for monitoring site are changed
(4.2.2). If prior measurement results are shown, however, monitoring site’s
position will be shown corresponding to measurement data;
• The licence assignment coordinates are displayed on the map by small
markers. Small blue marker designates the coordinates of the most probable
assignment. Other coordinates of the same frequency assignment are marked
by small grey markers;
55
• The assignment map’s coordinate context menu shows the frequency’s
licence owner, licence number, theoretically calculated field strength, the
difference between calculated and measured field strength, distance from
the monitoring site to the assignments coordinates and emission class
according to licence as well as the option to mark the assignment as the most
probably received;
• In the monitoring site’s marker’s context menu it possible to define an
unknown spectrum (NRS) user as the most possible signal source, as well the
option to mark as most possible an assignment without coordinates or an
undefined user from the list of specific frequencies;
• The signal detection result list is also updated according to the change of
assignment of the received signal;
• The map uses OSM maps offline or online (Error! Reference source not f
ound.), according to the map settings in the settings section;
• The map may be resized displaying or hiding the range’s spectrum graph or
waterfall graph (by clicking “Spectrum” or “Waterfall” buttons respectively),
as well as dragging the map’s lower border.
Map: Direction finding results
Map in measurement panel is used for two functionalities: display of frequency
assignments and display of direction finding results;
56
• The frequency assignment map can be shown or hidden by toggling “Map”
button in centre-right part of measurements tab;
• Direction finding results are displayed as histogram for currently selected
record in signal detection result list (4.1.8). Direction finding results and
corresponding functionality is only visible if the selected record has direction
finding attempts associated;
• Histogram is displayed by dark grey beams, with various opacity ranging from
minimum for single occurrences of particular bearing to full opacity for
bearing measured most often;
• Opacity behaviour of histogram display can be altered by HIST text box in
top-right corner of map in format “minimum visible recurrence – recurrence
for maximum opacity”. By setting minimum above 0, it is possible to dismiss
rare directions, by setting maximum bellow 100 it is possible to reduce impact
of most frequent bearing;
• Width of each individual bearing can be set by Δ textbox in top-right corner
of map;
• Red beam denotes last direction measured, it can be enabled or disabled by
pressing button at bottom-right corner of map (“261°”), number represents
last direction measured;
• First text box at bottom-right corner of map contains successful direction
finding attempts versus all attempts;
• Second text box at bottom-right corner of map contains date and time of last
direction measured;
57
• Third text box at bottom-right corner of map contains channel frequency of
signal, direction finding results and licences are displayed for;
• Forth text box at bottom-right corner of map contains direction and distance
from monitoring site location to mouse cursor as well as coordinates in DMS
format. That can be used to readout bearing values from map.
Direction finding override
If any active (set as used) measurement range has DF triggering enabled, “DF
override” button is visible in centre of “Measurements” tab. By clicking “DF
override” button “DF settings to override” and “DF queue” groups are shown.
User can manually set frequency to DF by selecting corresponding record in signal
detection results list and clicking “START DF…”
• By selecting record in signal detection results list DF settings to override list
filled with DF equipment settings that has been defined in “DF equipment
settings” (4.3.10) for range on which signal was detected, except “DF
bandwidth” row that is filled with value corresponding to measured
bandwidth of signal.
• If more than one record is selected in signal detection results’ list, “DF
settings to override table” won’t be filled with DF equipment settings that
has been defined in “DF equipment settings” and rows without check mark
for overriding will be disabled, however settings corresponding defined “DF
equipment settings” still will be used for direction finding.
58
• If check box in first column of “DF settings to override” is checked, user set
value will be used instead of automatically selected DF setting.
All settings to override except “All DF azimuth correction” are effective only for
direction finding that user has requested manually by clicking “START DF…” button.
“All DF azimuth correction” setting (if checked) will be used for all DF results –
for manually set frequencies and automatically set frequencies. However, bearing
results that have been gathered prior to change of “All DF azimuth correction” are
not changed.
• After direction finding override is started, “DF queue” group shows list of
frequencies manually set for direction finding. Direction finding queue of
automatically selected frequencies is preserved and is shown and used after
manually set direction finding is stopped by clicking “STOP DF” button.
• Contrary to automatically created “DF queue”, manually set frequencies are
not removed from list after direction finding has been made and will continue
endlessly or until “DF duration between scans” (4.2.2), if same receiver is
used for scanning and direction finding.
• If same equipment is used for scanning and direction finding, during direction
finding cycle scanning is paused (“Pause” button pressed), direction finding
will continue until DF queue is empty or endlessly if manually set frequencies
is being DF-ied.
Spectrogram (Spectrum Waterfall) graph
• To display actual spectrogram data, corresponding measurements have to be
opted in Ranges section or measurements that includes spectrograms have to
be stored before (See Ranges section for more information);
• Data displayed in Waterfall graph is generated every 256 scan cycles and after
the measurement is stopped. After the same events it is possible to update
spectrum waterfall;
• Zoom levels are generated sequentially after necessary scan data is acquired.
Second zoom level is generated after first 512 scans, third after 1024 scans
59
and so on. That way it is ensured that access speed to measured spectrogram
is similar to that of viewing map;
• Waterfall section is displayed above Time chart and Cumulated spectrum plot
if Waterfall button is toggled on:
• User has to select spectrogram data to displayed in waterfall graph. There
are two options provided for that. To show previously stored spectrogram
user has to press “open folder” button. To show currently acquired
spectrogram linked to selected frequency range user have to toggle on
“chain” button:
• In process of selecting stored spectrogram for display user is provided with
browse folder dialog. During measurement spectrograms are stored in results
folder set in Settings section. Spectrograms for each measurement session is
saved in subfolder with the name identical to one automatically given to zip
file when saving measurement result. Further each measurement range in
measurement session have subfolder named after range ID and range name.
This folder has to be selected to display waterfall;
60
• If user has opted to show currently acquired spectrogram, spectrogram of
currently selected range in Ranges group box (in Measurement section) will
be displayed after clicking on corresponding range;
• To display spectrogram of currently selected range regardless of further
selection of measurement ranges, user can toggle off “chain” button;
• Zooming in and out of spectrogram is done by mouse scroll. However, zooming
is only available after corresponding zoom levels are generated as mentioned
at the start of paragraph;
• Navigation on waterfall graph is possible with mouse drag, keyboard arrow
keys, “Home” and “End” keys;
• F5 key forces to reload waterfall data. Similar effect can be achieved by
zooming and panning waterfall graph.
Examining spectrum lines of spectrogram
It is possible to view distinct spectrum trace from spectrogram in frequency range
spectrum chart.
In following image spectrum trace from spectrogram is shown in black:
To view spectrum trace from spectrogram following conditions must be met:
• Spectrogram must be linked (“chained”) to frequency range spectrum
(4.1.19)
• User must select spectrum trace of spectrogram to view. Initially it is done
by double clicking on desired location of spectrogram.
61
After initial spectrum trace selection, it is possible to move trace selection up or
down in time domain by keys “Ctrl+Up” or “Ctrl+Down” when spectrogram window
is selected.
Marker at time corresponding to selected trace is added to Field strength versus time
chart:
Aural monitoring
• When measurements are paused, aural monitoring is possible. To enable it,
the frequency detected during monitoring may be sent to the receiver
together with the relevant receiver settings of the particular frequency. To
do this, the entry in signal detection results list should be double-clicked or
pressed on the “ENTER” key;
• The volume of the receiver speaker may be controlled by the context menu
of the button (A.12) at the lower left of the software window. The default
62
volume may be set prior to measurements in the settings section (Error! R
eference source not found. and Error! Reference source not found.).
Reporting frequency usage statistics to Skudra Server
• Functionality of reporting frequency usage statistics is designed for periodic
(in user set time intervals) storing of frequencies and count of detected
signals into Skudra Server. Goal of such recording is to provide Skudra Server
with immediate information about changes in spectrum usage;
• Frequency usage statistics are recorded in Skudra Server for selected ranges
that have marked option “Report statistics” in Measurement range list (D.1);
• Each measurement range has statistics recorded separately, and for each
range it is possible to set individual reporting;
• To perform reporting of statistics a valid Skudra server authorisation token is
necessary;
• In order to get Skudra Server authorisation token it is necessary to set
appropriate link in field “Skudra Server name”. Next it is necessary to fill
fields “Skudra Server user” and “Password”, and confirm request of token by
clicking “accept (See section 4.2.7);
• In case of commencing measurements set to include statistics reporting
without a valid authorisation token, software will display authorisation
window requesting to renew authorisation token by providing Skudra Server
username and password;
• By providing valid Skudra Server username and password and clicking “OK”
new authorisation token will be obtained and stored in Skudra Patrol and
measurements will be started. Providing invalid Skudra Server username and
password user will be asked to enter credentials repeatedly. Choosing option
63
“Cancel” will display dialog to confirm cancelation, confirmation of which
will cause measurement session not to start;
• According to result of authorisation Skudra Patrol information roll will show
message either “Initialising statistics failed!” or “Successful authorisation,
token saved”;
• If during the measurements authorisation token cease to be valid or expires,
acquisition of new token is prompted, similarly as when commencing
measurements, by authorisation window;
• Reporting statistics to Skudra Server without valid token is not possible.
However, if authorisation token expires during the measurements, calculated
statistics will be temporarily stored in Skudra Patrol until valid authorisation
token is acquired and then reported to Skudra Server. The same is true if
connection to Skudra Server has been lost;
• Reporting statistics stored temporarily in Skudra Patrol may take a while,
therefore progress report will be indicated in Skudra Patrol information area
(A.13);
• Choosing to cancel reporting statistics by clicking “Cancel” in authorisation
window or closing Skudra Patrol software during reporting of temporarily
stored statistics will cause loss of statistics that had not been reported by
then;
• Calculation of frequency usage statistics from uploaded Skudra Patrol
measurement results is foreseen in functionality of Skudra Server.
64
The Functionality of Settings
Saving settings
• Measurements are done with settings displayed at the start of measurements.
During measurements settings can not be changed.
• Settings (with exceptions mentioned in the next clauses) are saved
commencing measurements and closing the software;
• Frequency licences stored by the software, calculated taking into account
the monitoring site’s parameters, are stored immediately upon loading;
• Changes to the specific frequency file are saved immediately upon updating
them from the signal determination result list (A.10) as well as clicking the
save button in the list of specific frequencies group
• Changes to the range setting edit list (D.1) will be saved same as other
settings upon commencing measurements and closing the software. The save
button is provided to save the range settings in a separate file;
• The Skudra Server user password is not saved. The token acquired during
authorisation will be saved with other settings upon commencing
measurements and closing the software.
System Settings
• Usage of equipment - Setting sets whether to use receiver and direction
finder simultaneously (option “Simultaneous scanning and DF with separate
receivers”), which implies that separate receiver and direction finder is
available, or to use single receiver for scanning and direction finding (option
65
“Sequential scanning and DF with same receiver”). In later option DF (IP:port)
will be used as scanning receiver’s IP address.
• Receiver (IP:port) – Receiver IP address and port for scanning should be
entered in the format IPv4address:Port or IPv6address:Port. The port of
currently supported receivers is either “5555” or “5300”. If the receiver’s IP
address is not known, refer to the receiver’s user manual. Option is not
available is “Sequential scanning and DF with same receiver” is selected, as
then Direction finder is used as receiver.
• To check the connection to the IP address and determine the receiver’s model
click the “refresh” button next to Receiver (IP:port). In case the IP address
will correspond to a receiver supported by the software, the receiver model
will be displayed, else, if the IP address will belong to a different equipment
- “receiver is not supported”, but if the connection with the IP address will
fail – “connection failed”. If “Sequential scanning and DF with same receiver”
is selected, IP set in DF (IP:port) will be used.
• DF (IP:port) - The Direction finders IP address and port should be entered in
the format IPv4address:Port or IPv6address:Port. Use of direction finder is
not mandatory, it is required only direction finding is enables for
measurement ranges (4.3.9) or sequential scanning and DF with same receiver
is selected;
• To check the connection to the IP address and determine the direction
finder‘s model click the “refresh” button next to DF (IP:port). In case the IP
address will correspond to a direction finder supported by the software, the
DF antenna model and current settings (see 4.2.2.1) will be displayed, else,
if the IP address will belong to a different equipment - “Is not valid Direction
finder!”, but if the connection with the IP address will fail – “connection
failed”;
• DF duration between scans (s) – If “Sequential scanning and DF with same
receiver” is selected, it is necessary to set time window (seconds) for
direction finding after each full scan of all measurement ranges is completed.
If “Simultaneous scanning and DF with separate receivers” is selected, this
setting has no effect and is disabled.
• Azimuth and location: Provides three options for azimuth correction and GNSS
location usage. Receiver is configured with corresponding settings only when
measurements are started. However, as settings are not changed back to
previous state after measurements, that should be considered when using
receiver with software other than Skudra.
▪ Fixed azimuth correction without GNSS location – Fixed north
correction as set manually on receiver is used. Coordinates set Skudra
are used.
66
▪ Compass azimuth correction with GNSS location – Direction finding
results are corrected with compass values internally by direction
finder, compass magnetic declination is obtained by GNSS
coordinates. If “Report DF to Skudra Server” is selected in “Triggered
DF configuration” (4.3.9), direction finding results sent to Skudra
server after each direction finding measurement are accompanied by
current GNSS coordinates (For information in detail see 5.3.1).
▪ Course over ground azimuth correction with GNSS location - Direction
finding results are corrected with GNSS course over ground values
internally by direction finder. If “Report DF to Skudra Server” is
selected in “Triggered DF configuration” (4.3.9), direction finding
results sent to Skudra server after each direction finding measurement
are accompanied by current GNSS coordinates (For information in
detail see 5.3.1).
Direction finding results stored locally on Skudra Patrol and if necessary
later uploaded to Skudra server are always referenced only to coordinates
set on Skudra Patrol before start of measurements.
• Additional azimuth correction – All direction finding results gathered from
direction finder are corrected by value set here, regardless of whether they
have been already corrected internally in direction finder by fixed value,
Compass or GNSS course over ground. Setting additional azimuth correction
to zero degrees, effectively disables additional correction.
• The folder where results of measurements should be saved is indicated in the
window “result’s folder”. If the folder turns out to be inaccessible a pop-up
warning will appear. The results folder can be changed by clicking the “open”
button at the folder window and choosing the desired folder;
• The measurement should distinctively named in the input field “Measurement
session”. The name given will be used in the result file name, thus the
symbols used are limited to the characters supported by the computer’s file
system;
• The button “eye” is intended to display the contents of the window
“Measurement session” in the software’s measurement section under the
measurement range list.
67
• Type (Measurement session type) dropdown allows to set measurement
session type by which measurement results can be filtered after uploaded to
Skudra Server. Values available for selection (e.g. fixed, mobile,
transportable) are fetched from Skudra server at updating server sites, and
authorising and several other occasions. For saved measurements it is possible
to change session type in information tab;
• The input field “Antenna factor” and “cable attenuation” accordingly show
the antenna factor and cable attenuation files loaded into the software, and
their covered frequency range;
• The antenna factor and cable attenuation files may be replaced clicking the
button “open” next to the file window and choosing the necessary file. As
soon as a new valid factor file is chosen it is saved to the software’s memory
and it doesn’t have to be repeatedly read.
4.2.2.1 Current settings of DF equipment
By clicking “refresh” button by “DF IP(port)” textbox, device by set IP address will
be identified.
If device corresponds to supported direction finder DF antenna, Compass and GNSS
configuration will be displayed. Configuration is shown as it is, and some (see 5.3.1)
of settings may change after commencing direction finding.
If direction finder is currently set to fixed operation following message will be
displayed:
68
By selecting “Yes” receivers location source will be temporarily set from fixed to
GNSS and GNSS coordinates gathered, and location source returned to previous state.
Previous message is shown only, if receiver has GNSS capability.
After that current settings of DF equipment will be shown:
• DF antenna - Currently connected main direction finding antenna;
• DF settings – Set polarisation and amplifier mode. Some direction finders
allow setting polarisation and amplifier for antennas that do not support
switching, therefore value may be incorrect;
• Corr.(Compass) – Compass currently used for north correction of bearing
results. “-” value means that no compass is used.
Configuration when no compass is used means direction finder uses fixed DF
correction set in GUI:
69
It is important to note that “Use North Correction” for Skudra PATROL is effective
only if use of compass is disabled (corresponds to “Use Compass” setting in eb500).
If checking direction finder when bearing is currently corrected by compass following
message will be displayed:
• Corr.(Compass) – Compass currently used for north correction of bearing
results. Selected compass is followed by available compasses in scopes. If
physical compass is not available, direction finder can provide “Course over
ground” (COG) compass, if there GNSS device available, or “Software”.
“Software” option is available always, however is not used by Skudra PATROL;
• Mag.declination – Source for magnetic declination of compass values.
(Always set by Skudra PATROL to GPS)
70
• GNSS source – Source for direction finder’s coordinates. Options are manual
(fixed coordinates set in direction finders’s GUI), which are not used by
Skudra PATROL in direction finding process, or physical GNSS devices
connected to direction finder. Selected GNSS source are followed by available
sources in scopes.
Regardless of whether direction finder has DF antenna connected or even DF
option installed, coordinates (if available) of direction finder is read from
direction finder:
• Coordinates (decimal N/E) – Coordinates available from direction finder,
which can be set as measurement session coordinates, if accepted in user
dialog.
Editing of measurement session type for saved measurements
• Measurement results after uploaded to Skudra Server can be filtered by
measurement session type;
• If measurement session type set for saved measurement are not supported by
Skudra Server (e.g. at first use or recent server changes) uploaded
measurements no session type will be set;
• However, for saved measurement, it is possible to change measurement
session type in information tab/ Session type part in Settings treeview.
Selection made in “change session type to” dropdown will be set as new
measurement session type for saved measurement.
71
Configuration and import of licence database
The group of frequency licence loading comprises all functionality necessary to
determine the theoretical field strength of the stations detectable at the monitoring
site and their assignment’s parameters, as well as to determine the radiofrequency
application corresponding to the frequency channels. By the theoretical field
strength it is determined whether it is possible to receive the emissions from
assignments transmitter at the monitoring site;
• Licence database information can imported through licence file of
documented format (6.1.2), by clicking “folder open” button next to the
“Licence database file” and selecting corresponding file. However, it easier
to download database information directly;
• Authorised (4.2.7) user can download licence database information directly
from Skudra Server in frequency range set in “Licence database download
range” input field and validity period set in “Licence database download
period” input fields by clicking download button next to it;
• As download of licence database information can take some time, it is done
in background and progress is reported in “Licence database file” input field;
• The theoretical field strength value of the assignment at the monitoring site
is calculated by the Hata-Davidson method, using the monitoring site’s
coordinates, receiving antenna height, the monitoring environment
characteristics. Licence selection is explained is detail in 4.5;
• In computers running WINDOWS 10 or higher it is possible to get the
monitoring site coordinates from the information stored in computer’s
operating system by clicking the button “satellite”;
• Changing the monitoring site’s characteristics (i.e., everything except the
licence database information) the site’s characteristics will be changed
temporally indicated by highlighting the parameter in red. To recalculate the
theoretical field strength the button “refresh” should be clicked or the
licence database file should be reloaded by clicking the button “open” or
72
“download”. If recalculation is not done, the changed settings will be lost
next time the software restarts.
Clicking “Refresh” will also set monitoring site location on frequency
assignment map in measurements tab, provided that no previously made
measurement is open;
• In the window “specific frequency file” a file is indicated that contains
information on assignments not linked to any particular frequency or do not
require an individual licence. The specific frequency file may be changed
clicking the button “open” and choosing the necessary file. After changing
this file it is not necessary to recalculate the transmitters detectable at the
monitoring site;
• Contents of the specific frequency file loaded to the software are displayed
in the group “specific frequency list” (4.2.6);
• The file containing information on the radiofrequency applications
appropriate to the frequency bands is displayed in the window “Application
file”. The corresponding “xlsx” file of the necessary country may be
downloaded from the web site www.efis.dk. Application search results
exported to XLSX (country as columns) are supported (6.1.4). The
radiofrequency application file may be changed clicking the button “file
open” to the left from textbox and choosing the appropriate file; Additionally
older EFIS “csv” format is supported
• The licence database file, specific frequency file and application file
information may be deleted from the software by clicking the buttons
“delete” to the right from the appropriate file text fields. After deletion of
the file information, the recalculation of detectable transmitters at the
monitoring site is not necessary.
Frequency use licence recalculation (update of results)
• During measurements, information about most probable licences, the
theoretical signal field strength corresponding to licences, monitoring site
coordinates, and other information shown in the group “Configuration and
import of licence database” (see section 4.2.4), as well as values in the range
settings list column “Licence detection” are linked to the signal detection
results.
• In order to recalculate earlier results (e.g. with an updated licence database
file) the button “refresh results” (B.5) should be clicked; To update the
measurement results according to the newly loaded frequency licence
73
settings, the measurement results should be saved and opened as an archive
file;
• If different licence detection thresholds are necessary, appropriate change
have to be made in input fields “Min. field strength” and “Guaranteed
distance” shown after selecting “Measurement range list” in “Settings”
treeview (B.1). Changes will be indicated to the archived measurement range
settings table (B.2) in red.
• After implementing the neccessary changes to the column “Licence det.”,
and clicking button “Recalculate results” (B.5) - the results will be
recalculated according to the updated licence information and settings. A
pop-up message “Detection results recalculated” will appear;
The List of Specific Frequencies
• In the group “Specific frequency list”, it is possible to view and edit the
contents of the of specific frequency list, i.e., frequencies of assignments,
the licences of which are not linked to specific frequencies, or which do not
require an individual licence;
74
• The list of specific frequencies may also be appended from the list of
detected signals (A.24) by selecting the result’s context menu “to the
specific frequency list” (A.10);
• The list of specific frequencies comprises three columns:
▪ Frequency – the frequency of the channel (Hz),
▪ User – the user operating the corresponding entry’s frequency, the
equipment, the radio communication service or other information,
▪ Em. class - the class of emission corresponding to the frequency entry
and user. Filling this column is not mandatory and it’s contents are
purely informative;
▪ Span(kHz) – frequency span of assignment. Any frequency in set span
is considered related to set user;
• The list of specific frequencies may be sorted by column, clicking the header;
• Changes to the list of specific frequencies may be done by direct editing of
the entries. To save the changes and use them in measurements the button
“Save” should be clicked;
• The list of specific frequences may be appended or a highlighted entry
deleted correspondingly clicking the buttons “+”and “-” . In order to apply
the changes to measurements, they must be saved by clicking the button
“save” .
• Clicking button “save” saves changes made to “specific frequency list” to the
file that is loaded at “Specific frequencies’ file” (4.2.4), therefore, to save
previous edition of specific frequencies file, its copy have to be made
manually.
75
Interaction with Skudra Server
To upload results, exchange sample spectra, download licence information, store
waterfall spectrograms, report statistics, report DF results or register for remote
control it is necessary to acquire an access key to Skudra Server;
• The Skudra Server access token may be acquired filling the windows “Skudra
Server user” and “password” and confirming the key request by clicking the
button “accept” or pressing “Enter” key on password box ;
• The Skudra Server access token is stored in windows credential manager for
each instance (executable file) separately. The key may be deleted by
clicking the button “delete”;
• To be able to get the Skudra Server access token, valid Skudra SERVER name
(path) must be available;
• There is possibility that due to changes in Skudra server configuration some
of Skudra SERVER subpaths have been changed, they must be updated by
clicking refresh button next to Skudra SERVER name input field;
Map storage
• OSM maps are used to display the licence information;
76
• Maps may be used offline, when the map saved by the software is used, or
online when the map is acquired from OSM servers. Changing from offline
mode to online mode and vice-versa is done clicking the button
“Offline/Online” .
• Tiles of the map viewed online are saved in the software’s memory;
Preloaded maps are available at Skudra software download site as zip files. To
use downloaded map user have to overwrite Skudra/Core/karte folder with one
contained in downloaded zip file.
However, it is possible to create maps using Skudra Patrol functionality:
• In order to fetch the offline maps, click the button “Prefetch”. After clicking
the appropriate button map fetching will begin within the borders of the
current map displayed in the measurement section map “licences for
particular frequency” (A.14),;
• A confirmation for each zoomed-in layer download will be asked, and
download progress will be displayed;
• If the next zoomed-in layer’s download is not confirmed, the map’s download
will stop. Each downloaded layer is saved before commencing the next
download.
77
Measurement Ranges functionality
• The range settings define the bands that will be scanned during
measurements, as well as their parameters;
• Summary of set measurement ranges is displayed in Measurement range list.
List is not editable directly (except use check box), but selection of particular
range in list provides editorial controls. It is possible to edit several ranges
together by selecting more that one range;
Receiver settings
Parameters available to set for each range:
• Use – does the range need to be scanned during measurements. This is only
parameter settable in measurement range list;
78
• Frequency range name – the range’s name will be listed in the signal
detection result list to distinguish frequency channels where measurements
were done in the framework of different bands overlapping by frequency;
• Start/end frequency – The range edge frequencies in MHz. When choosing the
start and end frequencies, range overlapping is allowed, even several
identical bands are allowed. The software automatically will not allow the
start frequency to exceed the end frequency;
• Channel step – four measurement frequency steps are available in the
software:
▪ 100kHz/200kHz – for signals containing their characteristic features in
a range of 200 kHz and signals observed are aggregated in a step of
100 kHz (typically FM broadcasting)
▪ 6.25kHz/25kHz - for signals containing their characteristic features in
a bandwidth up to 31.25 kHz and signals observed are aggregated in a
step of 6.25 kHz (typically private land mobile service)
▪ 6.25kHz/25kHzIQ - identical to 6.25kHz/25kHz, except that spectrum
is calculated on user computer from IQ data, which may greatly
improve scanning speed, however that also requires high processing
power and connection bandwidth (speed) between receiver and
Skudra. Channel step is not available for SignalShark, ESMB, EB200 and
EM550 receivers
▪ 1MHz/25MHz - for broadband detection using machine learning
(5.2.2), for signals containing their characteristic features in a range
of 25 MHz and signals observed are aggregated in a step of 1 MHz, still
channel frequency is specified in detection process to 250 kHz
(typically used public mobile service and dvb-t)
▪ 10MHz/100MHz – initially reserved for jammer detection (5.2.4),
signals observed are aggregated in a step of 10MHz, and stored in
100MHz, 250 MHz or 500MHz bandwidth
79
However, jammer detection and mask detection options (but not narrowband
detection, broadband detection) are available regardless of channel step;
• RF Input – Setting is valid for receivers which have multiple RF inputs
available. Selected input (except “-”) is switched for each frequency range.
When “-” option is selected, no action (switching) is taken. Only “-” option is
available for receivers with single RF input. Value “0” is not the same as “-”!
With “-” no switching will take place, but with “0” first RF input will be
switched for R&S receiver.
• Attenuator – The setting of the receiver’s attenuator.
• IF attenuator – The setting of the receiver’s intermediate frequency
attenuator.
• Antenna ctrl. – Antenna polarisation and amplification setting. When set to
“-” value set previously will be used. However, if same receiver is used for
direction finding and scanning, corresponding equipment value may be set by
DF equipment settings.
• Available options for RF Input, Attenuator, IF attenuator and Antenna ctrl.
depends on the receiver properties. The parameter’s menu shows values
available to the receiver set in “Receiver type” menu in Ranges tab.
Licence detection configuration
• Guaranteed distance – Distance in km from the monitoring site, where all
assignments are considered valid. This parameter does not limit (filter)
accessible assignments, it shows additional assignments, which in cases (e.g.
FM broadcasting) when all transmitter parameters are known, are not
necessary. At high values (>30km) this can introduce additional errors in
determining the assignment. The value is practically applied to finding the
mobile station assignment in a large territory (e.g. in a large city);
• Minimum level – theoretically calculated threshold of field strength
(dBµv/m), exceeding which the assignment is considered detectable at the
monitoring site. Adjustment of this parameter is foreseen in sites of unusually
high or low noise level to refine the amount of assignments determined
automatically;
Narrowband signal detection configuration
80
• Narrow band detection is available only for 6.25kHz/25kHz, 6.25kHz/25kHzIQ
and 100kHz/200kHz channel steps;
• Correlation squelch – The squelch value is from zero to one. To detect a signal
the squelch value is compared to the maximum squared correlation
coefficient achieved doing Pearson’s correlation with sample spectra.
• Noise squelch – Squelch value in dB over noise. The noise squelch is used to
determine the frequency channels where signals should be further detected
using correlation;
Mask signal detection configuration
• Mask detection is available for any channel step;
• It is is possible to use two masks: maximum mask for detection when signal
overshoots mask and minimum mask when signal undershoots mask;
• For both maximum and minimum masks mask type can be set to “OFF”, fixed
squelch “Squelch (dB)” and to user defined mask;
• If mask detection is set to fixed squelch, no user defined mask is necessary,
and signal level is compared to value (in dBuV/m) set in textbox to the right
of mask type dropdown;
• To use mask detection with user defined mask, spectrum mask must be
generated (5.2.3 and 4.7). List of user defined masks compatible to selected
spectrum range (start frequency, stop frequency, channel step combination),
if any, is shown in dropdown bellow options “OFF” and “Squelch(dB)”.
• Channel step for mask detection is independent for measurement range
channel step and it will override signal aggregation channel step expected for
measurement range channel step;
• Mask detection’s channel step divisor enables non integer channel steps, for
example 25kHz/3 =8.333 kHz;
• Mask detection bandwidth (BW) is set to compare signal against mask only in
set bandwidth in the center of channel. For example, it can be used to
compare mask to signal only at stable part of signal (carrier frequency).
• Practicaly spectrum in mask detection bandwidth contains more that single
spectrum point. It may be relevant (for example spectrum changes due to
81
modulation) whether mask is overshoot by all spectrum points (100%) or just
single point (0%). Overshoot/undershoot percentage can be set in textbox to
the left of mask type dropdown, if user defined mask is selected;
Jammer detection configuration
• Jammer detection is available for any channel step;
• In depth guidance selecting parameters for jammer detection is provided on
5.2.4;
• Noise squelch determines neccessary interdecile range of emission’s
spectrum in 0.5 MHz, 2 MHz, 10 MHz or 20 MHz bands (respectively for
6.25kHz/25kHz, 10MHz/100MHz, 100kHz/200KHz and 1MHz/25MHz channel
steps), to proceed to jammer detection;
• Carrier spacing determines ranges of carrier spacing (periods) to be
considered related to jammer. Values are in format is “period1start –
period1end; period2start – period2end;…”. It is possible to add predefined
carrier spacing exclusions for GSM, LTE, 5G by pressing respective buttons;
• Car. specificity determines how much more power must be concentrated in
particular periodic carrier frequency, compared to average of other periodic
components. Practical value for jammer detection may be 1 to 2;
Broadband signal detection configuration
• Broadband detection is available only for 1MHz/25MHz channel step;
• In depth guidance selecting parameters for broadband detection is provided
on 5.2.2 and 4.6;
• To use broadband detection ML model must be imported (4.6). Dropdown box
provides list of currently imported ML models;
82
• Noise squelch determines level difference of spectrum sample to be used for
broadband detection. Generally, it is appropriate to use value similar to one
used when fitting model;
• Broadband detection provides probability value of signal being detected in
range from 0 to 1. Probability squelch determines, whether emission to be
regarded as signal depending on the probability value;
Statistics and spectrogram configuration
• Report statistics – enable functionality of reporting statistics to Skudra Server
and set reporting interval (seconds).
• Spectrogram storage enables recording (and display) of waterfall
spectrogram. Spectrogram can be stored on local computer, on Skudra Server
or both;
DF scanning configuration
“DF scanning” provides direction finding for all channels of spectrum currently
scanned, with delay of only 50ms-150ms, or simultaneously for DDF550 direction
finder.
• DF scanning requires that direction finder supports wideband DF, e.g. it is
possible to direction find all frequency channels within receiver’s Realtime
bandwidth simultaneously.
• Some direction finders (EB500, DDF205) require wideband DF option for DF
scanning to provide direction finding results. Narda SignalShark does not
support wideband DF scanning.
DF scanning has two configurable parameters: Level squelch and Quality squelch:
83
• Level squelch corresponds to value Threshold (dBuV) set in receiver’s GUI in
Normal DF mode. Value limits are -50 to +130.
• Quality squelch (%) configures threshold for bearing quality. Direction finding
is successful and result is output only if direction measured, has quality higher
or equal to that set in Quality squelch(%) textbox.
DF results gathered during DF scanning are added to signal detection results,
provided that signal has been detected on particular frequency channel.
With DF scanning, to provide delay as short as possible between spectrum
scanning and direction finding (if not simultaneous operation), spectrum scanning
and direction finding use the same settings for both operations. Therefore:
• Parameters that influence spectrum scanning results, also influence direction
finding results.
• DF equipment settings (4.3.10) has no effect on DF scanning results.
As Scanning DF is performed with low delay after scanning or even
simultaneously, that is before signals have been detected:
• Triggered DF configuration (4.3.9) has no effect on DF scanning.
Triggered DF configuration
84
• If enabled triggered DF, direction finding on each signal detection event that
trigger conditions is requested (5.3);
• Trigger conditions are minimum field strength of aggregated signal, minimum
count detections in particular frequency channel and frequency channel
characteristics, which includes whether there is no licence associated to
frequency (“NRS”), whether frequency is contained in DF list (“listed”), and
no condition (“any”);
• DF list contains frequencies in MHz, for which only direction finding will be
requested, if trigger condition “listed” is selected. Multiple frequencies can
be added to DF list from clipboard, or added after keyboard shift-enter
combination;
• Dwell time determines how long each DF request is carried out. During the
dwell time many df measurements may be performed, in such case one most
probably direction is output;
• Direction finding is successful and result is output only if at least one direction
measured, has quality higher or equal to that set in quality(%) textbox. Also
directions bellow quality(%) textbox value, are not included in calculation of
most probable direction;
• It is possible to send each direction finding result in realtime to Skudra server
by enabling Report DF to Skudra server (5.4). This functionality is separate
from sending direction finding histogram as part measurement results.
DF equipment settings
Df equipment (Direction finder’s) settings are crucial to attain correct direction
finding results. Therefore it Skudra provides functionality to DF equipment settings
for each measurement range.
DF equipment settings is available if “DF type” in Measurement range list is set to
value other that “-” and Triggered DF if enabled for selected range.
85
• Values set in DF equipment settings are used direction finding signals found
scanning corresponding range.
• For some settings “-” value is available, which means that value already set
in direction finder by other means (e.g. GUI) will be used. However, when
using same equipment for direction finding and scanning, settings relevant
also to direction finding may be set during scanning by receiver settings
(4.3.1)
• Settings not available for selected direction (regardless of antenna) finder
are greyed-out.
• Threshold (dBuV) corresponds to value set in receiver’s GUI in Normal DF
mode. Value limits are -50 to +130. In contrary to trigger conditions’ “field
strength” this is value set directly to direction finder.
Editing the range setting list
• The range settings available depend on the receiver specification. The range
editing list contains values available to the chosen receiver;
• If a different monitoring receiver is chosen in the menu the new receiver
supports a parameter in the range list, the parameter is left unchanged. In
the opposite case, the available value of the parameter closest to that
previous one is set;
• By clicking the Receiver type “refresh” button, the receiver having the IP
address set in “Receiver (IP:port)” will be automatically be chosen and set in
the Receiver type menu. However, if “Sequential scanning and DF with same
receiver” is opted, IP set in “DF (IP:port)” will be used;
• By clicking the DF type “refresh” button, the direction finder having the IP
address set in “DF (IP:port)” will be automatically be chosen and set in the
DF type menu.
• By clicking the button “add range” (“+”), the measurement range editing list
will be appended by a new entry with default settings of the receiver chosen
in menu.
• By clicking the button “delete range” (“-”), the highlighted entry will be
deleted from the measurement range editing list.
• By clicking the button “open” (open folder icon) and selecting an earlier
saved range setting file you may load this to the software.
• By clicking the button “save” (floppy disk icon) the software will offer to save
the currently presented bands in a user named file for it’s future loading into
the same or other instance of software by clicking the button “open”.
86
The Sample Spectra Functionality
To determine signals correctly, a sufficient stock of sample spectra is necessary. The
majority of signal types need their own sample spectrum. The more sample spectra
is available, the higher the correlation coefficient and the more it will differ from
increased noise or out of range emisssions, leading to better signal determination.
The collected sample spectra section is created for spectra sample analysis and
creating new sample spectra.
Adding and Displaying Sample Spectra
• Data defining new spectrum are taken either from the cumulated signal
spectrum or spectrogram. Type selection for sample spectra source is made
by toggling button “Source: POLY” or “Source: WF” respectively.
• If cumulated signal spectrum source is selected, then before defining a new
sample spectrum it must be ensured that the corresponding record is
highlighted in the signal detection result list;
• If spectrogram source is selected, refer to section 4.4.2 for details on setting
frequency and time of sample source;
• To start a new sample spectrum project, the button “load” (E.12) should be
clicked. The sample spectrum curve lies within the maximum values of each
frequency component’s cumulated spectrum that falls within the 90% interval
assuming that the dispersion of values follows a Gaussian distribution.
(Inaccurately, but simpler – 90% of the maximum value);
87
• In the process of creating a sample spectrum project, several curves are
plotted in the sample spectra display and defining graph (E.2), differing by
frequency offset. The calculated sample spectrum “measurement” without
frequency offset (E.5) is displayed, and, depending on the sample spectrum’s
range’s step, sample spectrum with a frequency offset corresponding to the
centring of the signal in the 200 kHz range (E.6) or two sample spectra with
a frequency offset corresponding to the centring of the signal in the 31.25 kHz
range (E.7) and 12.5 kHz (E.8);
• By selecting a sample spectrum on the graph with the left mouse button, it
is possible to adjust the automatically determined frequency offset with the
buttons “left” (E.10) and “right” (E.11);
• The automatic and manual sample spectrum offsets are shown in the group
“Sample spectrum information”, respectively, “Central frequency offset”
and “User set offset (points)” (E.21);
• The group “Sample spectrum information” also displays the information
”Additional correlation count” (E.22), which characterizes the number of
correlations necessary to the project (value exceeds 1 for most spectra
containing multiple carriers);
• The manually corrected offset may be reset by clicking “refresh” (E.13);
88
• When creating a sample spectrum project, the sample spectrum usage
statistics chart (E.3) of the closest signals to the source of the new sample
are also shown. Only those sample spectra are shown in the chart rows that
were detected as the closest signals, including occurrence count (E.9). The
chart can also display how often a particular sample spectrum is used in
various frequencies. To repeatedly view the source sample spectrum source
spectra statistics, the button “refresh” (E.13) should be clicked;
• In order to add the sample spectra project to the list of sample spectra, the
button “confirm” (E.14) should be clicked, and the columns ”information”,
“Use” and “Em. Class” should be filled-in directly in the list of sample spectra
(E.1).
Sample spectra source: Spectrogram
It is possible to define new sample spectra either from cumulated spectra or
spectrogram. Spectrogram source provides advantage that sample spectrum can be
selected from single signal spectra contained in long term measurements. For
example, it is possible to select the single spectrum in days’ worth of scanning, that
was not correctly detected as signal, and use it to fine tune the sample spectra
database.
To be able to set sample spectra source from spectrogram it necessary to:
• Create new or open stored measurement result, that is measured with
spectrogram storage “Locally” enabled (4.3.7),
• Select and show in frequency range spectrum chart particular spectrum trace
from spectrogram (4.1.20),
• Select frequency (signal) of interest in frequency range spectrum chart by
zooming and centring on respective frequency.
• Spectrum at center of frequency range spectrum chart will be used as sample
source, when user clicks button “load” (E.12) at sample spectrum generation
process (4.4.1)
The list of sample spectra
• The available sample spectra with their parameters are displayed in the list
(E.1) in columns:
▪ Information – A description of the sample spectrum, e.g., the model
of the emitting equipment, radiofrequency application or spectrum
description. A unique identificator is allocated to each sample spec-
trum, thus several sample spectra may have the same description.
▪ Use – A checkmark indicating the particular sample spectra is in use
by the software to determine signals. Unchecking this parameter
89
enables temporary disabling the particular sample spectra without
deleting it;
▪ Em. class – The class of emission associated with the sample spectrum
is used to predict the measured signal’s class of emission. The class of
emission in the signal determination results corresponds to the most
often observed sample spectrum most closely resembling the signal;
▪ Step – sample spectra differ significantly depending on the frequency
channel step (thereby of frequency ranges and the typical signals in
the range). To efficiently use the computer’s processing power two
goups of sample spectra are used – one for frequency ranges with a
channel step 6,25 kHz and the other for frequency ranges with a
channel step 100 kHz.
▪ Corr. – Correlation (coefficient of determination) between the
cumulated sample spectrum and the spectrum project created from
measurement results. The correlation column’s entry is blank when
no sample spectra project was acquired, when the sample spectrum
project was acquired at a frequency channel step not conforming to
the sample spectrum, as well as if the ratio of the standard deviation
between the level values of the sample spectrum project and
cumulated spectrum is less than 0.67;
▪ StDev – The standard deviation ratio of the level values of the sample
spectrum project and cumulated sample spectrum. The columns
entry is blank when no sample spectra project was acquired and when
the sample spectrum project was acquired at a frequency channel
step not conforming to the sample spectrum;
• Correlation, sample spectrum and signal spectra standard deviation ratio
columns are blank if the range or point number does not match the spectrum.
The corelation column also is blank when the standard deviation of spectrum
level values is half of the sample spectrum standard deviation;
• The corelation and signal spectrum standard deviation of entries characterize
how well the sample spectrum matches the project sample source - how
precisely such as signal may be determined. Standard deviation characterises
the difference between lowest and highest level values in sample spectra –
whether sample is derived from low or high level signal.
90
• By highlighting a sample spectrum entry it is displayed as a sample spectrum
in the sample spectrum defining graph;
• The sample spectra list may be sorted by clicking the column headers.
Editing the sample spectra list and exchanging it with Skudra Server
Under the Sample spectra list is a group “Edit sample spectra list” for editing the
sample spectra list and it’s exchange with Skudra Server;
• To delete the highlighted sample spectrum from the sample spectra list the
button “delete” (E.16) should be clicked;
• To undo unsaved changes in the sample spectra list the button “refresh”
(E.17) should be clicked;
• In order to save changes to the sample spectra list so that they are available
also after restarting Skudra, the button “save” (E.20) should be clicked;
• In order to compare the sample spectra list to the saved spectra on Skudra
Server, the button “load” (E.18) should be clicked. When loading will
complete, entries both in the sample spectra list and in Skudra Server will
appear in black font, in red those only in Skudra Server and blue – only locally
saved spectra samples;
• To upload highlighted sample spectrum to Skudra Server, the button
“upload” (E.19) should be clicked. Only authorized users having acquired the
authorization token from Skudra Server may update the sample spectra
database. If a sample spectrum is already stored in the database, no copy
will be added. A pop-up message on the upload results will appear.
91
• Upon clicking the button “information”, the distribution of sample spectrum
use across different frequency channels will appear on the chart Sample
spectra statistics (E.3). The distrubution rows comprise all frequency
channels where the highlighted sample spectrum was identified as the most
alike. Each row is also marked how often the spectrum has been identified.
The functionality of the frequency assignment
database
Upon clicking the button “import licence database file” (Error! Reference source n
ot found.) , “Licence database download” or “recalculate licences” (Error!
Reference source not found.) the table of valid licences at the monitoring site is
calculated. The array of valid licences is calculated by the following algorithm:
• The theoretical transmitter field strength at the monitoring site is calculated
using the Hata-Davidson radio wave propagation model (TIA TSB-88A), based
on the following input data: frequency, effective radiated power of the
transmitter, distance, antenna height, propagation environment at the
monitoring site, the receiving antenna’s height;
• The theoretical field strength intensity is calculated for all transmitters
whose licences include coordinates, effective radiated power, antenna
height, class of emission;
• The user of the licence with the highest theoretical field intensity exceeding
the established field intensity threshold is considered as the most probably
92
detectable at the monitoring site. Additionally, the numbers of all other
licences over the threshold are stored for the use of Skudra Server;
• Using a geographical distance calculation method (not taking account of the
Earth’s curvature) from all the transmitters having coordinates in their
licences, only those are selected that are not farther then the established
threshold. If a valid licence was not established applying the previous clause,
the user of a licence with coordinates nearest to the monitoring site within
the distance threshold is considered valid;
• Additionally, the numbers of all other licences over the threshold are stored
for the use of Skudra Server;
• All licences without coordinates are considered valid everywhere and are
appended in parentheses to the list of valid licences at the monitoring site;
• Additionally, the numbers of all the licences without coordinates are stored
for the use of Skudra Server;
• Frequencies which are not found in the Skudra Server database, but are
included in the user-prepared file of specific frequencies are appended to
the array of valid licences;
• Additionally, for display in the measurement section’s map and manual
tweaking of the licence, all licence information is stored, their theoretical
field intensity at the monitoring site and their distance.
Functionality of Machine Learning
To use machine learning signal detection, corresponding function has to be enabled
for particular measurement range (see 4.3). One of the parameters that is necessary
to set in order to use machine learning detection is ML model. This paragraph
provides instructions on how to generate ML learning model.
Generation of Machine Learning models
Functionality necessary to generate ML models is available in “Machine learning”
panel;
Generation of ML model is divided into five steps. The first step is to select stored
spectrogram data (for measurement of spectrogram see ranges and waterfall
functionality).
93
Selection of spectrogram data is provided by “Browse files” button. In following open
file dialog, it necessary to select single or multiple zip files that are contained in
spectrogram folder. Opposed to selecting spectrograms for waterfall display, where
it is necessary to select folder, for ML model generation it is necessary to select files
inside spectrogram folder:
After selection of zip files and pressing “Open” button, information text box is filled
with names of selected files and number of samples they contain;
Second step is to select (identify) spectrum samples to be used for generation of ML
model based on difference between maximum and minimum field strength in each
sample. This removes samples without change of field strength from using further
steps which includes manual selection of samples that must be considered as signal.
Practical value of necessary difference between maximum and minimum field
strength may be considered 10 dB;
Third step is to reduce number of samples used for ML model generation, however
there no practical use to limit the number bellow 10000. User must pay attention to
set limit, because limit value is not automatically updated after identifying new
94
samples in second step. Reduction of data is commenced by pressing button “Load
to list” or “Save to file”. By pressing “Save to file” samples will be stored in file in
format, that will allow to load it to list later, including together with other files
(functionality in group box management of spectrum samples). Pressing “Load to
List” will load samples to list for selection of samples to be considered as signal:
Step 4 provides functionality to mark samples that must be considered as signals.
Correctness of this marks has direct influence on usefulness of resulting ML model.
For broad band signals, list will have several records for single signal. In such case it
is important to select only the sample record that is centred on signal, otherwise
broad band detection will detect signal not only on centre frequency of spectrum,
but also on offset frequencies depending on how samples was marked;
To support selecting samples to mark as signals, cumulated spectrum of sample is
shown for selected record, and also value of frequency offset from record frequency
(usable as additional guide to select between nearby records, when spectrum alone
is not definitive) is shown in column “offset” list of samples.
95
After marking samples that must be considered as signals, it advisable to save
marked samples to file for combined, by pressing “Save samples” button:
After successfully saving spectrum samples, corresponding information line is added
to information text box:
Saving spectrum samples to file provides possibility for later loading samples to be
used to fit ML model from several files. Those files can be created at different
channel, different antennas, different signal to noise ratios to provide most diverse
spectrum samples. By pressing “Load samples” can load all files deemed necessary
96
for fitting model. Samples contained in files will be added to “List of samples for
fitting model”. Any samples contained in “List of samples for fitting model” before
loading files will be lost:
When necessary samples are loaded in list and signals are marked, Fitting of ML
model can be started by Pressing “Start” in “Fitting ML model” group box:
Fitting Starts with selecting file for saving ML model. Selected file name will be used
to select available ML models, when defining broad band detection in Ranges panel;
After selecting model name fitting of model is started. At the end of fitting,
information on success of fitting in “Fitting ML model” group box is shown, for
example: accuracy, whose low values (<90%) sometimes may be sign of incorrect
marking of spectrum samples and confusion matrix, where number of cases when
negative truth (no signal) is predicted as positive (signal) can be seen;
97
Any ML model, previously or newly created, must be imported to be available when
setting measurement ranges in Ranges panel. Import of models is started by pressing
“Import models” button in “Import of fitted models for broadband detection” group
box.
Importing models provides possibility to select several ML models. ML models
previously imported will be unloaded, and only newly selected models will be
available for setting Broadband detection for measurement ranges:
98
Functionality of Mask Detection
Skudra Patrol provides two approaches to detection emissions above/below the set
limit. First is detecting emissions above fixed squelch field strength, regardless of
measurement range parameters. Second approach is to compare measured field
strength to spectrum mask that is specifically designed for frequency range defined
by its start frequency, stop frequency and resolution.
For mask detection with fixed squelch no mask generation is needed. Generation of
specific masks for particular measurement ranges is described in section 4.7.1.
Mask generation
Functionality of spectrum masks’ generation is available in “Masks” panel.
Skudra Patrol provides three data sources to generate spectrum masks:
• Maximum and minimum spectrum traces of currently displayed frequency
range spectrum in “Measurements” tab,
• Currently displayed spectrogram in “Measurements” tab (which is then used
to calculate maximum and minimum traces),
• Previously generated spectrum mask selected in list of masks.
To load source for mask generation corresponding mask source button must be
pressed. Availability of data source is noted in scopes on the mask data source
button.
If loading data from spectrogram, depending on size of spectrogram, maximum and
minimum trace calculation may take considerable time. Therefore, progress
percentage is shown load button as well as option to cancel calculation:
Also spectrogram data used for calculating maximum and minimum traces is limited
by time range displayed in spectrogram panel in “Measurements” tab.
99
Time limits can be used to exclude unwanted parts of spectrogram or to shorten
calculation time. However, user must also ensure that spectrogram is displayed at
all, otherwise no traces will be calculated:
After successfully loading maximum and minimum traces from frequency range
spectrum or spectrogram, corresponding ranges will be loaded in spectrum mask
definition chart:
If loading mask from list, selected mask will be loaded in spectrum mask definition
chart as ClrWrt/Mask trace:
100
In general, after loading source data, new mask template can be generated from
maximimum or minimum traces, or set as straight line by pressing corresponding
buttons:
However, this functionality can be limited by markers, as further described in (4.7.2)
Mask manipulation
Mask manipulations are available as soon as ClrWrt/Mask trace is available in
spectrum mask definition chart. ClrWrt/Mask trace can be added in following ways:
• By selection in list of masks. This function is available only if there are no
mask manipulation in progress and selected mask is compatible with
maximum and minimum traces loaded id mask definition chart,
• By loading selected mask from list (specifically pressing “Load from list”
button),
• From maximum trace (if loaded) by pressing “From Max”,
• From Minimum trace (if loaded) by pressing “From Min”.
101
Once ClrWrt/Mask trace is available, markers can be added to limit “Preparation of
masks” functionality in frequency domain. Markers can be added by mouse left-click
while holding “Ctrl” key. Other marker functions are the same as those of frequency
range spectrum (4.1.14), with exception that in Spectrum mask definition chart
markers can be added to ClrWrt/Mask trace only and middle marker is not set to
trace, and it is freely adjustable.
Further spectrum mask in frequency range between outer markers can be altered as
follows:
• Markers can be connected with straight line by pressing “Straight line”
button,
• Spectrum mask can be updated with values from maximum trace by pressing
“From Max” button,
• Spectrum mask can be updated with values from minimum trace by pressing
“From Min” button,
• Mask trace points can be increased by value (dB) set in textbox in the left by
pressings “+dB” button,
• Mask trace points can be decreased by value (dB) set in textbox in the left by
pressings “-dB” button,
• Mask trace can be broadened (each point is given value maximum value of
itself and two closest neighbours) by pressing “<->” button,
• Mask trace can be narrowed (each point is given value minimum value of itself
and two closest neighbours) by pressing “>-<” button.
If no markers are set, functions described above are deployed for whole frequency
range of mask.
Maximum and minimum values of spectrum mask is 120 dBuV/m and -30 dBuV/m,
respectively. Therefore, to shape spectrum mask’s base as straight line it is possible
to decrease values below -30 dBuV/m, where values will clipped, and then increase
values again.
102
Examples of mask manipulation:
Mask administration
Following mask administration options are available:
• Add generated (manipulated) mask to list. Mask name is proposed the same
frequency range name or spectrum mask name from which new mask have
been created. If mask with same name already exists “(1,2,3…)” is added to
the name,
• Overwrite mask selected in list with newly created,
• Delete selected mask from list,
103
• It is possible to name of selected mask in list, by directly editing the name
on the list.
• For mask to be used in remotedly controled measurements by Skudra Server,
it has to be set as “Used” by clicking checkbox in list of masks. Only one mask
with distinct Start frequency (F1), Stop frequency (F2) and Resulution (Res.)
combination can be set as used.
If mask manupilations render changes in spectrum masks for measurement ranges
set in Ranges panel, warning text “Spectrum masks for particular ranges have
been changed” is displayed on statusbar.
Mask names compatible to measurement range (with corresponding Start
frequency, Stop frequency and Resolution combination) is displayed and
selectable in Mask detection’s Max. mask/Min. mask dropdowns in Ranges panel:
104
Functionality of Remote Control
If set to remote control (4.1.1) operation, Skudra Patrol signal Skudra server for
acceptance of remote tasks and performs measurement according to received tasks.
• To set Skudra Patrol to remote mode, it is necessary to that user is authorised
(4.2.7);
• By toggling “Remote” button to enabled, remote operation is started in
following order:
o Skudra Patrol registers on Skudra Server as available for remote
control. Information registered contains computer host name and IP
address, location (N/E), receiver model and serial number;
o Additionally spectrum masks an machine learning models available at
local Skudra Patrol is registerd on Skudra Server;
o Skudra patrol requests measurement ranges set for particular
receiver/ computer at Skudra Server;
o If there are no set measurement ranges at Skudra Server, Skudra
Patrol idles until measurement ranges is added or remote mode
disabled;
• Measurement ranges set at Skudra Server are time limited (the have defined
start and stop times). If start time is set to be in future, Skudra Patrol start
measurement at set time (provided that remote mode still active) and stop
at stop time;
• If measurement ranges are edited or added at Skudra Server, Skudra Patrol
immediately receives notification and if necessary, updates measurement
ranges. If changes set at Skudra Server impact remote measurements
currently performed, measurement is stopped and results are saved and if
necessary new measurement is started;
• Informative message is displayed at status bar’s left side, informing that
remote control is active (“Remote control proceeding…”) and that “New task
received”, if Skudra Server has notified of changes in scheduled
measurements;
• Options available in measurement ranges (4.3), start and stop times, and
option to upload measurement’s results to Skudra Server is available at
Skudra Server;
105
• Information on currently remotely measured ranges and other settings is
available in “Stored measurement settings” panel(3.2).
Software operating principles
Measurement of range spectra
• Measurements are done in the chosen bands with start and end frequencies
set in the settings, with a defined signal attenuation and channel step. Other
spectrum scanning parameters are specific to signal determination and no
editing is foreseen. The bands selected cannot be changed during scanning;
• Scanning of the bands is cyclic - after scanning the last range scanning is
continued in the first range;
• Signal detection is done parallel to spectrum scanning, thus in real life the
scanning speed and repetition rate is determined by the performance of the
receiver.
Signal detection
Manipulation of the signal detection process during measurement is not foreseen -
the process depends on settings applied before the measurement (functionality of
settings and ranges).
Narrow band detection
• The receiver is controlled according to the chosen measurement bands.
Arrays of spectra blocks in the receiver’s FFT range are acquired;
• The noise level of each frequency block is determined by a practically
acquired algorithm;
106
• In cases when the emission levels in the frequency channels exceed the noise
level set to be the detecting threshold (squelch setting functionality), signal
search continues in the particular channel;
• In cases when the central frequency of an emission determined by a
practically acquired algorithm corresponds to the frequency channel under
investigation, the emission’s spectrum is compared to the sample spectra. If
not, the comparison will be done in the next channel or any other channel
where the signal central frequency will be located
• Comparison of spectra is done by Pearson’s correlation function. If the
correlation result’s determination coefficient exceeds the set value (setting
functionality), a signal (transmitter operation) is detected on the frequency;
• If frequency channels overlap (in case of 12,5 kHz and 31,25 kHz channels),
the channel with the highest correlation is considered to be detected.
Broadband detection
The sample spectra functionality is best suited for detection of signals whose
spectral shape is defined mostly by signal itself. That is not the case for broadband
signals, where received spectrum shape is influenced by multipath fading. To cover
detection of broadband signals Skudra Patrol employs machine learning algorithms.
• It is important to note that machine learning approach is highly dependant
on diversity of spectrum samples. For example, if model is fitted for dvb-t
signal, it won’t detect LTE signal. Further, if model is fitted for single dvb-t
signal, model’s applicability will be reduced, when there are two signals side
by side. The same is true for high power signals versus signals close to noise
floor or inside interfering signals. To accommodate various reception
scenarios, best way is to fit ML models using data obtained from drive test
(provides different signal to noise ratios and interference scenarios) and data
from different regions where different channel configurations exist;
• Output of ML model is 1 if emission classifies as signal, 0 – as not signal, values
between 1 and 0 denotes probability of emission being signal. If value of
probability reaches set probability squelch (see Prob. Squelch 4.3), emission
is considered as signal.
• Compared to correlation techniques used in narrow band detection, where
correlation values have continuous distribution, probability values tend to
have values closer to 1 or 0. Therefore limiting probability values has less
influence on detection of compared to narrow band’s correlation squelch,
and generally to change behaviour broadband model refitting is necessary;
• Before ML model is applied, value close to interdecile range of emission’s
spectrum in 25 MHz band, is compared to noise squelch (see Noise squelch(dB)
4.3). Detection of signal is continued with ML model only if noise squelch
value is reached. It is recommended to set noise squelch value close to that
107
used when fitting ML model (4.6.1), otherwise ML model would be used on
data it was not fitted for, which may yield unexpected results.
Mask detection
In general functionality of Skudra Patrol is aimed towards detection of actual
operation of transmitter at particular frequency. However, there are cases when any
emission or elevated noise outside above specified limits must be identified. Typical
use cases would be detection of out of band emissions form FM broadcasting stations
or detection of emissions in public mobile guard bands.
To meets these requirements Skudra Patrol provides functionality of Mask detection.
• Mask detection provides two detection directions - above mask (Mask. mask)
and below mask (Min. mask), which can be used separately or both together
and together with other detection types (for example, narrow band
detection).
• Mask detection is configurable to use fixed squelch with value in dBuV/m set
to the right of mask dropdown.
• Mask detection is configurable to use user defined spectrum mask. In this
case percentage of mask signal is overshooting or undershooting to be
considered as detection must be set. 0 % - any point spectrum above (or
below) mask will trigger detection, 100% - all points of signal spectrum have
to above (or below) mask to trigger detection.
• Mask detection bandwidth (BW) is set to compare signal against mask only in
set bandwidth in the center of channel. For example, it can be used to
compare mask to signal only at stable part of signal (carrier frequency).
• Practicaly spectrum in mask detection bandwidth contains more that single
spectrum point. It may be relevant (for example spectrum changes due to
modulation) whether mask is overshoot by all spectrum points (100%) or just
single point (0%). Overshoot/undershoot percentage can be set in textbox to
the left of mask type dropdown, if user defined mask is selected;
• Channel step for mask detection is set independently from measurement
range’s channel step. This allows to use any channel step. Further channel’s
step divisor is introduced, to use channel steps that are not integer values,
for example 25kHz/3 = 8,333 kHz;
• Width of spectrum channel is defined by measurement range’s channel’s step
second value (e.g. 25 MHz for “1MHz/25MHz” channel step), unlike
108
narrowband and broadband detection, width of spectrum has no influence on
mask detection channelling; Spectrum corresponding to width of channel will
be used to establishment of signal parameters (5.6);
• Detections related to maximum mask overshooting or minimum mask
undershooting are recorded in list of detection results with emission class
“mask+” and “mask-” respectively.
Mask detection is dependent on EM conditions at particular site, therefore specific
procedure for transfer of masks from one measurement site to another is not
foreseen.
Jammer detection
Skudra Patrol provides specific detection of signals generated by public mobile and
GNSS jammers. Usually, jammer signal is constructed by mesh of carriers. In order
detect jammer signal repetitiveness of jamming carriers is measured.
• Repetitiveness of jammer’s carriers is expressed as Carrier specificity for
required carrier spacing ranges. For example, if emission contains carriers
separated from each other (carrier spacing) by 100 kHz and power contained
in those carriers is by certain amount higher than typical value of other
spacing components, then emission will be detected as jammer.
However, jammer detection process includes several mathematical
conversions, in a way that dB relation between noise and carriers level is lost.
Therefore, Carrier specificity value is expressed as comparative measure
from 0 up to 5 (usually) with practical jammer detection squelch level of 1
to 2;
• Jammers for public mobile networks and GNSS usually have carrier separated
by 60 to 160 kHz, yet jammers designed for 433 MHz band can have carrier
spacing in range 1 to 5 kHz. To provide jammer detection for diverse types
of jammers, jammer detection is available for all channel steps, providing
options for jammers with finer or broader carrier spacing.
• In practice spectrum resolution (channel step) limits Carrier spacing ranges
usable for reliable jammer detection:
o 6.25kHz/25kHz (also IQ) limits to 1-10 kHz
109
o 10MHz/100MHz limits to 2-50 kHz
o 100kHz/200KHz limits to 10-200 kHz
o 1MHz/25MHz limits to 20 – 500 kHz
Those limits are approximate and twice broader limits may be usable;
• As jammer detection is available for every channel step, selecting
appropriate channel step increases scanning speed. For example, most public
mobile jammers can be detected with 2,5 kHz resolution provided by
100kHz/200kHz channel step;
• Many wanted signals contains repetitive carriers. For example, LTE signal has
traces of repetitive carriers with spacing of 45 kHz. To exclude such carriers
from calculation carrier spacing ranges must be set (example: 31-44;46-180).
To aid exclusion, it is possible to add predefined carrier spacing exclusions
for GSM, LTE, 5G by pressing respective buttons;
• Noise squelch determines neccessary interdecile range of emission’s
spectrum in 0.5 MHz, 2 MHz, 10 MHz or 20 MHz bands (respectively for
6.25kHz/25kHz, 10MHz/100MHz, 100kHz/200KHz and 1MHz/25MHz channel
steps), to proceed to jammer detection;
• Rarely local emissions, for example, from power adapters, may have
repetitive carriers. Their influence can be limited by setting noise squelch.
However unnecessary setting high noise squelch values may limit potential of
jammer detection, because even emissions with low signal to noise ratio
(lower that carrier specificity) can have high carrier specificity. Caution
setting high noise squelch is particularly important, because usually jammer’s
signal power density is low and most detection will happen close to noise
level;
• Guidance what repetitive carrier spacing frequency to exclude from by
spacing ranges, can be obtained by selecting false jammer detection record
in signal detection result list (4.1.8) and in sample spectra section (3.5)
clicking “download” button (E.12, otherwise used to obtain new sample
spectra). After that breakdown of carrier spacing with highest specificity is
110
displayed in “Sample spectra statistics” group. Carrier spacings displayed may
be excluded by spacing ranges to mitigate false jammer detections.
• Usually jammers cover broad frequency ranges, sometimes in excess of 100
MHz. Therefore, depending on bandwidth of jammer, signal will be stored in
100 MHz, 250 MHz or 500MHz span, resolution will be reduced to 400 kHz, 1
MHz or 2 MHz respectively. However, if waterfall spectrogram storage is
enabled, spectrum in full resolution will be available through waterfall
spectrogram.
Direction finding
Skudra Patrol provides functionality to trigger direction finding (DF) on detected
signals. Ranges tab provides DF triggering (4.3.9) configuration for each
measurement range. Direction finding results for each frequency channel are
displayed on map (4.1.17) and stored in measurement results file.
Intended objectives of DF triggering is to provide quality directions to the source of
detected signal, to reasonably share DF time between continuous and infrequent
signals, and to reserve DF time for most important detections. Objectives are
realised through following functions:
• Direction finding is triggered by signal detection event. Considering that
direction finding is more time-consuming operation than spectrum scanning
in most cases que of direction finding requests is created. Each DF request
has distinct frequency and measurement range combination.
• Direction finding request que is prioritised by more seldom requests, so that
infrequent signals and continuous signals have equal chance of being DF-ied.
Even more priority is given to seldom requests if request queue is more that
10 frequencies long. Priority is further increased after queue has reached
length of 20, 30, 100 frequencies.
111
• Receiver’s DF measurement time (averaging time) always is set 100 ms. If
triggered DF dwell time is set to 0 seconds, direction received from DF
equipment is returned as result of request. If dwell time is set longer that 0
seconds, most probable value of direction results received from DF
equipment during dwell time is returned. When calculating most probable
direction, it is taken into consideration that signals during the dwell time may
be received from several sources.
• DF results with quality lower that set limit in text box “Quality(%)” are not
taken into account, when calculation most probable direction during dwell
time. If no result from DF equipment above quality squelch is received, DF
request is returned as unsuccessful e.g. no direction is stored.
• Trigger field strength condition determines that DF request is made only for
signals above set field strength threshold. This condition is usable to ensure
that DF request are made only for signals with field strength sufficient for
direction finding, or to limit direction to signals of highest field strength;
• Count of signals trigger condition limits the number times signal has to be
detected for DF request to be made. Functionality can be used to exclude
from direction finding signals with low probability of repeating.
• Frequency trigger condition can be configured whether all signals (“Any”
satisfying other conditions are DF-ied, or only those without licence
assignments, or only those with channel frequencies listed in text box “DF
list (MHz)”.
Direction finder settings changed by Skudra PATROL
To ensure reliable direction finding some of the direction finders RF settings are
changed upon first or each DF request:
• DF bandwidth is automatically switched between 7.5 kHz (9 kHz for
SignalShark), 15 kHz, 120 kHz, 240 kHz (150 kHz for PR200 and EM200) and
2,4 MHz (2 MHz for PR200 and EM200) depending on bandwidth of detected
signal. However, setting these values requires to set DF selection and DF
112
span. To merit faster DF, bandwidth is set indirectly though DF step (if
possible).
• DF measurement mode is set to Normal (regulated by DF squelch).
• Spectrum measurement time is set to “Auto”;
• Settings like DF squelch threshold, antenna polarisation or amplification,
direction finders attenuation, DF antenna RF-input are changed according to
values set to DF equipment settings (4.3.10) for each range or as manually
overridden by user (see. 5.3.2)
• For some settings “-” value is available, which means that value already
set in direction finder by other means (e.g. GUI) will be used. However,
when using same equipment for direction finding and scanning, settings
relevant also to direction finding may be set during scanning by receiver
settings (4.3.1) and vice versa.
It is important to note that in versions below 4.5.8 Skudra PATROL sent “reset”
command to direction finder that resulted in default location (“Munich”) and
magnetic declination corresponding to that location. Starting version 4.5.9 reset
command is not sent.
Direction finding override
Direction finding override functionality is available, if any active (set as used)
measurement range has DF triggering enabled (4.3.9).
• DF override – direction finding on manually selected frequencies is started by
user clicking “START DF…” and stopped by clicking “STOP DF…”.
• During DF override direction finding is done on frequencies, corresponding to
records that has been selected in signal detection list on the moment of user
clicking “START DF…”.
• For DF override automatically created direction finding queue is replaced
with user created. Still, as scans progress, new frequencies is added to
automatically created DF queue, which will be used as DF override is stopped
by user.
Information on how to use direction finding override is available in section 4.1.18.
Dynamic bearing and location correction by Compass and GNSS
Skudra PATROL provides functionality to use compass correction for bearing results
and GNSS coordinates for location. Both corrected bearing and GNSS location is used
when DF results is reported to Skudra Server (5.4), however location is discarded for
results saved locally in Skudra PATROL.
Bearing and location correction can be enabled by selecting “Compass azimuth
correction with GNSS location” or “Course over ground azimuth correction with GNSS
location” in Azimuth and location dropdown (4.2.2)
113
However, enabling bearing and location correction, has effect only if physical GNSS
source is available. Further exact compass and GNSS source will be chosen after first
direction requested through triggered DF (4.3.9) by following scheme:
1. If physical GNSS source is not available, then
1.1. Skudra PATROL is running with dynamic bearing and location correction
disabled;
1.2. Skudra PATROL has set direction finder’s bearing correction by compass to
disabled (fixed North offset in use) and GNSS source to manual;
2. If physical GNSS source is available, then
2.1. First choice location source is DF antenna built-in GNSS source;
2.2. Second choice location source is GNSS source connected (or built-in) to
direction finder;
2.3. If to use compass azimuth correction is selected:
2.3.1. First choice compass is DF antenna built-in compass;
2.3.2. Second choice compass is compass connected to direction finder;
2.3.3. If no compass is available Skudra PATROL sets direction finder’s
bearing correction by compass to disabled (fixed North offset in use) and
GNSS source to manual;
2.4. If to use course over ground azimuth correction is selected:
2.4.1. First choice is “Course over ground” derived from DF antenna’s built
GNSS source;
2.4.2. Second choice compass is “Course over ground” derived from GNSS
source connected (or built-in) to direction finder;
2.5. Software azimuth correction is never used.
Selections made here are stored in direction finder, and may influence results of
other software used after Skudra PATROL.
Direction finding: Report DF results to Skudra Server
If accordingly configured (4.3.9) Skudra Patrol reports direction finding results
realtime to Skudra Server. For further storage, realtime display and triangulation.
Following data is sent to Skudra server:
• Frequency channel;
• Most probable direction to signal source, obtained according to 5.3;
• Timestamp of DF;
• All DF results, obtained during the dwell time period;
114
• Coordinates of direction finder during the dwell time if compass functionality
in settings panel (4.2.2) is enabled. Otherwise coordinates set in settings
panel (4.2.5) are sent;
• If direction finding is unsuccessful, field strength of signal associated with
the coordinates is still sent to Skudra Server.
The storage of signals detected
All detected signals are aggregated by frequency channel to minimise storage space
and processing power, as well as efficient access to monitoring results.
• All signals found in any single frequency channel are stored in one array
(cumulated spectrum) creating a matrix, the elements of the matrix showing
how often the index value (frequency and level) is detected;
• Every time when, monitoring a frequency channel, a signal is detected, it’s
level is stored. Information on the number of scans when no signal was
detected is also stored;
• The average correlation value of all signal detection events in a channel is
stored;
• Each scan’s start time is stored. This value corresponds to signal detection
time and is referenced to each detection event
• The sample spectra use statistics are stored – how often each sample
spectrum was detected as most appropriate;
• Distribution of triggered DF results (if available) is stored.
The establishment of signal parameters
A single value for each parameter is obtained for each frequency channel.
• The field strength is calculated as the maximum electromagnetic field
strength dBµV/m, exceeded in 2 % of signal detection cases. The intensity is
calculated adding to the signal level the earlier set antenna factor (Error! R
eference source not found.) and cable attennuation (Error! Reference
source not found.);
• The field strength for each signal detection case is calculated as the spectrum
maximum value in the signal bandwidth (the FFT resolution for 100 kHz
channel step FFT is 2,5 kHz, for 6,25 kHz step – 125Hz, Blackman windowing);
• Bandwidth – The detected signal maximum bandwith exceeded in 5 % cases
of signal detection at a signal to noise ratio at least 30 dB. If the signal to
noise ratio never has exceeded 30 dB, the presented bandwidth is calculated
as the maximum unique bandwidth level pairs exceeded in 5 % of detected
signals;
115
• The signal bandwidth in each detection event is determined by the 1% β (99%
power in bandwidth) method if signal to noise ratio at least 30 dB, and by the
mid-level between the maximum level and noise level if the signal to noise
ratio is less than 30 dB;
• The signal activity percentage is calculated as a percentage of signals
detected over the total number of scans.
File formats
The file format of the antenna factor and cable attenuation
• The antenna factor and cable attenuation is delivered to the software by an
UTF-8 text file (*.txt). Each row of the file comprises pairs of frequencies in
MHz and attenuation coefficient in dB separated by the tabulation symbol
(TAB). The decimal sign is point (.).
• The antenna factor and cable attenuation should be delivered with a positive
sign enabling the calculation of the resulting field intensity by summing up
the received signal level, the antenna factor and the cable attenuation.
The file format of the licence database
• The antenna factor and cable attenuation is delivered to the software by an
UTF-8 text file (*.txt).
• Each file row comprises 20 tabulation symbol seperated (TAB) values:
1. Reserved for future use
2. Frequency (MHz)
3. User
4. Reserved for future use
5. Reserved for future use
6. Comment
7. Effective radiated power (dBd)
8. Reserved for future use
9. Reserved for future use
10. Antena height over ground (m)
11. Class of emission
12. Reserved for future use
13. licence identificator
14. Reserved for future use
15. Decimal coordinate (E)
16. Decimal coordinate (N)
17. Reserved for future use
18. Reserved for future use
19. Reserved for future use
116
20. Reserved for future use
• All values are given in single quotes as ‘value’. The decimal sign is point (.).
The format of the specific frequency file
• The specific frequencies are delivered to the software by an UTF-8 text file
(*.txt). Each file line contains a frequency in Hz, the frequency user and class
of emission separated by the tabulation symbol (TAB).
• The frequency may only be a positive integer. The class of emission is not
mandatory.
The file of radiofrequency applications
• The radiofrequency application information is delivered by a “xlsx” format
file, that should be downloaded from the web-site https://efis.cept.org/,
choosing necessary country in the tab “Application” and then pressing search.
• After that by click “Export search results to XLSX (country as colums)” EFIS
application file supported by Skudra Patrol is downloaded;
117
• The radiofrequency application information is delivered by a “csv” format
file, that should be downloaded from the web-site https://efis.cept.org/,
choosing necessary country in the tab “Application”;
• Length of each application record contained in radiofrequency application
information file is not limited, however, for efficiency reasons, Skudra
PATROL/SERVER limits its length to about 2000 symbols.
CSV file of radiofrequency applications
Skudra Patrol also supports previous EFIS “csv” format for applications file. This
coma separated values file must be composed in following manner:
"Lower Frequency";"Upper Frequency";"Latvia"
"14 kHz";"19.95 kHz";"Inductive applications / Defence systems"
"19.95 kHz";"20.05 kHz";"Standard frequency and time signal"
"20.05 kHz";"70 kHz";"Inductive applications / Defence systems"
"70 kHz";"72 kHz";"Inductive applications"
"72 kHz";"84 kHz";"Inductive applications / Defence systems"
"84 kHz";"86 kHz";"Defence systems / Inductive applications"
"86 kHz";"90 kHz";"Inductive applications / Defence systems"
• For each frequency application there are 3 values: “Lower frequency”, “Upper
frequency” and “Application”;
• Each value is inside double quotes, and is separated by semicolon;
• Each application is separated by “new line” symbol;
• Decimal separator for frequencies is point “.”;
• Frequencies can be of Hz, kHz, MHz or GHz units.
118
User manual
2024-Q3.2
Rīga, 2024
1
CONTENT
Content .......................................................................................... 2
1 Installation................................................................................. 3
1.1 Explanations ........................................................................ 3
1.2 Supported devices.................................................................. 3
1.2.1 Receivers ......................................................................... 3
1.2.2 Direction finders................................................................. 4
1.2.3 Additional devices ............................................................... 4
1.3 Installation steps ................................................................... 4
2 Configuring the Skudra target driver ................................................ 13
3 Client configuration .................................................................... 16
4 Receiver control and measurement .................................................. 18
4.1 General settings .................................................................. 18
4.2 Settings for measuring radio emission parameters .......................... 19
4.3 Taking measurements ........................................................... 21
4.4 Measurement data recording and analysis .................................... 22
5 ANALYSIS OF RECORDED MEASUREMENT DATA ...................................... 25
5.1 Access to Recorded Measurement Data ....................................... 25
6 Direction finding (DF, leveling) ....................................................... 28
7 HEATMAP OF Emision SOURCE LOCATION ........................................... 30
7.1 Configuring Target Driver to Obtain a Location Heatmap .................. 31
7.2 Configuring TARGET Control Measurement to Obtain a Heatmap ......... 33
7.3 Calculation of the Radiation Source Location Heatmap .................... 34
8 AUTOMATIC MEASUREMENTS .......................................................... 36
8.1 Configuring and Saving Individual Tasks in the Measurement List ........ 36
8.2 Preparing the Automatic Measurement List and Starting Measurements 37
8.3 Editing Individual Tasks in the Measurement List ........................... 38
8.4 Automatic Measurements in Remote Mode (REMOTE) ...................... 39
9 SIMPLIFIED MODE........................................................................ 41
9.1 Selecting the Measurement Point .............................................. 41
9.2 Starting the Measurement ...................................................... 41
9.3 Saving Results ..................................................................... 42
9.4 Preset Groups and Frequency Ranges ......................................... 42
2
1 INSTALLATION
To use Skudra Target, you must have the latest PostgreSQL database installed. The
PostgreSQL Installation Guide provides information on how to download and install
PostgreSQL .
During PostgreSQL installation it is important to set and note database port and
password that will be necessary during Skudra Target installation.
This document provides instructions for installing and using Skudra Target.
1.1 Explanations
Skudra Target consists of three applications:
• Skudra Target Driver – for communication with radio monitoring equipment
and storing results in database;
• Skudra Target Control – for measurement control and real time visualization;
• Skudra Target Analysis – for analysis of measurement results that are stored
in database;
Three applications may be run on the same computer or on different computers
providing that there are TCP and UDP communications allowed on ports in range of
19005-19100 in both directions.
UDP communications from monitoring receiver to computer with Skudra Target
Driver installed have to be allowed at ports ranging from 19005 to 19100. Additionally
TCP connection from driver’s computer to monitoring receiver also has to be allowed
on port 5555. Port 5555 is usual for R&S receivers, however it may be updated
depending on receiver.
PostgreSQL has to be installed on computer where Skudra Target Driver is intended
to work.
Software protection dongle is necessary only on computer where Skudra Target
Driver is running.
1.2 Supported devices
Skudra Target supports in this chapter listed devices, additional devices can be
added upon request.
1.2.1 Receivers
Current Skudra Target version supports fallowing receivers:
• Rohde & Schwarz ESMB
• Rohde & Schwarz EB200
• Rohde & Schwarz ESMD
• Rohde & Schwarz EB200
• Rohde & Schwarz EM100
• Rohde & Schwarz EM200
• Rohde & Schwarz EM500
• Rohde & Schwarz UMS100
• Narda SignalShark family receivers
3
1.2.2 Direction finders
Current Skudra Target version supports fallowing direction finders:
• Rohde & Schwarz ESMD with DF option
• Rohde & Schwarz EB500 with DF option
• Rohde & Schwarz EBD190
• Rohde & Schwarz EBD195
• Rohde & Schwarz PR100 with DF option
• Rohde & Schwarz PR200 with DF option
• Narda SignalShark family direction finders
With their peripheral devices (e.g. compasses, GPS) witch are provided with control
units manufacturer.
1.2.3 Additional devices
Current Skudra Target version supports fallowing additional devices:
• Antenna Control Units and Switches:
− FU129
− GB016
− GB127M
− GB127MU
− GB127S
− ZS129A1
− ZS129A5
With their peripheral devices (e.g. rotators) witch are provided with control units
manufacturer.
1.3 Installation steps
1. To start installing Skudra Target, you need to start the installation file
2. Depending on the settings of Microsoft Defender , the installation may be
considered insecure, then you need to press "More info"
4
•
3. You have to press " Run anyway "
5
4. Depending on the security settings of the system, it is possible that there will
be such a restrictive inscription below, then you need to press " Allow this
file ”:
•
•
5. Permission to install must be approved
6
6. We select all three Skudra Target components and press " Next "
7. We select the folder where the program will be installed
•
• Recommended installation path: “C:\SKUDRA\Skudra TARGET\”
7
8. Some components require Administrator rights to install
9. We press " Continue " so that Skudra Target connects to the database
8
10. We choose " Connect to existing ", enter the Port and Password values that
were entered during PostgreSQL installation (Port:19040, Password:monitor)
11. Press " Close " and continue the installation
9
12. Press " Finish " after creating Desktop icons and Skudra Target and Control to
start.
13. Skudra Target The Control window will look like this
10
14. Skudra Target Driver will be available in notification area
15. Double-clicking the icon will open the Skudra Driver window
16. Skudra Target Driver status is available on corresponding tab. Error messages
if any will be shown is this tab.
11
17. Skudra Target is successfully installed. Shortcuts for Skudra Target Driver,
Control and Analysis are available on desktop.
12
2 CONFIGURING THE SKUDRA TARGET DRIVER
Skudra Target Driver is an interface for radio monitoring equipment and for storing
measurement results into the database, so before starting measurements, it is
necessary to make settings for the Skudra Target Driver for connected receivers,
antennas and database connection.
Figure 1Skudra Target Driver
Skudra Target Driver consists of 4 sections:
1. Receivers:
A section where you can connect and disconnect receivers (choosing from the
available ones) and configure their connections
Figure 2Receiver section
To add a new receiver, you need to set the following parameters:
• Title;
• Status - Enabled/Disabled (tick next to “ Enabled ”);
• IP address of the local network of the receiver ;
• Port number for remote control (for Rohde&Schwarz receivers it is 5555, for
others - according to the manufacturer's documentation);
• Type (list of available receivers);
• Position in antenna switch;
• Use of receiver-maintained (GNSS) location (Enabled/Disabled);
To delete a receiver, double click on the receiver and “ Delete Receiver "
2. Antennas
13
Section for adding, selecting and configuring antennas.
Figure 3Antenna section
To add a new antenna, you need to set the following parameters:
• Name – it is preferable to use the name given by the manufacturer;
• Status (Enabled/Disabled);
• Position in antenna switch;
• Comments;
• Antenna gain file ( csv format);
• Cable attenuation file ( csv format);
To delete an antenna, double-click on the antenna and “ Delete Antenna "
3. Status
The status section is for driver connection and error information.
Figure 4Status section
14
4. Settings
Section for drivers connections credentials and settings.
Figure 5 Settings section
General settings are used for client and driver communication, if client to driver is
connected through VPN or restricted network, port range defined in these settings,
should be opened as exceptions for communication.
In general those settings should be left default values.
After successful drivers configuration it is advised to backup all user settings using
“Export current configuration”.
15
3 CLIENT CONFIGURATION
Skudra Target Control application is used as client for monitoring equipment remote
control and perform and maintain measurements on multiple drivers instances.
Figure 6Skudra Target Control main window
Figure 7 Control application setting window
In order to perform measurement, there is necessary to add driver instances to client
configuration, it is possible to add multiple driver instances and use each connected
device simultaneously.
Figure 8Adding a new driver
The following parameters need to be set for each driver:
• Name – the name of the driver, it is preferable to use the name of the
monitoring point;
• Driver computer IP address;
• Driver port number;
Drivers IP address can be found in drivers application window status bar, see “Figure
5 ” ex. 10.0.212.23:19010.
16
Control Driver
application instances
settings
Data analyse
application
Connected
equipment
Driver
settings
Figure 9Skudra Target Control main menu window with connected drivers
After completing the configuration settings, all connections are visible in the main
menu window and also as a color indication (monitoring points):
• – connected;
• – disconnected;
The status is visible for each monitoring point hardware:
• Ready – equipment is ready to use;
• Busy – equipment in use;
• Unavailable – connection from diver to equipment is not available;
17
4 RECEIVER CONTROL AND MEASUREMENT
4.1 General settings
In the control window of the receiver, it is possible to perform measurements with
measurement visualization in real time
Measurement control
window
Data views
Measurement
modes
Measurement
settings
Measurement
statuss
Figure 10Receiver control window
Workflow for measurements:
1. Choose measurement mode:
• Level meter – signal technical measurements, e.g. level, bandwidth and
modulation;
• Bearing – direction finder measurements;
2. Set measurement settings;
3. Set frequency in measurement control window;
4. Start measurement ;
5. Open required data view.
• There is available following data view, depending on measurement mode:
• Spectrum;
• Compass;
• Map;
• Data table;
Fig 11 Data view floating panels
Data view panels are floating panels, which you can arrange by dragging and dropping
to guided arrangements.
18
4.2 Settings for measuring radio emission parameters
For measurements of radio emission parameters, it is essential to correctly select
and set the required setting values for the result.
1. Antenna selection:
We select the necessary antenna from the available list:
2. Selection of parameters to be measured (what the receiver will measure):
•
• Field Strength – Field intensity;
• Spectrum – Spectrum display;
• Frequency Offset – Frequency shift;
• Occupied Bandwidth – Occupied bandwidth;
• Audio – turning on the sound;
• AM Modulation – Amplitude modulation depth measurements;
• FM Modulation – Frequency deviation measurements.
•
3. Receiver basic settings :
•
• Attenuation – attenuation values;
• Attenuation mode – type of intermediate frequency attenuation;
• IF Bandwidth – measurement bandwidth;
• Enable squelch – Noise suppression threshold (on/off);
• Squelch – Threshold limit value for noise suppression.
•
•
•
4. Spectrum display settings:
19
•
• Frequency span – the width of the spectrum to be displayed;
• Spectrum selectivity – display selectivity;
• Spectrum RBW – spectrum resolution.
Note – when changing Frequency span , the Spectrum RBW also changes
automatically , but then the Spectrum RBW can be set manually.
5. Bandwidth measurements:
•
• or
•
• Bandwidth mode – Bandwidth measurement method selection (Beta/ Xdb );
• xdB – parameter for the XdB method (minus dB from the peak);
• % for marker function – parameter for the Beta method (percentage of the
spectrum);
• Meas . Bandwidth – bandwidth to be measured (it is possible to set less than
Frequency span ).
•
6. Additional settings:
•
• Spectrum Trace – Spectrum curve display selection;
• Detector – detector selection;
• Measurement time – measurement reading time.
•
7. Demodulation:
•
• Mute Speaker – turning on/off the receiver's speaker;
• Speaker volume – volume settings for the receiver speaker;
• Audio mode – audio quality for the demodulated signal;
• Audio volume – volume level when listening to the signal in Skudra Target;
• Demodulation type – selection of demodulation type (FM, AM, etc.).
20
•
4.3 Taking measurements
1. The frequency to be measured must be entered:
•
• Or frequencies (using +):
•
• Frequencies can be removed one by one by pressing the red X, or all by
pressing the " Clear " button all frequencies ”:
•
•
2. The type of display of the required information must be selected (spectrum
and/or tables of measurement results):
•
•
3. Start the measurement by pressing the button in the upper right corner
4. Visual control of measurements:
•
• Selection of frequencies to be displayed (in the relevant spectrum
graph, we choose to display either one frequency or several - in LIVE
mode):
• Setting the limits of the vertical axis of the spectrum:
21
•
• Trace - spectrum accumulation option on/off; Reset – deleting the
accumulated curve
•
• Hold time – measurement time for each frequency ( Hold time defaults
to 0):
•
• Instantaneous values of measurements in the data table window:
•
• To stop the measurement, press the key
•
•
4.4 Measurement data recording and analysis
1. Recording measurement data:
• Before starting measurements, or during them, in the field " Recording
name ” type the name of the file and press “ Save ”:
• A green indication “ Saving ”is visible since recording is started:
•
•
• “Stop Live Stream ” button stops the visual display of measurements
in the spectrum and table, but does not stop measurements and
recording;
• It is not possible to change measurement settings during recording.
•
2. Analysis of recorded measurement data:
• Target should start Data analysis tool. This can be done in two ways -
starting from the computer's Desktop shortcut , or from Target Control
bottom toolbars:
22
• A list of performed measurement records opens, which can be
filtered, searched, renamed and deleted:
•
• You can analyze and play the specific measurement by double-clicking
on it:
• Double-clicking on a measurement unit displays its detail and
spectrum. With the blue vertical arrows you can switch between
measurement units:
•
•
23
• Measurement data can be exported in various formats (CSV, WAV and
MP3):
• Measurement records can be displayed graphically using the " Explore
" button graphs ' options:
• An example of a graphical representation:
24
5 ANALYSIS OF RECORDED MEASUREMENT DATA
5.1 Access to Recorded Measurement Data
To perform analysis of the recorded measurement data, you need to use the Target
Data Analysis tool. It can be opened from Target Control in three ways:
1. Starting Data Analysis from the upper toolbar of the Target Control
connection dialog. In this case, the user must provide the access credentials
to the database where the measurement data is stored:
•
2. Starting Data Analysis from an established connection with Target Driver
in Target Control. In this case, Target Analysis will open connected to the
database where the respective Target Driver saves the results:
3. Starting Data Analysis from the lower toolbar of the Target Control
measurement window. In this case, Target Analysis will open connected to
the database where the current results are being saved:
25
•
•
•
• A list of performed measurement recordings will open, which can be filtered,
searched, renamed, and deleted:
• To analyze and play back a specific measurement, double-click on it:
• By double-clicking on a measurement unit, its details and spectrum will
appear. You can switch between measurement units using the blue vertical
arrows:
26
•
• Measurement data can be exported in various formats (CSV, WAV, and MP3):
• Measurement recordings can be displayed graphically using the options
provided by the "Explore graphs" button:
27
• Example of a graphical representation:
6 DIRECTION FINDING (DF, LEVELING)
• You must select the bearing mode - " Bearing "
• Then the basic settings related to the direction finder are visible:
DF Quality – bearing quality;
DF Bearing – bearing azimuth.
• Pelengator additional settings menu:
DF Polarization – Direction finding antenna polarization selection;
Measurement time – measurement time of the measurement;
28
CBW resolution – The width of the measuring band, limited by the width of the
spectrum displayed by the receiver ( Frequency span ). To apply a higher CBW
resolution , you need to increase the Frequency span in receiver settings:
DF Squelch – Threshold of the squelch signal above which measurements are
captured;
DF Mode – Mode of dialing;
DF quality – Threshold of scaling quality in percentage.
• To see the display of the direction on the map, press the button " Add
folder ”:
• The numerical values of the surveying results can be seen in the table,
while visually the surveying direction can be seen on the map as a
beam:
• It is possible to scan several frequencies at the same time:
29
• The length of the displayed ray on the map can be changed:
•
• If a recording is made, then in surveying mode, the results of direction
determination measurements are also recorded.
7 HEATMAP OF EMISION SOURCE LOCATION
In this chapter, the location of a radiation source is determined by combining
direction-finding results from a single moving point. Each direction-finding result is
assigned coordinates and is referenced relative to geographic north.
The obtained results are used to calculate the probability of the radiation source
being at each point within a previously selected area on the map. By displaying the
calculated probabilities on the map using a color scale, it becomes possible to
visually determine the location of the radiation source:
30
Displaying parameters (including the probability of a radiation source) on a map using
a color scale is called a heatmap.
7.1 Configuring Target Driver to Obtain a Location
Heatmap
Unlike direction-finding from a fixed point, determining direction from a moving
monitoring point and subsequently calculating the radiation source heatmap requires
the use of GNSS and sensors for the antenna's orientation relative to geographic
north.
Target supports two types of sensors: those connected to the computer's serial port
that provide NMEA-formatted data, and sensors built-in or directly connected to the
R&S direction finder (or receiver).
To use serial port GNSS and compass sensors, their availability must be specified in
the Target Driver under the Devices section by selecting External GNSS and
Compass, and by indicating the serial port number (COM1 – COMn). USB devices and
other devices with drivers that provide serial connections are also supported:
31
When using the External Compass, the user must specify the magnetic declination
appropriate for the measurement location.
To use sensors built into or directly connected to the receiver, they need to be
configured in the Target Driver under the Receivers section by selecting the
direction finder or receiver that will be used for direction-finding:
In the direction finder's configuration window under the Capabilities section,
pressing the Fetch button requests information from the direction finder about the
connected sensors. The available sensors are organized in the Compass and GPS
menus according to the function they perform.
Examples of compass types:
• Automatic – Target will use the compass already set in the direction finder
without Target's intervention (via the receiver's GUI or screen); Target will
not make changes to the direction finder's configuration.
• Software, COMPASS_SW – Fixed correction compass (not usable in motion).
• GH150@ADD107 – Magnetic compass built into the ADD107 antenna.
• COG@ADD107 – Course over ground; azimuth value is obtained from GNSS
values in motion using the ADD107 antenna's GNSS sensor.
• COG@u-Blox LEA-6T – Course over ground; azimuth value is obtained from
GNSS values in motion using a GNSS sensor connected to the direction finder.
• COG@NMEA – Course over ground; azimuth value is obtained from GNSS
values in motion using an NMEA-format GNSS sensor connected to the
direction finder.
Examples of GNSS sensor types:
• Automatic – Target will use the GNSS sensor already set in the direction finder
without Target's intervention (via the receiver's GUI or screen); Target will
not make changes to the direction finder's configuration.
• Manual – GNSS sensor is not connected; fixed coordinates set in the receiver
will be used (not usable in motion).
• LEA@ADD107 – GNSS sensor built into the ADD107 antenna.
• u-Blox LEA-6T – GNSS sensor directly connected to the receiver.
• NMEA – NMEA-format GNSS sensor directly connected to the receiver.
When using a magnetic compass directly connected or built into the direction finder,
the magnetic declination is automatically determined by the direction finder based
on the GNSS coordinates provided by the selected GNSS sensor.
32
The selection of built-in and directly connected sensors to the receiver is made (after
pressing the Fetch button) in the displayed menus, with subsequent confirmation by
OK or Apply.
Upon reopening the direction finder's configuration window, only the previously
selected value and Automatic are available. To change the sensor being used, you
must press Fetch again, which for some direction finders can block all functions for
up to 30 seconds.
7.2 Configuring TARGET Control Measurement to Obtain a
Heatmap
Unlike direction-finding from a fixed point, determining direction from a moving
monitoring point and subsequently calculating the radiation source heatmap requires
the use of GNSS and sensors for the antenna's orientation relative to geographic
north.
The use of GNSS and the antenna's orientation relative to geographic north is
specified in the TARGET Control measurement settings under Location Source and
Azimuth Correction, respectively.
The "Location Source" menu offers the following options:
• Driver (Fixed) – Fixed coordinates specified in the TARGET Driver under
Settings (not applicable for heatmap calculation).
• External GNSS – External NMEA GNSS sensor configured in the TARGET Driver
Devices section (applicable for heatmap calculation).
• Receiver (Fixed) – Fixed coordinates specified in the TARGET Driver under
Receiver → Geographical (not applicable for heatmap calculation).
• Receiver (selected value) – GNSS sensor selected in TARGET Driver under
Receiver → Capabilities (applicable for heatmap calculation).
• Antenna (Fixed) – Fixed coordinates specified in TARGET Driver under
Antenna → Details (not applicable for heatmap calculation).
The "Azimuth Correction" menu offers the following options:
• Driver (Fixed) – Fixed direction correction specified in TARGET Driver under
Settings (not applicable for heatmap calculation).
• External Compass – External NMEA magnetic compass configured in the
TARGET Driver Devices section (applicable for heatmap calculation).
• Receiver (Fixed) – Fixed direction correction specified in TARGET Driver under
Receiver → Geographical (not applicable for heatmap calculation).
• Receiver (selected value) – Azimuth correction source selected in TARGET
Driver under Receiver → Capabilities (applicable for heatmap calculation).
• Antenna (Fixed) – Fixed direction correction specified in TARGET Driver under
Antenna → Details (not applicable for heatmap calculation).
When the user selects Location Source → External GNSS or Receiver (selected
value) and Azimuth Correction → External Compass or Receiver (selected value),
the direction relative to north will be automatically recalculated for each direction-
finding result, and current coordinates will be added.
For measurements configured according to heatmap calculation, the TARGET
Control map and results table visualize measurements with changing coordinates and
direction:
33
Currently, heatmap calculation is available in the TARGET Data Analysis tool.
Therefore, to display the calculated heatmap, saving the results is necessary (press
the Recording button).
7.3 Calculation of the Radiation Source Location Heatmap
To calculate the radiation source location heatmap, saved direction-finding results
(performed in motion) are required. Both previously saved results and results that
are currently being saved can be used for calculations.
While performing measurements, it is convenient to switch to the Data Analysis tool
for displaying the heatmap by pressing the Data Analysis icon in the lower toolbar
of the Target Control measurement window:
The heatmap calculation functionality is available in the list of measurement results
by selecting the result that contains direction-finding data and pressing the result
display icon:
34
From the available display options, select Statistical map and press Calculate:
The result of the radiation source heatmap calculation:
When performing the heatmap calculation, consider the following:
• The heatmap calculation is performed only for the area displayed on the map.
That is, only the direction-finding results that intersect the displayed area
will be used for calculating the radiation source heatmap. This may lead to
incorrect results if the radiation source is not located within the displayed
35
map area. Therefore, it is advisable to perform the calculation initially over
a wider area.
• The heatmap calculation is performed for the current map zoom level.
Changing the map zoom level also zooms the calculated heatmap in or out,
but it does not become more accurate. To obtain a more precise radiation
location heatmap, you need to recalculate it by pressing Clear → Calculate.
8 AUTOMATIC MEASUREMENTS
Skudra TARGET automatic measurements are implemented as a receiver control
mode that sequentially performs measurements of previously configured and saved
tasks. The list of tasks to be performed automatically can be created and initialized
for measurement both from the TARGET interface and from the Skudra SERVER
(remote measurement mode).
Individual measurement tasks, which together form the list of tasks to be performed
automatically, are created by the TARGET user by saving the current measurement
configuration. The saved configuration includes all parameters that determine the
measurement result:
• Receiver RF parameters
• Antenna used (its position in the switch, polarization, direction in the rotator,
gain)
• Connected additional devices (GNSS and compass sensors)
• Measured parameters
• Measured frequencies
The transition from single-task measurement mode to automatic task list mode is
made for each receiver individually by toggling the Expert mode slider in the
TARGET Control measurement window:
In the current TARGET functionality, Expert mode means a mode where the user
needs to specify measurement parameters, as opposed to automatic measurements
where parameters are predefined.
8.1 Configuring and Saving Individual Tasks in the
Measurement List
Configuring and saving individual tasks in the measurement list is done in Expert
mode, as it provides the ability to set all parameters:
36
In the task configuration, all measurement parameters that can be specified in
Expert mode are saved, except for the result saving option (automatic task results
are always saved) and the result visualization and audio playback options (they do
not affect the measurement result and are available during automatic measurements
as needed).
The measurement task configuration is saved by pressing Save current
configuration, after which you can specify a configuration name:
8.2 Preparing the Automatic Measurement List and
Starting Measurements
To perform automatic measurements and create the list, switch to the automatic
measurement mode (Scheduling Control):
To perform automatic measurements and create the list, switch to the automatic
measurement mode (Scheduling Control):
37
After adding the task, you can:
• Select which of the previously saved measurement configurations to use in
the selected task.
• Specify how long to perform the measurement (format "hours
• ").
• Monitor the frequencies included in the measurement configuration.
• Remove the measurement task from the list (by pressing the red cross next
to the task).
To start automatic measurements according to the list, press the green START
button. Measurement results will be saved in the database, creating a separate
record for each task.
The measurement result record name will be formed as: "Measurement Filename"
+ "Measuring preset".
8.3 Editing Individual Tasks in the Measurement List
The measurement task configurations used for tasks in the automatic measurement
list can be edited. In Expert mode, select the saved configuration and press Edit:
38
The Measure Control window will then be displayed in Editing mode:
The Editing mode provides the ability to:
• Change the frequencies in the measurement configuration.
• Check and change any measurement parameters.
• Delete the measurement configuration.
• Change the measurement configuration name.
• Save or cancel the changes made in the configuration.
After making changes, the edited configuration is available in Scheduling Control
mode.
8.4 Automatic Measurements in Remote Mode (REMOTE)
It is possible to create the automatic measurement task list and control
measurements from the Skudra SERVER.
Just as when controlling measurements from Skudra TARGET, a task list is also
created for each receiver separately on the SERVER.
To set the selected receiver to remote control mode, activate remote control in the
TARGET Control receiver window:
While remote control is activated, the TARGET Driver will regularly and
automatically communicate with the Skudra SERVER to obtain the current automatic
measurement tasks. Upon receiving measurement tasks, their execution will begin,
and results will be saved.
During the time when TARGET remote control is activated but no tasks are received
from the Skudra SERVER, it is possible to perform direct measurements with TARGET.
However, direct measurements will be interrupted as soon as a task is received from
the Skudra SERVER.
39
The progress of Skudra SERVER automatic measurements can also be monitored in
the Skudra TARGET Scheduling Control window, which visually does not differ from
the direct automatic measurement window and has the same functionality available,
except for the ability to make changes:
40
9 SIMPLIFIED MODE
In simplified mode, tasks can be performed without the need to change device
settings. Depending on the frequency entered by the user and the selected mode
(Direction Finding or Levelmeter), one of the available devices is chosen.
Appropriate settings are automatically applied to this device, and the measurement
process begins. The received measurement results are visualized, and the option to
save them to the database is offered.
9.1 Selecting the Measurement Point
To start using Target in simplified mode, select the measurement point (1) from the
Control tool, and then press Start (2).
1
2
9.2 Starting the Measurement
To start the measurement, enter the frequency (3) and press the start button (4).
This initiates a measurement in Levelmeter mode.
3
4
41
If a receiver that supports Direction Finding mode is available, pressing the start
button labeled DF (5) initiates a direction-finding measurement, and the direction
of the received signal is displayed on the map.
5
9.3 Saving Results
It is possible to save the received data by turning on the Record switch (6).
6
Returning to the initial view, by clicking on the settings button (7), you can open the
settings window. Here you can specify the destination database or point (8) where
the measurement data will be saved. Changes take effect after pressing the Save
button (9).
7
8
9
9.4 Preset Groups and Frequency Ranges
In simplified mode, device settings are applied automatically depending on the
selected frequency. Automatic application of settings is provided by predefined
setting groups (called presets). The preset groups can be edited in the Target Driver
program under the corresponding tab (10). Here you can add new preset groups (11,
12) as well as edit existing ones (by clicking on the desired group, 13). By right-
clicking on the group, a context menu is opened (14), where you can delete the
preset group.
42
11
10
12
13
14
In the preset group definition window, settings for each device type are specified.
By selecting the value –, the particular setting will not be changed.
43
SKUDRA SERVER v.5.3.61 user guide
Riga, 2024
User manual for Skudra Server v.5.3.61.
1 CONTENTS
1 CONTENTS ....................................................................................................................................... 2
2 Introduction .................................................................................................................................... 3
3 Getting started with SKUDRA Server............................................................................................... 4
4 Map ................................................................................................................................................. 5
5 24/7 ............................................................................................................................................... 13
6 Broadcasting .................................................................................................................................. 14
7 DF ( Direct Finding / direction measurements) ............................................................................. 19
8 Equipment ..................................................................................................................................... 20
9 Scheduler ....................................................................................................................................... 22
10 Measurement units .................................................................................................................. 23
11 Measurement ........................................................................................................................... 23
12 Schedule ................................................................................................................................... 25
13 Reports ..................................................................................................................................... 26
14 Sample spectra ......................................................................................................................... 29
15 Appendix .................................................................................................................................. 30
16 Abbreviations and terms used. ................................................................................................ 30
Page 2of30
User manual for Skudra Server v.5.3.61.
2 Introduction
Skudra Server software module purpose is to provide radio control monitoring function
operators with frequency user information, current radio monitoring information and
historical radio monitoring information in the most effective way.
The system provides an opportunity to visualize and analyze monitoring data, thus
helping to perform more efficient monitoring and control of the radio frequency spectrum.
The system also collects information about the hardware and equipment used in monitoring
and other measurements, their technical data and other important information. The Skudra
Server application is regularly updated and renewed, so there may be situations when one of
the described functionalities works partially or is temporarily unavailable.
Page 3of30
User manual for Skudra Server v.5.3.61.
3 Getting started with SKUDRA Server
You can work with the app using one of the web browsers (e.g. Google Chrome or
Microsoft Edge ). You can activate the home screen in:
1. Type in the address line of the browser: https://skudra/
fig. 3. 1Command line entry
By choosing the access path described in the first two points, in the next step we get to
the login screen, where the user name and password must be entered.
fig. 3. 2Login screen
In order for a VASES employee to become an authorized user of Skudra Server , it is
necessary to contact the main specialist of RMD, who will assign the user an account.
After successful authorization, a start screen appears with several sections, the actions
of which are described in the following points (content points 3-9).
Page 4of30
User manual for Skudra Server v.5.3.61.
fig. 3. 3SKUDRA Server home screen with menus
4 Map
The "Map" section shows current and historical information about all individual
frequencies registered during monitoring with the SKUDRA Patrol program from fixed
monitoring points or mobile monitoring. Both registered users and NRS.
fig. 4. 1Monitoring data and map
The amount of data in the columns can be changed by zooming in or out of the map
on the right side of the screen. This can be done both by scrolling the mouse wheel, placing
the cursor over the map beforehand, and also by using the + and – (to scale) buttons in the
left, upper corner of the map. When you zoom in on Riga, the columns will show only the
information registered in Riga's fixed RMP, or mobile monitoring data, if they were made
within the zoomed-in map. Likewise in other regions.
Page 5of30
User manual for Skudra Server v.5.3.61.
fig. 4. 2Data arrangement in columns
The left side of the screen with the data arranged in columns. Data in columns can be
sorted in ascending or descending order by clicking on the column headings.
The columns show the following information:
1. Frequency, the use of which is fixed during monitoring.
2. Start date of the monitoring during which the frequency is fixed.
3. Signal level dBµV /m.
4. User. The data in this column are active links to user permission information (see
3.3). It can also be as NRS without additional data.
Page 6of30
User manual for Skudra Server v.5.3.61.
fig. 4. 3User authorization data
5. The fixed monitoring point or place from which the monitoring was carried out.
6. Frequency average bandwidth.
7. The number of times the frequency was fixed during monitoring.
8. Frequency occupancy in percent of the total monitoring time.
9. The correlation threshold indicates how reliably the frequency corresponds to a
sample spectrum . The higher, the more likely.
10. Class of electromagnetic radiation.
11. Accumulated spectrum and bandwidth images and occupancy graph. The
information in this column also contains active links (see Fig. 3.4).
fig. 4. 4Accumulated spectrum, bandwidth and occupancy schedule
12. You can get more detailed information about the measurement by clicking on the
" go to event " icon ( see fig . 3.5). And it is also possible to correct or delete
the measurement.
fig. 4. 5Detailed information about the measurement
The number of columns can be changed by pressing the "Columns" button on the
bottom edge and selecting the required number of columns in the additional window .
Page 7of30
User manual for Skudra Server v.5.3.61.
fig. 4. 6Changing the number of columns
The display of information on the side of the columns can be changed by clicking on the
"Grid display" button at the bottom of the page
fig. 4. 7Grid view button
Now, on the left side of the screen, instead of columns, pictures of the spectrum
accumulated in the measurements for each frequency are displayed.
fig. 4. 8Grid representation
Details can be obtained by clicking on any of the pictures.
Page 8of30
User manual for Skudra Server v.5.3.61.
fig. 4. 9Detailing in grid representation
In the upper right corner of the screen, above the map, there is a search menu window.
fig. 4. 10Location of the search window
When you left click mouse on it, it scrolls down, and you can enter search/filter
parameters (frequency, user, level) to select information.
fig. 4. 11Search window
Searching information - frequency, level, date can be entered in the fields with a
limitation from – to, thus expanding the search range. After entering the data in the search
fields, the filtered information appears in the columns on the left side of the screen.
Next to the search window are two square buttons :
1. DF ( bearing ) spread button.
2. Map layout button.
att. 4.12 Pelengācijas un kartes izklājuma pogas
Page 9of30
User manual for Skudra Server v.5.3.61.
By pressing the DF layout button, an additional window opens , in which, by default, the
names of Riga monitoring points are displayed:
fig. 4. 13DF pop-up window
To add other Latvian points, press "MANAGE DF":
Page 10of30
User manual for Skudra Server v.5.3.61.
fig. 4. 14DF Management window
Now you can add or remove the points needed for data analysis in the table. Instead of
the fixed points, you can also record longitude and latitude degrees, so you can see the bearing
picture from any other point in Latvia where monitoring with direction determination has
been carried out. It is also possible to change the color of each dot's outline:
fig. 4. 15Options for changing the colors of the directional beams
Page 11of30
User manual for Skudra Server v.5.3.61.
In the fields "Degrees" write the results of measurements, in the next cell the tolerance
+/-. By default, the tolerance is +/- 2. In the example picture, the map of surveying results from
all Riga monitoring points. It can be both zoomed in and out.
fig. 4. 16Map of bearing
The map layout button allows you to select map layers and overlays:
fig. 4. 17Map layout options
To return to the initial view, the "CLEAR" and "CLOSE" buttons must be pressed on the
DF layout screen.
Page 12of30
User manual for Skudra Server v.5.3.61.
fig. 4. 18How to return to the home screen
5 24/7
the "24/7" section of Skudra Server , you can view the measurements made during
monitoring with Skudra Patrol within the limits of whole ranges together with the spectrum
diagram of the waterfall.
When opening the section , columns with range monitoring diets are visible on the left,
and a map that can be zoomed in or out on the right. Highlighting one of the lines on the left
side at the bottom of the screen below the map, a spectrum diagram of the waterfall appears,
which can also be zoomed in or out:
fig. 5. 1Range monitoring data, map and waterfall spectrogram
In the data columns, you can see information about the point from which the
measurements were made. Frequency range and monitoring date and duration.
Page 13of30
User manual for Skudra Server v.5.3.61.
fig. 5. 2Range monitoring detail
Dragging the mouse cursor over the spectrogram of the waterfall changes the
information about the frequency and signal level in the field next to the spectrogram.
fig. 5. 3Waterfall spectrogram information
6 Broadcasting
Monitoring of broadcast ranges is performed at fixed points with the help of frequency
spectrum analyzer ETL and the results are automatically saved on the Skudra Server website
after the end of the measurements. With ETL, measurements of broadcasting stations and
DVBT signal levels, scanning of broadcasting and DVBT ranges, as well as deviations and MPX
measurements of broadcasting stations are performed. You can get to the broadcast
measurement results directly from the Skudra Server environment by clicking on the
"Broadcast" icon,
fig. 6. 1Broadcast icon SKUDRA Server
When opening one of the menus, we arrive at a page with signal level measurements of
broadcast stations (dBµV /m).
Page 14of30
User manual for Skudra Server v.5.3.61.
fig. 6. 2Measurements of broadcast station levels
In the left, upper corner of the screen, you can choose which monitoring point's
measurements to view.
fig. 6. 3Selection of monitoring point
Next to that, you can choose what kind of measurements you want to review (level,
direction, deviation, scan, DVB-T scan, DVB-T level or MPX).
Page 15of30
User manual for Skudra Server v.5.3.61.
fig. 6. 4Choice of measurement type
For measurements, with some exceptions, it is possible to choose the arrangement of
the data in a table or graphical representation.
fig. 6. 5Arrangement of data in a table
Only graphical display is for broadcast scan and DVB-T scan measurements. Below is the
broadcast scan schedule. When you move the cursor over the circles of the graph, you can see
information about the level at different points.
Page 16of30
User manual for Skudra Server v.5.3.61.
fig. 6. 6Broadcast station scanning schedule
DVB-T broadcast scan schedule.
fig. 6. 7Scan schedule for DVB-T stations
In the graphs of the levels of broadcasting stations, it is possible to view the graphic
changes of the levels of individual stations over a longer period of time. Before that, you must
select a specific frequency in the field next to "Schedule". Also in this graph, by following the
line with the cursor, it is possible to see the values at different points of the circle.
Page 17of30
User manual for Skudra Server v.5.3.61.
fig. 6. 8A schedule of individual broadcast station level changes during the period
In the table view, it is possible to change the number of columns on the screen, excluding
frequencies from the list.
fig. 6. 9Changing the number of columns in a table
Location directions of broadcasting stations at monitoring points are made with other
hardware (not ETL) and are described in the Argus software, as defined monitoring
measurements. After they are done, special csv format files are prepared at the points and
imported into the Skudra Server environment. This is to be done by clicking on the "Add new
measurement" button in the upper right corner of the "Broadcast" page.
fig. 6. 10Start of loading of broadcast station direction measurement files
You have to choose the location of the file and select the import option.
fig. 6. 11File loading process
Page 18of30
User manual for Skudra Server v.5.3.61.
N/A.
7 DF ( Direct Finding / direction measurements)
In section DF, are stored direction measurements made at monitoring points with the
Skudra Patrol software, with a condition that the operation of Skudra Patrol with direction
finding equipment is possible at monitoring point and the setting to send data to Skudra Server
is activated.
The DF section is activated by entering the Skudra Server website and clicking on the
corresponding "DF" icon.
fig. 7. 1Directional measurement icon in Skudra Server
A window appears with the ID numbers, locations, times and ranges of the saved
measurements.
fig. 7. 2Directional measurement data table
In the next step, highlight the required line and press the "CHOSE" button on the upper
left corner of the screen.
Page 19of30
User manual for Skudra Server v.5.3.61.
fig. 7. 3A path to directional measurement detail
Details of direction finding measurement and map with frequency direction, if frequency
direction finding was successful appears, which you can zoom in and zoom out.
fig. 7. 4Detailing of direction measurements with a survey map
You can return to the list using the "BACK" button
fig. 7. 5Return to the DF home screen
8 Equipment
The Equipment section of the system gathers information about the equipment at the
disposal of the monitoring department, which is used in the work process. Here you can find
information about equipment location and calibration dates, as well as equipment
instructions and calibration certificates, etc.
Page 20of30
User manual for Skudra Server v.5.3.61.
The Equipment section of the System is available to all users registered in the System in
reading mode.
You can get to the equipment registry directly from the SKUDRA Server environment by
clicking on the " Equipment" icon,
fig. 8. 1Equipment registry icon for SKUDRA Server
Opening one of the menus, we get to the list of equipment. The columns contain
information about inventory number, name, type, material responsible person, user, location,
calibration data and technical documentation or user manual.
fig. 8. 2Equipment Registry Master Table
By highlighting one of the lines, a details with all the above information and a link to the
documentation can be downloaded for familiarization purposes.
Page 21of30
User manual for Skudra Server v.5.3.61.
fig. 8. 3Single line detailing
The required number of columns can be turned on and off by pressing the "COLUMNS"
menu in the lower right corner of the page.
fig. 8. 4Option to change the number of columns
Adding new hardware is described in the RUNIS user manual.
9 Scheduler
This module is intended for Skudra Patrol measurement task planning from on user
interface to all registered Skudra Patrol instances.
fig. 9-1 Scheduler icon SKUDRA Server
Scheduler consist on 3 sections, where each section main functionality will be described in this chapter.
fig. 9-2 Scheduler sections
Page 22of30
User manual for Skudra Server v.5.3.61.
10 Measurement units
fig. 10-1 8.1 Measurement unit section
In this section user can see all registered Skudra Patrol instances, their parameters and
location, in table and map view. Each instance has fallowing parameters:
• Host – PC host name where is instaled Skudra Patrol;
• Status – status of Skudra Patrol instance, options are OFF/ON;
• Receiver – Skudra Patrol instance used receiver;
• IP address – ip adress to Skudra Patrol instancel;
• Latitude – Skudra patrol instance locations latititude (in WGS84);
• Longitude – Skudra patrol instance locations longitude (in WGS84);
Each Skudra Patrol instance have unique record in database, if in Skudra Patrol is
changed on of listed parameter (Host, Receiver, IP address) new instance record will be
created. When Skudra Patrol instance is set to remote, status update is send to server.
11 Measurement
fig. 11-1 Measurement section
Page 23of30
User manual for Skudra Server v.5.3.61.
Measurement section consist of user defined measurement tasks. Users with
corresponding rights can add, change and remove measurement tasks. It also provides
functionality to search defined tasks, it is possible to search by – Name, frequency range start,
stop frequency, receiver name.
fig. 11-2 Measurement edit window
Editing Skudra Patrol measurement task will show up form for creating and editing tasks, task
form corresponds to all the same range definition form in Skudra Patrol, for more details see
Skudra Patrol user manual “3.2. Range definition section”.
fig. 11-3 Skudra Patrol Range definition section
when connecting to Skudra Patrol instance to Server it also send available ML models
and spectrum Masks on this instance, see “3.6. Machine learning section” and “3.7. Masks
Page 24of30
User manual for Skudra Server v.5.3.61.
section”. After connecting instance it is possible to assig responding ML models and Masks,
that means, if Instance is disconnected, it is not possible to add it to task.
12 Schedule
Schedule section allows to plan predefined tasks to registered Skudra Patrol Instances.
fig. 12-1 Schedule section
Schedule section consist of two parts – predefined tasks and horizontal calendar
consisting of registered Skudra Patrol instances in separate rows. Multiple instances
(receivers) of one host are grouped.
To plan task in schedule, it is needed to drag and drop task in desired calendar row,
where is responding Instance, receiver.
fig. 12-2 Dragged and dropped task.
When task is dragged and dropped it is not saved in schedule, to save user need to
double click on it and edit/review tasks start, stop and recurrence. Only after pressing “SAVE”
button task will be sent to Server.
fig. 12-3 Planed task review.
Page 25of30
User manual for Skudra Server v.5.3.61.
fig. 12-4 Repeated task
it is also possible to plan repeated task, repeating period options are following:
• Every time at …;
• Every week on curent weak day;
• Every month on curent month day;
And also last measurement date, until which date all repeated tasks will be created.
By changing task start and stop date it will show in task list overlapping tasks.
fig. 12-5 Saved tasks represents color-coded statuses: grey – saved, not sent. Blue – sent and accepted.
13 Reports
This module is intended for conducting reports on monitoring activities, as well as on
current events in the company and industry, both in Latvia and around the world. Access to
the section is through the Skudra Server app by clicking on the "Reports" icon.
fig. 13. 1Reports icon SKUDRA Server
Page 26of30
User manual for Skudra Server v.5.3.61.
A window appears where you can select the type of report. They are MONITORING,
ACTIVITIES and SKUDRA PATROL. You can also choose a reporting period.
fig. 13. 2Selection of report type
MONITORING. Graphical information about fixed and mobile monitoring reports drawn
up in the defined period.
fig. 13. 3Monitoring reports window
ACTIVITIES. Information about current events in the company, industry and binding
regulatory acts. The activity section is used as a system for recording daily and other important
tasks, the textual information of which is used to create various reports. It is possible to add
classifiers from the Administration environment.
fig. 13. 4Current information window or ACTIVITIES
The list can be exported as an xls file by pressing the button "EXPORT" in the upper right
corner of the screen
Page 27of30
User manual for Skudra Server v.5.3.61.
fig. 13. 5Option to export current information
As a result, the downloaded files folder shows:
fig. 13. Appearance of the 6information export xls format file
SKUDRA PATROL. Still to be clarified. Gets to the screen from the main SKUDRA Server
window.
fig. 13. 7SKUDRA Patrol window in the SKUDRA Server app.
Page 28of30
User manual for Skudra Server v.5.3.61.
14 Sample spectra
After logging in to Skudra Server , in the upper right corner of the screen, next to the
user name, there is a down arrow, which when pressed brings up the " Sample Spectra " menu.
fig. 14.1 Sample spectra menu button
Selecting " Sample spectra " opens a window showing lines with the basic information
of the so-called sample spectra . When you move the cursor over one of the rows, the
spectrogram, radiation class and name appear on the right side of the screen. The monitoring
program Skudra Patrol uses sample spectra in its operation , that is, it compares the frequency
parameters recorded in daily measurements with one of the sample spectra .
fig. 14.2 Table of sample spectra and spectrograms
Page 29of30
15 Appendix
16 Abbreviations and terms used.
VASES – State joint-stock company "Elektroniskie sakari"
RUNIS – information system of the radio frequency monitoring department
RMP – radio monitoring point
EMI – electromagnetic radiation
EMS – electromagnetic situation
NRS – Unidentified Radio Signal
DF – Direction Finding , determination of direction
TMS – transportable monitoring station