CORRIGENDUM No. 2
SUPPLY TENDER DOSSIER
EuropeAid/127469/D/SUP/HR
Contract title: „National Border Management Information System – Phase III”
In the Corrigendum no 2 to Tender dossier (Draft contract) launched on 08/08/2009, the article 3.1 is modified and replaced by the subsequent text:
Instead of:
3.1The price of the supplies shall be that shown on the financial offer (specimen in Annex IV). The total maximum contract price shall be: ______EUR (<amount in words>), excluding VAT and other taxes of which
75 %(<amount in figures>EUR) is paid by IPA and
25 %(<amount in figures>EUR) is paid by the national co-financing.
VAT and other taxes will not be paid by the European Commission on the funds from the EC and such taxes and duties, if attributable, are payable by the National Authority to the Contractor, and in accordance with the Croatian VAT Laws.
Should read:
3.1The price of the supplies shall be that shown on the financial offer (specimen in Annex IV). The total maximum contract price shall be: ______EUR (<amount in words>), excluding VAT and other taxes of which
75 %(<amount in figures>EUR) is paid by IPA and
25 %(<amount in figures>EUR) is paid by the national co-financing.
In the Corrigendum no 2 to Tender dossier (Special Conditions) launched on 08/08/2009, the article 31 is modified and replaced by the subsequent text:
Instead of:
Article 31Provisional acceptance
The Certificate of Provisional Acceptance must be issued using the template in Annex V. The Contractor shall deliver to the Contracting Authority, together with the request for provisional acceptance, 3 copies of the Provisional Acceptance Certificate signed by the Contractor and the Beneficiary as well as the official Certificate of Origin for all delivered supplies. The request for provisional acceptance to the Project Manager (Contracting Authority) should take place before the deadline specified in Annex V.4. Programme of implementation of tasks. The provisional acceptance certificate will be issued by the Contracting Authority as stipulated in Article 31 of the General Conditions.
The Certificate of Provisional Acceptance shall be issued by the Contracting Authority only upon fulfilment of all requirements related to provisional acceptance as specified in the Annex II+III: Technical Specifications + Technical Offer.
Should read:
Article 31Provisional acceptance
The Certificate of Provisional Acceptance must be issued using the template in Annex V. The Contractor shall deliver to the Contracting Authority, together with the request for provisional acceptance, 3 copies of the Provisional Acceptance Certificate signed by the Contractor and the Beneficiary as well as the official Certificate of Origin for all delivered supplies. The request for provisional acceptance to the Project Manager (Contracting Authority) should take place before the deadline specified in Annex V.4. Programme of implementation of tasks. The provisional acceptance certificate will be issued by the Contracting Authority as stipulated in Article 31 of the General Conditions.
Partial provisional acceptance shall not be issued by the Contacting authority for this Contract.
The Certificate of Provisional Acceptance shall be issued by the Contracting Authority only upon fulfilment of all requirements related to provisional acceptance as specified in the Annex II+III: Technical Specifications + Technical Offer.
In the Corrigendum no 2 to Tender dossier (Technical Specifications) launched on 08/08/2009, the following parts are modified and replaced by the subsequent text:
Heading: 1.1 Strategic Technical Requirements
Subheading: 1.1.5 Security
Page No.: 11
Instead of:
NBMIS shall achieve a security level compliant with Common Criteria EAL3.
Tenderers shall propose and describe a security framework that shall offer a level of security compliant with CC EAL3.
The security of the network infrastructure is out of the scope of this call for tender
Should read:
NBMIS shall achieve a security level compliant with Common Criteria EAL3.
Tenderers shall propose and describe a security framework that,when implemented, shall offer a level of security compliant with CC EAL3 for the NBMIS database and the Operating System (OS) on central blade servers.
The security of the network infrastructure is out of the scope of this call for tender.
Heading: 2.1 Management of the project realization (Deliverable 0)
Subheading: 2.1.4 Planning and reporting
Section: Periodic reporting
Paragraph No.: 2; Item No. 18
Page No.: 32
Instead of:
At the first scheduled monthly meeting the Supplier shall provide:
(12)Schedule for Monthly reports
(13)Schedule for Reports on completion of individual sub-systems
(14)Schedule for Reports on completion of the whole installation
(15)Schedule for Minutes of meeting for every meeting
(16)Schedule for Final report after last roll-out
(17)Schedule for Reports on completion of the training
(18)ISO 20000 standard in electronic version together with ISO/IEC 20000 Checklist.
Should read:
At the first scheduled monthly meeting the Supplier shall provide:
(12)Schedule for Monthly reports
(13)Schedule for Reports on completion of individual sub-systems
(14)Schedule for Reports on completion of the whole installation
(15)Schedule for Minutes of meeting for every meeting
(16)Schedule for Final report after last roll-out
(17)Schedule for Reports on completion of the training
(18)ISO 20000 standard ordered by the Supplier for itself either from the Croatian Standards Institute or directly from the ISO organization shall be presented to the Beneficiary, to be used as the defining standard for the execution of the project, and additionally electronic version of the ISO/IEC 20000 Checklist shall be delivered and also fully utilised in the execution of the contract.
Heading: 2.2 Equipment for the NBMIS System (Deliverable 1)
Subheading: 2.2.1 Scope of deliverable
Paragraph No.: 3
Page No.: 34
Instead of:
Tenderer shall provide in his offer Statement of availability of authorized service provider in Croatia for all hardware, software and middleware.
Should read:
Tenderer shall provide in his offer Statement of availability of authorized service provider in Croatia for all hardware, proprietary software and proprietary middleware.
The Tenderer shall provide in the offer its Statement confirming its obligation as the service provider for the Beneficiary institution for all open source software and open source middleware supplied through this contract.
Heading: 2.2 Equipment for the NBMIS System (Deliverable 1)
Subheading: 2.2.2 ANPR testing
Paragraph No.: 1
Page No.: 47
Instead of:
It is not acceptable for ANPR to recognize any other part of vehicles as number plates. Failure to register number plates will result in the equipment being rejected as non compliant. The Supplier shall replace this equipment with equipment that meets the technical requirements in full without additional cost for the contracting authority or the beneficiary.
Should read:
It is not acceptable for ANPR to recognize any other part of vehicles as number plates. Failure to register number plates will result in the equipment being rejected as non compliant. The Supplier shall replace this equipment with equipment that meets the technical requirements in full without additional cost for the contracting authority or the beneficiary.
In order for the equipment to be approved by the Beneficiary institution maximum 1failure out of 1000 recognitions may occur.
Heading: Heading: 2.2 Equipment for the NBMIS System (Deliverable 1)
Subheading: 2.2.3 System testing
Section: Prototyping
Page No.: 49
Instead of:
Prototyping
Because of the intrusive civil works required in the sensitive BCP locations the Supplier shall be obliged to first install one prototype unit on one traffic line for trucks and one for mix traffic on one border crossing point. This prototype shall be used for a controlled consecutive four hour test using live traffic without NBMIS application. The system shall demonstrate a minimum accuracy of 95 per cent during this test.
The Supplier, monitored by the Beneficiary’s test team, shall test ANPR through NBMIS application after beneficiary receives and approves Supplier’s prototype test results for ANPR without NBMIS application.
Only following a successful ANPR / NBMIS test may the Supplier install ANPR on traffic lines for the selected border crossing points.
Should read:
Prototyping
Because of the intrusive civil works required in the sensitive BCP locations the Supplier shall be obliged to first install one prototype unit on one traffic line for trucks and one for mix traffic on one border crossing point. This prototype shall be used for a controlled consecutive four hour test using live traffic without NBMIS application. The system shall demonstrate a minimum accuracy of 95 per cent during this test.
Consecutive four hour test using live traffic shall include all traffic in four hours. For the test to be valid minimum 200 samples of number plates shall be tested on every traffic line. For the traffic lines where 200 samples have not been collected, the test shall continue after the 4 hours period, until this number of samples (200) is collected.
The Supplier, monitored by the Beneficiary’s test team, shall test ANPR through NBMIS application after beneficiary receives and approves Supplier’s prototype test results for ANPR without NBMIS application.
Only following a successful ANPR / NBMIS test may the Supplier install ANPR on traffic lines for the selected border crossing points.
Heading: 2.3 Mobile NBMIS Application detailed design specifications
(Deliverable 2)
Subheading: 2.3.1 System performance
Paragraph No.: 3
Page No.: 54
Instead of:
In order to facilitate cooperation with the Beneficiary counterparts the Supplier shall deliver to the beneficiary ISO 12207 standard in electronic version together with the Suppliers version of the ISO/IEC 12207 Checklist for Software Life Cycle Processes.
Should read:
The Supplier shall order for itself the ISO 12207 standard either from the Croatian Standards Institute or directly from the ISO organization andpresent it to the Beneficiary institution. The supplier must deliver electronic version of the ISO/IEC 12207 Checklist for Software Life Cycle Processes to the Beneficiary institution.Application of these standards will be an integral part of the contract delivery.
Heading: 2.3 Mobile NBMIS Application detailed design specifications
(Deliverable 2)
Subheading: 2.3.2 Provisional acceptance
Page No.: 58
Instead of:
The following documents shall be required from the Supplier as a precondition for the provisional acceptance. Provisional acceptance shall not be granted without presentation of the complete set of at least the following documents:
(1)Customer requirements specification;
(2)System requirements specification;
(3)Interface requirements specification;
(4)Traceability Matrices Between Customer Requirements and System requirements
(5)System architecture design;
(6)Traceability Matrices Between System Requirements Specification and System architecture design
(7)Software requirements specification;
(8)Traceability Matrices Between System Requirements Specification and Software Requirements Specification
(9)Software architecture design;
(10)detailed design specification;
(11)database design
(12)Traceability Matrices Between Software Requirements Specification and Detail design
(13)GUI specification documentations in English and Croatian
(14)Prototype and mockups acceptance acquired from the beneficiary
(15)ISO 12207 standard in electronic version together with ISO/IEC 12207 Checklist for Software Life Cycle Processes
Final version of documentation shall be delivered in electronic version in English and Croatian language.
Should read:
The following documents shall be required from the Supplier as a precondition for the provisional acceptance. Provisional acceptance shall not be granted without presentation of the complete set of at least the following documents:
(1)Customer requirements specification;
(2)System requirements specification;
(3)Interface requirements specification;
(4)Traceability Matrices Between Customer Requirements and System requirements
(5)System architecture design;
(6)Traceability Matrices Between System Requirements Specification and System architecture design
(7)Software requirements specification;
(8)Traceability Matrices Between System Requirements Specification and Software Requirements Specification
(9)Software architecture design;
(10)detailed design specification;
(11)database design
(12)Traceability Matrices Between Software Requirements Specification and Detail design
(13)GUI specification documentations in English and Croatian
(14)Prototype and mockups acceptance acquired from the beneficiary
(15)ISO 12207 standard ordered by the Supplier for itself either from the Croatian Standards Institute or directly from the ISO organization shall be presented to the Beneficiary and additionally electronic version of theISO/IEC 12207 Checklist for Software Life Cycle Processes shall be delivered.
Final version of all NBMIS system related documentation shall be delivered in electronic version and hard copy (except the ISO standard) in English and Croatian language.
Heading: 2.4 Realization of the Mobile NBMIS application; including unitary,
integration and performance test (Deliverable 3)
Subheading: 2.4.1 Design
Paragraph No.: 2
Page No.: 59
Instead of:
At the project initiation meeting the Supplier shall provide the current ISO 9126 standard in electronic version to the Beneficiary together with a proposed working checklist based on the standard as a basis for monitoring of software development.
Should read:
The Supplier shall order for itself the current ISO 9126 standard either from the Croatian Standards Institute or directly from the ISO organization and present it at the project initiation meeting.
The supplier must deliver electronic version of the checklist based on the standard as a basis for monitoring of software development to the Beneficiary institution.
Heading: 2.4 Realization of the Mobile NBMIS application; including unitary,
integration and performance test (Deliverable 3)
Subheading: 2.4.7 Provisional acceptance
Section: User Documentation
Page No.: 68
Instead of:
The following documents for each product delivered shall be required from the Supplier as a precondition for the provisional acceptance. The Supplier shall be aware that provisional acceptance can not be granted without the presence of the complete set of documents as follows:
(1)User manual
(2)System Test plan, test case, test procedure, test data and test result
(3)Software Test plan, test case, test procedure, test data and test result
(4)Installation manual
(5)Acceptance test plan
(6)Acceptance record
(7)Traceability Matrices between Software Requirements Specification, Software Design Document, Software Test Cases and Code Coverage.
(8)Traceability Matrices between Software Requirements Specification, Software Design Document and Software Units
(9)Documentation of source code, algorithms, interfaces, SDKs and APIs.
(10)Source code metrics report
(11)ISO 9126 standard in electronic version together with checklist which shall be based on the current ISO/IEC 9126 standard
(12)ISO/IEC 15910 and ISO/IEC 18019 standardsin electronic version
Final version of documentation shall be delivered in electronic version and hard copy in English and Croatian language.
Should read:
The following documents for each product delivered shall be required from the Supplier as a precondition for the provisional acceptance. The Supplier shall be aware that provisional acceptance can not be granted without the presence of the complete set of documents as follows:
(1)User manual
(2)System Test plan, test case, test procedure, test data and test result
(3)Software Test plan, test case, test procedure, test data and test result
(4)Installation manual
(5)Acceptance test plan
(6)Acceptance record
(7)Traceability Matrices between Software Requirements Specification, Software Design Document, Software Test Cases and Code Coverage.
(8)Traceability Matrices between Software Requirements Specification, Software Design Document and Software Units
(9)Documentation of source code, algorithms, interfaces, SDKs and APIs.
(10)Source code metrics report
(11)ISO 9126 standard ordered by the Supplier for itself either from the Croatian Standards Institute or directly from the ISO organization shall be presented to the Beneficiary and additionally electronic version of the checklist which shall be based on the current ISO/IEC 9126 standard shall be delivered.
(12)ISO/IEC 15910 and ISO/IEC 18019 standardsordered by the Supplier for itself either from the Croatian Standards Institute or directly from the ISO organization shall be presented to the Beneficiary
Final version of all NBMIS system related documentation shall be delivered in electronic version and hard copy (except the ISO standard) in English and Croatian language.
Heading: 2.6 Successful integration of all equipment with NBMIS application
from deliverables 2, 3 and 4 (Deliverable 5)
Subheading: 2.6.1 Integration and installation of the system
Page No.: 81
Instead of:
2.6.1 Integration and installation of the system
For this deliverable the Supplier shall carry out the operations necessary for integration and installation including software and hardware elements, firstly to ensure the conformity of all equipment with NBMIS system which is established in Phase 1 and Phase 2 of the NBMIS project and secondly to allow the immediate use of it by the users.
The realization assumes the supply of all the applications, functions, and components necessary for the operation of the NBMIS according to the Functional Users’ Needs Description.
The Tenderer need to offer middleware and Commercial off-the-shelf (COTS) softwarenecessary for successfull implementation of all equipment in NBMIS application from deliverables 2, 3 and 4.
The current software in use is described below. However the Beneficiary shall consider a viable alternative open source middleware proposal.
The Tenderer shall include in his offer licence for every middleware and Commercial off-the-shelf (COTS) software (open source of proprietary) and propose organization of training for the beneficiary engineers (7 persons) for all middleware and Commercial off-the-shelf (COTS) softwarecomponents.
If the tenderer proposes middleware or Commercial off-the-shelf (COTS) softwaredifferent than that described below then it is necessary to state how the tenderer plans to replace the existing middleware or Commercial off-the-shelf (COTS) software (including all locations from Phases 1 and 2 of the NBMIS project)as a deliverable under the scope of this tender component.
For all the middleware and Commercial off-the-shelf (COTS) software the Supplier shall deliver technical documentation and training materials. Installation procedures for any middleware and Commercial off-the-shelf (COTS) softwareare required.
For any middleware and Commercial off-the-shelf (COTS) software perpetual licences shall be provided. Warranty shall explicitly include the provision of updates, patches, and newer versions as soon as published by the respective manufacturers during the Warranty Period, without any additional cost for the beneficiary or the Contracting Authority.