Development of Capabilities for Seismic and GPS data integration, processing, storage, archival and dissemination at INCOIS and IMD Data Centers Addendum to Tender, INCOIS: PUR: 14//2010 (Note: Modification given under column is to be complied with, while Clarification, clarifies the points raised during pre-bid discussion on 11 th June 2010 and asked after. (Clarifications are given grouped under different Heads: Data acquisition, Error correction & processing, Database system, Storage &Archival, GPS related, General& Financial). Additional requirement(option): An additional component Requirements of Earthquake Risk Evaluation Center (EREC) data Center given as Annexure -1, is included as part of this tender. It is to be quoted as an Optional Item. The vendor is required to provide a technical solution, system architecture, generic specifications of hardware/software, supply of application software, software development/customization, system integration, installation and testing as per the requirements mentioned in Annexure-1. This additional component is required to be supplied and implemented at IMD Centre only. INCOIS/IMD will procure required hardware and software as per generic specification given by the vendor. Vendor is required to give a separate technical proposal and financial offer for this component viz., EREC Data Centre, under this present tender with all other purchase and other conditions remaining same. This optional requirement will be treated separately and will not be taken into the total price. Vendor cannot quote only for this part for this tender. Delivery period is one year. Details of the new requirement, delivery schedule is given in Annexure-1 of this addendum. Regarding clarification for this additional component only, vendor may forward their queries through Email before 10 th July 2010, to the same contact address which has already been mentioned in the tender document. The Addendum for this additional component, if necessary, will be placed in the website on 14/7/2010.
(A) Modifications of the clause Page No. 2 Clause Modification Clarification sought from vendor Date and Time for Submission of Tender: 1700Hrs of July 23, 2010 Clarification 6 vi Date of opening of Financial offer of Technically qualified Firm: 1600Hrs of August 18, 2010 Clause added: The data centre vendor, being an end application provider has to co-ordinate with VSAT communication link provider, respective co- coordinators of Regional seismic network, PIs (Principal Investigators) /providers who maintain the seismic/gps instrument to get continuous waveform data/gps data from field stations and Regional Seismic network centres as best possible in line with project objective. 7 4. xv Continuous waveform retrieval: Suitable S/W is to be designed and developed for storing continuous wave form data of all stations and later query & retrieval of such information in SEED or mseed format from the data base in the form of network/sub-network list in the denominations of year, month, day, hour and minute. The application software should have the option for decimating the higher sampling waveform data (requested in the query) to 20sps or 1sps and provide the waveform output file in mseed/seed format as mentioned above. - -
12 5 v The Data centre operation will be on 24x7 basis by the vendor. The vendor should make available at any time one system administrator /integrator for the round the clock operation& maintenance at each of the data Centre location of INCOIS and IMD. He should be a degree holder and should have been involved in the set-up of Data centre from beginning of the project. Please clarify the service coverage required at IMD. We need at data centre one person per shift on 24x7 basis. The vendor/ person at the Data centre has to co- ordinate with respective providers (given in clause vi, page 6 above) for any problem in receiving continuous seismic wave form data /GPS data. The vendor will be provided contact address with telephone No. email address of these persons. 9 10.0 Time schedule for selection process: Submission of Technical &Financial Tenders in separate sealed covers: July 23, 2010 ( 1700Hrs) Technical presentations by Firms: July 26, 2010 Opening of Financial offers of Technically qualified firms: August 18, 2010( 1600Hrs)
(B) Clarifications Sl. No Clarification sought by the vendor Clarification Data acquisition,error correction & processing 1 2 Integration with existing data processing system; GPS data Application software: Apart from existing seismic data and processing Application software (Response Hydra, SEISCOM P) and for GPS data processing (RTnet/3D Tracker software, Bernese/GAMIT software mentioned in RFP), is there any other Application software required to integrate for data processing. Are we expected to interface with any instrumentation at any of The field location directly? In case we have to interface the devices directly can you provide the protocols? No. Even though, it is not the direct responsibility of the Data vendor to interface the instrument, the vendor has to co- ordinate with VSAT vendor (who provide communication solution in transfer of data) for any specific setting in the field instrument that may have to be done and ensuring end application at data centre acquire the continuous waveform data from Seismic / GPS data acquisition system on real time basis at each data centre. There must not be any data-gaps in the continuous waveform data being acquired. The list of available equipments (with make and model no.) at each filed site is enclosed with the tender document. The vendor may go through the web-sites of corresponding OEM for more details of the equipments. It is the responsibility of the vendor to understand the recording data formats and protocols being used by these data acquisition systems.
3 4 5 6 7 8 9 Will INCOIS provide all the required technical details and algorithms for processing of data as part of applications being proposed. Will there be any third party application other than GPS and Seismic data stations, for which interface is required. Is there any relation between seismic data and GPS data? Will there be any analysis involving both the data. How to read GPS wave form data? Is it fixed or variant? Is there any GPS toolkit for integration? How to connect and receive Data from VSAT What will be contents of data received from GPS stations It is expected that the vendor should understand the technical details and provide IT solution to achieve the objectives of the project. Seismic and GPS data: There is no relation with regard to data formats of GPS and Seismic. They are different from each other and hence required to be handled separately. At present, no analysis involving both the data. 7. GPS wave form should be in term of lat/long/height variation with time 8. No there any toolkit except mentioned software The contents of data received from GPS station are Lat/long/height and met data. 10 11 Is usage of SEISAN mandatory? If yes, will there be any specifications/ standards for interfacing SEISAN with the proposed data base. Please confirm that each data centre must acquire waveform, state---of---health, response and meta---data for each instrument for which data are acquired. The SEISAN software will be used for post-processing involving user-interaction for finalization of source parameters of earthquakes occurred and subsequently prepare the seismological bulletins. It is expected that Vendor may visit IMD to understand the requirements under this clause. The data centre must acquire the continuous waveform data. The remaining state-of-health, meta data is also required at data centre along with the waveform, if available and the field station seismic/ GPS equipment support the transmission of these parameters continuously over VSAT.
12 Please confirm that the successful vendor will be required to interact directly with the remote station Source device and that the software will be responsible for acquiring the real-- -time data, providing Error correction between the Remote and central site and for Acquiring any available SOH, response and meta---data. See clarification provided Sl.2 13 Please confirm that the central site software will only be required to support error correction in accordance with the protocols of the original digitiser or GPS manufacturer. Please further clarify that this support will be for the existing code installed and that any changes required to support future software versions installed on remote site equipment, will be an extra cost item. The Datacenter vendor will not be responsible for loss of data and increase in latency due to VSAT communication link and due to limitation of buffer memory in the field seismic recorder/gps receiver. However, it is expected from the data centre vendor to co ordinate with VSAT communication provider for best possible solution keeping project objective. (The VSAT is specified for UDP unicast and multicast routing as requirement. However, the vendor has to see whether this feature is supported by the end remote equipment.) 14 15 We understood from discussions during the pre-bid meetings that the system should recover from Communications outages of at least 30 minutes. Please confirm that each of the Seismic digitisers and GPS receivers are configured with this length of data buffer for on---line data--re-request. If not please confirm that this data will be available from data buffered on the VSAT modem. Please confirm that any loss of data caused by insufficient bandwidth on the VSAT system which may result from flow control issues will not be the responsibility of the data center vendor. As given for Sl. No. 13 above
16 17 18 19 20 21 22 23 Please confirm that any loss of data resulting from insufficient outbound bandwidth will not be the responsibility of the data centre vendor. Can we assume that where TCP/IP socket connections are used for data communications between the remote site digitiser and acquisition software, that the error correction provided by the underlying TCP/IP protocol will be fully satisfactory? Can we assume that where TCP/IP socket connections are used that two connections will be available in order to implement fully redundant acquisition systems at the central site locations? Can we assume that the VSAT will fully support multicast routing for those digitisers that use this protocol Will the VSAT system support IP fragmentation? Can we assume that the flow control between the remote site device and remote site VSAT terminal will be managed by the remote site VSAT terminal and that any loss of data or erratic performance of the error correction protocols caused by improper flow control management will not be the responsibility of the data centre vendor? Please confirm that the 10 second latency for real---time data will be waived following VSAT outages where TCP/IP sockets Connections are used. Please confirm if the Q330 Sites are equipped with Baler data storage systems or another model? Q330 are equipped with baler type storage (Model No. PB-14F)
24 25 26 Please confirm that all GPS Systems with Ethernet connectivity are capable of streaming RTCM data via TCP/IP or UDP connections. Please confirm whether the vendor is required to the cost of additional station licenses for the Existing Hydra installations. Please confirm that there is a requirement for software tools to check the waveform data for incorrect instrument response. We understand that data center operators must have an independent waveform quality tool to ensure the correct response for any station within the network The GPS receiver details are provided in Annexure-2 The vendor to see scope of work and deliverable as per RFP. Yes, However, the vendor may give as an optional item, which INCOIS may buy. 27 We understand that the response management system must automatically produce the various response data products required by the real-time processing and off-line processing systems, and that these systems should be updated at all times. Please confirm. The vendor may give this as part of architecture and design solution for the Data centre. 28 Please confirm that the response management system must be able to input and output response in SAC, SEED and the various formats required by the real-time and off line processing systems Output continuous data in mseed/seed format 29 30 Please confirm that suitable security and quality control checks are required to access and change information in the response management system. Seismic data and GPS data format? Yes All the continuous seismic waveform data being received from various field stations should be converted to SEED/mSEED format for final storage and integration with suitable RDBMS for meeting the requirements. Similarly for GPS, the standard
31 32 Integration of incoming data stream format Seismic data recording Station equipment parameters format? All the incoming continuous raw waveform data in heterogeneous formats (as mentioned in clause viii at page no.6) required to be handled The details are given in Annexure-2 of the tender document. It is the responsibility of the vendor to understand the recording data formats and protocols being used by these data acquisition systems. 33 34 35 36 Points need to be clear RFP(section 4 viii, ix- Interfacing at Regional centre &Integration with Existing data processing system) SEISAN database Format? ED Database: SEISAN to be analyzed? Phase arrival measurement, hypo central solutions, fault plane solutions How to integrate with the existing seismic applications of INCOIS and IMD? The data centre vendor has to provide SEED link server at each of the Regional Data centres specified and interface with existing Regional network seismic data server and Customer End(CE) router of Terrestrial line(mpls) at respective locations and transport the seismic data including meta data to data centres of INCOIS and IMD. (Terrestrial link will be provided by INCOIS). INCOIS will provide also server hardware as per specification given by vendor. The CE router of MPLS link at INCOIS and IMD will be interfaced with seismic data acquisition/processing server at respective location. The phase-picks data is organized in a database like structure in the ASCII file system and consists of many sub-directories as per year and month. More details on SEISAN data base can be had from the website http:// http://www.uib.no/rg/geodyn/artikler/2010/02/software. The vendor may visit IMD Centre to understand the details on the SEISAN. -do- Through SEED-link protocol. 37 Seismic centres and seismic digitizer type? The details of the seismic recorders are given in Annexure-2 of the tender document. (Some of the seismic instruments types are: Retek 151-120, CMG- 3T, CMG 40T, Trillium 240(Nanometrics), STS-2(Kinemetrics), Quandra Q330 (Kinemetrics)
It is the responsibility of the vendor to understand the recording data formats and protocols being used by these data acquisition systems. Database system, Storage &Archival 38 39 40 41 42 43 Back end application. Is this application intranet(or) internet The storage specification mentioned is for current capacity of the seismic and GPS data or does the seismic and GPS data does include future expansion Storage requirements are given in 4.xxi. Is this inclusive of processed data? If not please specify? Please confirm that each data Centre should be configured with two fully redundant acquisition servers and that each Server should acquire data from the entire network. What is the Tier of data centre? ( Tier 1,2,3 or 4) What is the level of availability needed from the overall solution? Both The storage specifications mentioned, is the indicative storage size to meet the requirements of 300 seismic stations and 100 GPS stations. At present, the storage size does not include the future expansions. However, the proposed system should have the scalability option. The storage requirement given is inclusive of processed data. However the volume of the processed data (location, time and magnitude) is very small and the storage is mainly of storing continuous waveform seismic data and GPS data in a standard format. The data centre should be designed for 99.99% availability.
44 Redundancy levels=n+1 or 2(N+1) 45 46 47 Seismic data centre standard-define? Do you need Database Server to provide active-active clustering for providing fault tolerance from hardware failures or planned outages and load balance across all clustered nodes for achieving availability level up to 99.99%? Is 99.99% availability includes routine maintenance and failover time mentioned in RFP? Are you expecting continuous access of data, even in case of any node of cluster go down, all the data should be available from surviving node without any downtime As given for Sl. No 41-43 above 48 49 50 Do you need database level storage management mechanism, which should enable the availability by means of creating redundancy, automatically balance the data files across the available disks, i/o balancing across the available disks for the database for performance, availability and management? Should the database server provide support for native spatial data formats within the database, co-located with the attribute data? Should it enable to preview the data by simple SQL queries, and still have underlying database strengths of scalability, manageability, availability and security? Do you need the database server to support full 3D Data Model (3D Geometrics, surfaces, TINS, Point Clouds), all geospatial data INCOIS already has RDBMS, ETL tools in a cluster configuration with all the capabilities. The vendor is required to build a solution based on existing RDBMS & tools only.
including vector and raster data, topology, and network models. 51 52 53 54 Do you need inbuilt functionalities like Linear referencing system, GeoRaster data type, Topology data model, spatial analytic functions, Geocoding engine, and Routing engine within the database. Do you need database support option of different partitioning schemes within the database (Range, List, Hash & combinations) to split large volumes of data into separate pieces or partitions, which can be managed independently? Are you looking database partitioning for enhance the performance, and help in managing huge volumes of data and should provide foundation for Information Life Cycle Management (ILM). Do you need database self-diagnostic engine (automatic database diagnostic monitor) inbuilt into core database? Do you need Option for Automated/manual identification and tuning of high load SQL Statements and provide details about dynamic tuning capability of the database depending on workloa d requirement, system resources etc. As given above GPS related Queries 55 Page4-1,3:Please advice what exactly meant by old data and what is the format and size, content 56 Page7-x: can the bidder/contractor provide alternate SW solutions instead of (GPSS) RT net and (geodesic) 3D tracker and Bernese or these software packages already in Seismic data, SEED format, size within the capacity of storage system Please see clarification provided in Sl.61
use by the contracting authority? 57 Page 8- xviie: Does this mean that SW developed for this project will be considered also as Free Ware? 58 Page9-xix: What exactly mean by Data Processing? ( In the context of GPS, are we talking about the reference station Software management or we are taking about baseline processing etc; please? 59 Section 1.3 Objective of the project, paragraph after section ix, o page4: If the selected contractor for the Project is subsidiary or related to a equipment manufacturer, will it be a conflicts of interest based on the above statement that the contractor should provide generic specification of the additional hardware/ software and application software required at each locations f INCOIS and IMD, please? 60 Section 4: Functional Requirement, Page7, x: Instead of transmitting in native binary format, will the Department accepts, BINEXT format, a public domain and independent binary format supported by major manufactures? The source code of all customized software developed under this project will be property of INCOIS and IMD, who will use this software in their own Projects and will not sell to anybody outside. The vendor should provide this software under no-disclosure guarantee as given in the Tender. It is about baseline processing etc We have asked selected vendor to give generic specifications, not proprietary specifications, of the hardware and system software. The specifications will be reviewed by INCOIS and IMD experts and will be procured as per project requirement. Some of the GPS manufactures provide processing software with more features specific to their native data format. Hence it is planned to provide facility to store also this native format of GPS receiver in the data centre other than RINEX format, to be useful to some users. However, BINEX format also additionally tried as an option for those receivers which support this format.
61 Section 4, Page 7 xi It appears that the department already owns RT net and 3D Tracker software for real-time processing, will the Department willing to consider a better and integrated software which could operate in parallel with the Departments current two software, RT net and 3D Tracker software which ar proprietary are acceptable? INCOIS and IMD do not have this SW. RT net and 3D tracker were selected based on our requirement of real time processing for Tsunami warning system (as well as for earth crust movement) and being used elsewhere in the world ( Ex. In Geonet network in Japan) for such application. While the vendor provide solution with these SW as has been asked, the vendor could offer also any other proven SW for these applications and to give it as an option. These SW could as well be operated in parallel, if suitable. 62 Section 4, Page 7 Relating to GPS data, What is the real time display of wave forms, can the Department, please provide a graphical example? Alternatively, is the Department willing to consider other graphical forms of incoming GPS data display 63 Page 7 xvi: Kindly do advices the RDBMS used by the Department today? 64 Page7, xxix: Please do advice regarding the communication link, data bandwidth and speed used for linking INCOIS and IMD, please? Existing Real time Display system in Tsunami Warning system in INCOIS is to used. Real time display, lat/long/height/met data variation with time Oracle for seismic data acquisition and processing It is 2Mbps MPLS. However the speed will be increased higher, if required, with more number of stations added in future. 65 General Question: Some GPS/GNSS receivers do not appear to have inbuilt facility to store data hence an appropriate mechanism is required to store the data in case of outage for transmission We have not made any mandatory requirement in our Tender any specific storage in VSAT modem nor for any external storage medium outside the GPS receiver.
over VSAT or some VSAT modems have the capability to cache and store data directly without any storage media in between GPS/ GNSS receiver and VSAT modem which can be later transmitted further down the system. Please which of the arrangement is required? General 66 67 Is there any need for large screen displays in house? Do we have to give our recommendations for the UPS, DG, and other related data centre components or do we have to quote them as well?. No The vendor should provide the details of UPS power, DG and other environmental details for implementing the project as per clause Section-4, ix, page no.6 of the tender document. INCOIS will arrange these facilities. Financial 68 Total cost specified in the Table shouldn t include the cost of optional items. In this case, the Table can be modified to identify the actual cost and the additional optional cost. Optional items specified and item specified as any other items including license fee etc will not be taken into total cost. However the vendor has to provide cost for the optional items without which the tender will be rejected. Also, the vendor may specify any other items, licenses etc, along with price and which are required for the project but not included in the Price bid format.
69 The Bank Guarantee format requires some additional clauses to be added as per the norms of the bank. This additional clause along with the BG format provided in the Tender could be used if the bank norms demands so. Notwithstanding anything contained herein above i) Our liability under this bank guarantee shall not exceed Rs /- (Rupees only). ii) This bank guarantee shall be valid upto ----------- iii) We are liable to pay the guaranteed amount or any part thereof under this bank guarantee only if you serve upon us a written claim or demand (and which should be received by us), on or before the Dt. before 14.30 hours (Indian Standard Time) whereafter it ceases to be in effect in all respects whether or not the original bank guarantee is returned to us.
Annexure-1 Requirements of Earthquake Risk Evaluation Center (EREC) data Center 1. Introduction Earthquake Risk Evaluation Center (EREC), a multidisciplinary center of India Meteorological Department (IMD) is involved in generating knowledge products to help the national endeavor in mitigating the disastrous impacts of earthquakes and undertake/promote the specific tasks related to earthquake risk evaluation of cities vulnerable to earthquakes. The mandate of the centre includes generation of earthquake risk based knowledge products including seismic hazard and risk microzonation of high earthquake prone cities, develop information system and user interface. Presently, the data generated by EREC is being managed by a few small data collection and archival systems of EREC, which have become obsolete. The proposed requirements aims at setting up a state-of-the-art web based data center with the objective of multidisciplinary data management right from raw data to processed data at center, analytical capability, generation of end products and their accessibility to the end users through web page, data exchange and data security etc. 2. Data generation - Seismic hazard studies and Product generation: Study of seismic hazard and risk evaluation requires collection and generation of variety of data related to geology, geomorphology, seismotectonic, geotechnical, geophysical and built information etc to generate base map, geological map, seismotectonic map etc., and product maps such as peak ground acceleratio n, seismic hazard and risk map etc. EREC also aims to develop a state-of-art web based data / information collection and distribution system for earthquake risk hazard. The seismic hazard and risk microzonation study of metro city only, involves data generation of order of 300GB per city. The seismic microzonation of targeted cities will therefore generate about 1.5TB data. This will be followed by related application software(s) and products generation related to EREC, their availability on web, data sharing, data security and data management. 3. Requirement: The proposed database is multidisciplinary in nature with suitable hardware and software packages, with integrated design to meet the following objectives/capabilities:
3.1 Development analytical/computing capability integrating application software. 3.2 Development of distribution information system for ready collection of multithematic data, archival, storage, retrieval and also develop advance level interface with other related database. 3.3 Database is to be designed to incorporate tailored reporting and ad hoc query capabilities, which can support organizational decision making on the basis of product generated by application software and provide near real time view of risk information on occurrence of an earthquake. 3.4 Develop adequate printing facility of maps of different size 4. Salient features of Database: 4.1 The database should be designed based on industry standard H/w with high volume network storage, high speed network interconnect, high speed OS and automatic data management tools. 4.2 A key aspect of the data structure is the inclusion of Metadata according to NSDI (National Spatial Data Infrastructure) standards. Metadata about each feature class for each project study of various themes (e.g. seismicity/ seismic microzonation/ seismic hazard etc.) is stored in the RDBMS but is also exposed to standard geographic search engine. In addition to feature class metadata, each feature (record) also has key metadata elements that provide links back to the original sources. Access to the data can be geographic searches (e.g. what is here ), metadata bases (e.g. what data was prepared by EREC in 2005 ) or both. 4.3 Data and various products are subsequently retrieved by users through internet / VPN. Retrieval of data is transmitted using the TCP/IP protocol. 4.4 The project envisages the processed multi-disciplinary data to be expressed in geo referenced GIS presentation to be utilized for preparation of hazard maps, risk map, other type of related geo-scientific & geotechnical maps and decision support system. It is suggested that the core of this system will be a large Enterprise RDBMS type database containing all generated/ processed data content from various field studies with appropriate application server like Enterprise RDBMSAS to run various GIS middleware and applications and capable database manager.
4.5 To provide a user friendly web accessible interface for users desiring to access data and various end produc ts like hazard map, risk map, earthquake event information, etc. from the data center system, the solution provider has to create the set of server applications and portions that run in a client web-browser. 4.6 Near-real time observational data such as intensities, etc. reported by agencies/ individuals for preparation of shake maps etc. as a tool for disaster management under GIS based decision Support System. 4.7 The EREC database is to be integrated with database of GPS/Seismic data centre for making use of the products generated by each other 5. Hardware requirement: State-of-art industry standard hardware including servers, terminals, storage system (about 2 TB for ten year period), scanners(a4 and A3 size), product display panel, LAN, printers(a4 and A3 size), plotter (A0 size) etc. as envisaged in schematic block diagram and other miscellaneous accessories required to meet actual requirements. 6.0 Software requirement: Basic OS for servers, terminals and other peripheral. Database: Enterprise Edition RDBMS Database with license, media, documentation and warranty. Application Server: AS compatible to RDBMS Enterprise Edition with license, media, documentation and warranty. GIS software: GIS (Latest version) Enterprise Edition with license, media, documentation and warranty. Application/Analysis software (licensed) required are as follows: o SHAKE, LIQUEPRO, FLAC-3D, LIQUEFAC, HAZUS99, ERDAS, ROCKWARE, SEISAN, DATAMINE, Zint Compatible with Digital Modelling capability, other software pertaining to hazard & Risk evaluation Software
Web Portal software: A web server with license, media, documentation and warranty. Firewall software: Industry standard dedicated Firewall 7. Requirements for Software Development (Deliverables) 7.1 Integration of databases: Project requirement would be integration of different databases, so that all information related to earthquake parameters in real time may be used for assessing input for actual hazard. Software provisions must be there for accessing/injecting satellite imagery, maps/charts and other processed information from other databases from similar organizations in near real time. 7.2 Earthquake Hazard Product generation: These are GIS based map products related to seismic hazard and risk which will be produced using various application softwares. 7.3 GIS and integration with map data base : Suitable S/W is required to be designed and developed for linking spatial data base engine with RDBMS to generate user defined dynamic and layered map products such as current as well as old earthquake information, catalogs, Intensity map, Site response map, Geological map, hazard map, etc. **************************** -x-
Table-1 Expected Deliverables S. No. Milestone Deliverable Timeline 1 Preliminary Design Review (PDR) 2 Critical design Review(CDR) 3 Installation and functional test Preliminary Design Review document: System Architecture Development Plan Integration Plan Operation maintenance Plan Tender Document for procurement hardware, system software & Application software by INCOIS/IMD Prototype development and demonstration. Critical Design Review document: Integration and testing of hardware & software. Deliverable software components as listed in Section 7.0 in Annexure 1 Installation of final software in the computing system. Functional test T + 1 Month T+6 Months T+9 months 4 Reliability Test and Acceptance ATP( Acceptance Test Plan) document and test T+12 months
Table-2 S.No Description of item Amount (Rs./USD) 1 System Architecture Hardware, system software and application software specification (Tender document) 2 Application Software development as envisaged. 3 Installation, System Integration & commissioning 4 Maintenance Charges during 1-year warranty period 5 Annual Maintenance Charges(comprehensive) during 2 nd year period 6 Annual Maintenance Charges(comprehensive) during 3 rd year period 7 On-site training to engineers at IMD 8 Statutory Levies and Taxes 9 Total Cost 10 Any other items, including license fee etc;