OFFICE OF HEAD, CLIMATE RESEARCH AND …imdpune.gov.in/Links/tenders/TD.CDSP.NDC.pdfTender Document...

Tender Document for the Climate Data Services Portal at IMD Pune

OFFICE OF HEAD, CLIMATE RESEARCH AND SERVICES

(CR&S)

INDIA METEOROLOGICAL DEPARTMENT

SHIVAJINAGAR, PUNE 411005

Tender Document for

Design, Development and Implementation of

Climate Data Services Portal at IMD, Pune


LIST OF ACRONYMS USED IN THIS DOCUMENT

Abbreviations Full forms

AMSS Automatic Message Switching System

ARG Automatic Raingauge station

AWS Automatic Weather Station

BoM Bills of Materials

BUFR Binary Unified Form

CliSys/CDMS Climate Data Management System

CDSP Climate Data Service Portal

CR&S Climate Research and Services

DRS Disaster Recovery Site

EMD Earnest Money Deposit

FTP File Transfer Protocol

GFCS Global Framework of Climate Services

GIS Geographical Information System

GUI Graphical User Information

ICT Information and Communication Tools

IITM Indian Institute of Tropical Meteorology

IMD India Meteorological Department

INCOIS Indian National Centre for Ocean Information System

LAN Limited Area Network

METAR Meteorological Aviation Report

MMR Monthly Meteorological Register

MO Meteorological Office

MoES Ministry of Earth Sciences

MoU Memorandum of Understanding

NCDC National Climate Data Centre

NDC National Data Centre

NKN National Knowledge Network

NMHS National Meteorological and Hydrological Services

PB Pilot Balloon data

PBG Performance Bank Guarantee

QA/QC Quality Assurance / Quality Control Process

RDBMS Relational Data Base Management System

RH Relative Humidity data

RMC Regional Meteorological Centre

RS Radio Sonde data

RTH Regional Telecommunication Hub

RW Radio Wind data

SI System Integrator

SLA Service Level Agreement

SYNOP Synoptic hours observational Data

TEMP Temp Message (Coded form)

VPN Virtual Private Network

WBS Work Break-down Structure

WMO World Meteorological Organisation

Wx Weather Information


LIST OF FIGURES

LIST OF TABLES

Table No. Description

1. Details of Query / point for Clarifications

2. Details of reception and Acquisition of Observational Data

3. Details of reception and Acquisition of AWS data

4. Timings for SLA

5. SLA for availability management services

6. SLA for service level maintenance

7. SLA for solution availability

8. Payment schedule with milestones

9. Reception details of various types of data

10. Reception details of Automatic stations

11. Hardware details of CliSys

12. Details of climate Data products

Fig. No. Description

1. Overall Functional Diagram of CDSP

2. Activities of Task Management

3. Schematic Flow of Data types, sources of communication

4. Flow Chart of Quality process on data

5. Flow Chart of functional system

6. Present metadata schema available at NDC

7. Flow chart of Data supply management


TENDER DOCUMENT FOR DESIGN AND DEVELOPMENT OF CLIMATE DATA PORTAL

TABLE OF CONTENTS

SECTION DESCRIPTION PAGE NO.

SECTION 1 INTRODUCTION 6

SECTION 2 INSTRUCTIONS TO BIDDERS 10

SECTION 3 EVALUATION OF BIDS 19

SECTION 4 SCOPE OF WORK AND TECHNICAL SPECIFICATIONS

21

SECTION 5. SERVICE LEVEL AGREEMENT – INDICATIVE 39

ANNEXURES

ANNEXURE TITLE / CONTENTS PAGE NO.

ANNEXURE A PROFORMA – BANK GUARANTEE 54

ANNEXURE B PROFORMA – PRICE BID 57

ANNEXURE C PAYMENT SCHEDULE 59

ANNEXURE D DELIVERABLES AND TIMELINES 62

ANNEXURE E PROPOSAL DOCUMENT SUBMISSION FORM 63

ANNEXURE F EXISITING DATA ACQUISITION / RECEPTION 64

ANNEXURE G DATA PRODUCTS GENERATION TOOLS 87

ANNEXURE H ON-LINE DATA SUPPLY AND COMMERCIALISATION 96

ANNEXURE I PRE CONTRACT INTEGRITY PACT 104

ANNEXURE J SPECIFICATIONS OF HARDWARE /SOFTWARE / PERIPHERALS

110


ANNEXURE K PROPOSED DETAILS OF HARDWARE 111

SECTION 1

INTRODUCTION BACKGROUND 1. INDIA METEORORLOGICAL DEPARTMENT:

1.1 India Meteorological Department (IMD) established in 1875 has a large network of observatories for monitoring the weather and National Meteorological and Hydrological Services (NMHS). IMD functions under Ministry of Earth Sciences (MoES) since formation of the ministry. IMD is responsible for International cooperation in the field of Meteorology through various World Meteorological Organisation (WMO) programmes. As National Meteorological Organisation (NMO), IMD has been serving the nation for more than 135 years with forecasting and weather services. IMD serves and supports the global data exchange as part of its activities. Today meteorology in India is poised at the threshold of an exciting future.

NATIONAL DATA CENTRE:

1.2 In the office of Climate Research and Services (CR&S), National Data Centre (NDC), Pune, is a data division of India Meteorological Department (IMD) acts as the custodian of all data being collected from various parts of India. The mandate of this centre is to preserve quality controlled data and supply for Weather Prediction, Aviation, Agriculture, Environmental studies, Oceanography and Shipping and Researchers of various Institutions and Universities. There are about 15 types of data / met. Parameters like Surface, rainfall, autographic, upper-air data, radiation data, air-pollution data, etc.. Under the modernisation programme, the observational networks were expanded and upgraded with installations of Automatic Weather Stations (AWS), Automatic rain-gauge stations (ARG), and other automatic surface and upper-air atmospheric observations which have further increased the inflow of volumes and variety of data for permanent archival. The data size of about 10 MB or more is expected to flow every day or depending on the observational frequency. These data would help in providing the instantaneous weather details and ultimately improve climatological information for a better understanding the Climate change and its predictions by the operational and research community for applying in their climatological diagnostic and simulation studies for achieving results with more accuracy. As modernisation programmes carried out in IMD during 2001-10, augmentations were undertaken in the observational networks / services were upgraded and towards strengthening both infrastructure and communication. Also, availability of fast and advanced technology/ tools for integration and communication necessitate the up gradations and latest state-of-art systems for all data management and services. Recently, an emphasis is on the WMO’s Global Frameworks of Climate Services (GFCS)


due to variety of high-resolution real-time data and volumes of data. This throw challenges for multi-pronged Climate services on sectoral applications (Disaster, Water, Health, etc.,) which are targeted globally as well as regional levels. Being the active contributing member of WMO in all its endeavors, IMD has its responsibility to fulfill the commitments and implement these at national levels too.

Therefore, the office of CR & S has a prestigious plan project proposal entitled “Development of Climate Data Services Portal” to accomplish the goals of the Climate services at all levels keeping WMO’s vision and improve on Climate Data Management (CDM) Systems for implementation at IMD.

CLIMATE DATA SERVCIES PORTAL:

1.3 The Climate Data Services Portal sought to be developed, is aimed at improving the existing data management activities of CR & S with upgrades both in terms of technology and infrastructure. This will include fast data acquisition from different media i.e. Internet, Messaging System like e-mails, storage like CD, External Hard Disk etc. and archival, on-line payment and data supply and web-based Climatological Information Service(s) Systems at par with standards of International Meteorological Centres (as mentioned in Annexure G). The proposed tasks are to facilitate real-time monitoring and reporting with automatic messages, QA/QC procedures before the archival, retrieval, net-centric operations such as web-based tools for data analytics and visualization, products such as map, graph, images and e-commercialisation on all types of meteorological data. Further, it is required to integrate with other existing databases available at IMD (i.e. Satellite, Seismic, and Radar) as well as data those of institutions under MoES.

INVITATION FOR BIDS

1.4 IMD invites proposals for consideration of awarding the work of Design and Development and Implementation of Climate Data Portal. 1.5. The present tender is for inviting formal proposals from the proficient companies / firms

who can undertake the works as turn-key project fulfilling all the requirements in the establishment and integration of the following components which are explained subsequently in the Tender document: (a) Seamless dedicated portal for providing all climate data products and services; (b) Upgrade all facilities and develop fully-automated ICT towards (i) fast data acquisition, (ii) real-time monitoring / reporting & QA/QC procedures, (iii) archival and retrieval, (iv) net-centric / based utilities for data analytics and products with GIS , Table, text enabled formats;

(c) On-line data supply, commercialization and sharing;

(d) providing Climate services using links to other databases of IMD and those institutions under MoES, viz., IITM, NCPOR, INCOIS, NCMRWF, etc.,.


1.6. A data acquisition along with processing, archival and data monitoring system needs to be integrated into the proposed portal. This requires automatic ingestion and first level quality control management in addition to its monitoring, messaging / mailing response and acceptance. This should include a dual communication facility and a secondary level quality control, quality assured procedures, etc., and permanent archival of climate data. Various tools are to be developed for deriving different standard data products, value additions, analytics and climate data including visualization. The different activities of acquisition, monitoring, process, archival, retrieval and value-added production, etc., are explained in the Annexure F,G and H of this document.

1.7. For the E-commercialization and online data supply management system the components

include designing, development, payment process, Testing, Implement and maintenance (hardware and software, licenses and third-party services) installation, Configuration, Commissioning and training of web based software systems.

1.8 The climatological services through the data portal sought to be developed must have the

scope of data accessibility and utility for the remote users by providing all types of retrieval, application and analytical tools with GIS featured interfaces for the users’ knowledge. This must serve as a main gateway to a remote user to have options and accessibility to various databases of IMD such as Satellite, seismic, forecast and model outputs and climate products generated by IMD as well as other institutes of MoES, with suitable privileges and different authorization as decided by the institutes.

1.9 Thus, the works to be taken up by the selected firm that would comprise the following (for

details please refer to the requirements indicated in the Annexure F, G & H to this Request For Proposal).

• Design and Development of state-of-art Climate Data Portal with user-friendly features at par with international standards

• Management of historical, current and future data and migration of data.

• Monitoring and reporting on data acquisition, receipts along with time-latency

• Host, Manage and secure the digital assets like data, metadata, transaction data, etc.

• Quality control with standard WMO procedures

• Data archives with suitable policy

• Streamline net-centric operations

• Design and develop tools for data products, value additions, analytics and climate data

• Provide authorized and secured access (such as https, ftps and etc). (Internet, Extranet & IMD LAN)

• Provide mechanisms for on-line payment as per IMD data supply & policy and rates. Create a data supply management system (it is by default)

• Implement solution for high availability (multiple instances) hardware and software


disaster recovery and proper backup solution Backups

• The portal should be secured and 24x7 data availability

• Design, develop, test, install, configure, commission and maintain all web-based tools, utilities and interfaces

• Supply necessary cabling system for integration and overall solution as per international IT standards.

• Supply, Install, configure and commissioning of all necessary and adequate accessories for respective equipment and/or products supplied for the development of portal.

• Provide integration of the hardware, software, network components, peripherals, etc required for the design and development of application and its deployment (includes existing infrastructure and additional hardware procured, if any)

• Prepare and provide user manuals, test plans, and appropriate testing cases including integration testing and its reports

• Prepare and provide User Acceptance Testing (UAT)

• Post-warranty support for THREE years after completion of the warranty of THREE years (AMC or extended warranty)

• Undertake to complete all aspects of the work and make available all the deliverables as detailed in this Proposal to the best satisfaction of IMD / Technical Expert Committee.

INVITATION FOR PROPOSAL 1.10. IMD invites proposal for the provision of the above-mentioned services.

Bidder shall upload their proposal (complete in all respects and complying with all the requirements), ONLINE through CPP Portal at https://eprocure.gov.in/eprocure/app. The proposal submitted as manual bids shall not be accepted.

TWO BIDS SYSTEM 1.11. There is a TWO BIDS system evaluation in the process, namely a) Technical Bid and b)

Price Bid and hence to be followed on the procedures mentioned in Section 2 under instructions to the bidders.

LAST DATE FOR SUBMISSION 1.12 The proposal complete in all respects should be submitted as per date and time indicated

in the NIT

OPENING OF TENDERS


1.13 The purchaser will open the online tender at the specified date and time and at the

specified place as indicated in the NIT. In case the specified date of tender opening falls

on / is subsequently declared a holiday or closed day for the purchaser, the tenders will

be opened at the appointed time and place on the next working day. Authorized

representatives of the Bidders, who have submitted tenders on time may attend the

tender opening, provided they bring with them letters of authority from the corresponding

Bidders. Two Bid system will be as follows. The Technical Bids are to be opened in the

first instance, at the prescribed time and date. These Tenders shall be scrutinized and

evaluated by the competent committee/ authority with reference to parameters prescribed

in the TE document. Thereafter, in the second stage, the Price Bids of technically

qualified Bidders only shall be opened online for further scrutiny and evaluation on a date

notified after evaluation of the techno commercial tender.

1.14 IMD reserves the right to vary the specifications provided in this proposal or to award the whole of the required services to one bidder, as it seems fit, or not to make any award for any or for all of the services, following this invitation to this tender.

1.15 IMD reserves the right to reject any or all of the bids received in response to this invitation

to this document without assigning any reasons whatsoever.

END OF SECTION 1 SECTION 2

ELIGIBILITY CRITERIA AND GENERAL INSTRUCTIONS TO BIDDERS

General Eligibility Criteria

2.1 The bidders should have Certification of SEI-CMMi level 3 or 5 and above (copy of the valid certificate to be enclosed).

2.2. The bidder should have experience in design and development of Climate / Weather data Scientific Data Center along with GIS based database application, having minimum three projects each of 4 Crores or above in last five years, undertaken in a reputed organization (India / overseas). Copy of documentary proof in the form of Purchase Order/Work Order / Agreement along with completion certificate with duration to be enclosed.

2.3 In case of multiple products, bidder shall submit a valid memorandum of Association or Understanding (MoU)/ back-to back support Manufacturers Authorisation Form (MAF) with from all OEMs for their supporting products among the members signed by the authorized signatories of the companies dated prior to the submission of the bid. However, the Purchase Order/work order shall be placed with the prime bidder, who shall be sole responsible to execute the entire project and support services during warranty/post warranty/AMC period. Details on the Projects undertaken such as Awarded year, Nature of Project, modules developed, Client’s name & Full address, Cost, Status of the project, completion with performance certificate) must be attached as proof


2.4 Bidder should have support office at Pune or Hyderabad and Delhi / NCR. A list of such offices should be attached with the technical bid.

2.5 The bidder should have an average turnover of at least Rs. 10 Cr. (Rupees Ten crores)

during last three years (copy of audited profit & loss accounts and balance sheet of three years i.e.; 2016-17, 2017-18 & 2018-19, to be enclosed). Bidder should have earned profit in the last two years out of 3 years period. The information should be provided duly verified by audit.

2.6 Bidder should submit mandatory visit certificate from Head, CR&S.

Pre – Bid Meeting: 2.7 If the bidder finds any queries or clarifications on any points mentioned in this TENDER

DOCUMENT or in any Corrigenda as may be issued by IMD prior to the last date for submission of the proposal, or if the bidder has any doubts as to the meaning or intent of any part thereof, he shall immediately so inform IMD, who may send written instructions or explanations to the bidder. The format for these queries / clarifications is given under:

Table 1. Details of Query / Point for Clarification

S.No. Tender document Reference (Section, page #, etc.)

Content Query / Point for clarification

1

2

2.8 If an explanatory notice is so issued by IMD, it will be distributed to all the Bidders. 2.9 Pre-Bid minutes shall be uploaded on e-Procurement portal at

https://eprocure.gov.in/eprocure/app. Prospective bidders are advised to see IMD website

at http://imdpune.gov.in/Links/tenders/tender_main.html and at CPP portal at

https://eprocure.gov.in/eprocure/app on regular basis for any change in NIT schedule,

amendment / corrigendum in Tender Document (T.E.) including technical requirement

and pre-bid minutes etc.

2.10 Bidders in their own interest and shall make own arrangements to attend the pre-bid meeting.

2.11 Bidders shall note that IMD will not entertain any correspondence or queries on the status

of the offers received against this tender document Invitation. 2.12 Canvassing in any form by any bidder or by any other agency acting on behalf of the

bidder after submission of the bid may disqualify the said bidder. IMD’s decision in this regard shall be final and binding on the bidder.

2.13 In formulating their proposal, bidders shall have full regard to the contents of the General

Conditions of Agreement given in Section 5, since all bids will be deemed to have been made after taking into account all the provisions thereof.

https://eprocure.gov.in/eprocure/app

http://imdpune.gov.in/Links/tenders/tender_main.html



2.14 The successful bidder will have to execute an Agreement as set out in Section 5 within 21 days from the date of issue of a fax / letter of intent by IMD. The Agreement as finally accepted will include solution to this tender document and amendments if any, and the bidder’s offer as finally accepted by IMD.

2.15 Performance Security Deposit / Performance Bank Guarantee (PBG) shall be submitted

as per Annexure - A 2.16 Within twenty one (21) days from date of the issue of notification of award by the

purchaser, the supplier, shall furnish performance security to the purchaser for an amount equal to ten percent (10%) of the total value of the contract excluding AMC if any. Performance Security has to be submitted irrespective of its registration in GeM. Performance security is not relaxed to any supplier.

2.17 It shall be in the form of Bank Guarantee drawn/issued issued by a commercial bank doing

government business in the prescribed form in favour of the purchaser. In the event of any amendment issued to the contract, the supplier shall, within twenty-one (21) days of issue of the amendment, furnish the corresponding amendment to the Performance Security (as necessary), rendering the same valid in all respects in terms of the contract, as amended. Bank Guarantee should be issued from any of Nationalized banks in India.

2.18 IMD will release the Performance Security without any interest to the supplier on

completion of the supplier’s all contractual obligations including the warranty obligations & after receipt of bank guarantee for AMC security (if applicable) . The supplier shall submit pre receipt for obtaining their security.

2.19 Such guarantee shall be

(i) Unconditional as per format in Annexure A (ii) Valid for 3 years from the date of completion of warranty period, as per

and shall be so declared by IMD, and (iii) Will be for the due performance of the Agreement by the bidder / Service Provider, claimable by IMD in the event of breach by the bidder / Service Provider of any of its obligations under the Agreement.

2.20 EARNEST MONEY DEPOSIT (EMD)

2.20.1 Bidders shall submit along with their document, an EMD for a sum of Rs. 50,00,000 /- (Rupees Fifty Lakhs Only) . The earnest money is required to protect the purchaser against the risk of the tenderers unwarranted conduct.

2.20.2. The EMD shall be furnished in the form of Bank Guarantee (BG) (as per Annexure - III) from any commercial bank doing government business. in the favour of “HEAD, CLIMATE RESEARCH AND SERVICES, payable at PUNE”. The Bank Guarantee issued from the foreign banks must be authenticated by STATE BANK OF INDIA or any other Nationalized Bank of India.

2.20.3 The clause “encashment / release of BG requires clearance certificate from Purchaser i.e HEAD, CLIMATE RESEARCH AND SERVICES must be mentioned in issued BG by Bank.


2.20.4. The earnest money shall be valid for period of sixty (60) days beyond the validity period of the tender.

2.20.5. Refund of EMD: Unsuccessful tenderers’ earnest money will be returned to them without any interest, after expiry of the tender validity period. Successful tenderers’ earnest money will be returned without any interest, after receipt of performance security from the tenderer. The tenderers have to submit pre-receipt for obtaining their EMD in the FORM GAR 43D in duplicate with original signatures. One form should be affixed with revenue stamp.

2.20.6. Forfeit of EMD: Earnest money of a Tenderer will be forfeited, if the tenderer withdraws or amends its tender or impairs or derogates from the tender in any respect within the period of validity of its tender or if it comes to notice that the information/documents furnished in its tender is incorrect, false, misleading or forged without prejudice to other rights of the purchaser. The successful tenderer’s earnest money will be forfeited without prejudice to other rights of Purchaser if supplier fails to furnish the required performance security within the specified period.

2.20.7. Firm shall have to extend the validity of EMD if extension of tender validity is agreed on the request of purchaser in exceptional cases. 2.20.8. Scanned copy of Earnest Money Deposit (EMD) in the form of BG. Original EMD in physical form shall be submitted to Purchase Section of IMD, Pune on or before closing of bids submission date. 2.20.9. IMD shall, arrange to release the EMD in respect of the unsuccessful bidders as soon as possible after a decision is taken on the successful bidder.

2.20.10. IMD will not be liable for any obligation until such a time IMD has communicated to the successful bidder of its decision to entrust the work.

INSTRUCTIONS FOR FILLING PROPOSAL DOCUMENT - GENERAL

2.21 The Proposal papers shall be filled-in, complete in all respects and shall be submitted together with requisite information and Appendices, if any. It shall be complete and free from ambiguity, change or interlineations.

2.22 Request for Proposal prices must be indicated only in the format of price bid given in

Annexure B. 2.23 Any additional information that the bidder wishes to submit must be attached as an

addendum. 2.24. All pages should be numbered and the document should have a proper index. All pages

properly bound in a file / booklet form. There should be no loose page.


2.25. The Bidder’s Proposal document and any annotations or accompanying the documentation shall be in English Language only. Supporting documents in any other language shall carry an English translation authenticated by an independent authority.

2.26. The bidder shall sign on each page of the Proposal Document submitted by him. 2.27 Bidders should indicate at the time of quoting against this Request for Proposal their full

postal and e-mail address and fax number(s). 2.28 The Proposal shall be kept valid for acceptance for a minimum period of 180 days from

the date of opening of the bid. If any bidder desires to offer a longer validity period, it should specifically be mentioned in the Proposal document. Offers with validity of acceptance for less than 180 days from the date of opening of the bid will not be considered.

2.29 The bidder shall sign the Proposal document with the exact name and address of the firm,

which is bidding for the works stated in this Request for Proposal. 2.30 The Proposal document shall be signed by a duly authorized officer of the firm which is

bidding for the works stated in this Request for Proposal, and in the case of a Corporation, seal, or otherwise appropriately executed under seal

PRICE QUOTE 2.31 Bidders shall set their price/quotations in firm and fixed figures and without qualifications.

Each figure stated should also be repeated in words and in the event of discrepancy between the amount stated in figures and in words, the rates quoted in words shall be deemed to be the correct amount.

2.32. Proposals containing qualifying expressions such as “subject to availability”, “subject to

minimum acceptance”, etc. or any conditional clauses invoked by the bidder shall be liable to disqualification and rejection. If the space in the Proposal form or in the appendices thereto is insufficient, additional pages shall be separately added. These pages shall be consecutively numbered and shall also be signed by the bidder.

2.33. Bidders shall be bound to keep the prices quoted in their Price Bids firm without any

escalation for any reasons whatsoever until they complete the work assigned by IMD against this tender document.

2.34 The prices shall be given in Indian Rupees only. 2.35 The quoted prices shall include all costs along with taxes applicable, with option including

but not restricted to the proposed works have relevance of paras detailed under Section 4.

2.36 Charges towards the operational maintenance of the system along with the components

sought beyond the comprehensive warranty of 3 (THREE) years followed by 3 (THREE)


years of comprehensive maintenance should be quoted separately as operational and maintenance charges per year/quarter (as per the format details given at Annexure B).

2.37. Payment to the Service provider shall be made in accordance with the Terms of Payment

given in Annexure C, subject to the full satisfaction of IMD 2.38 IMD will not pay any additional charges other than those provided for, in the Agreement. INSTRUCTIONS FOR SUBMITTING THE PROPOSAL DOCUMENT: 2.39 The Proposal document is non-transferable.

2.40 The Technical specifications for the Proposal work are provided in Section 4.

2.41 The Technical and financial details for the proposed work shall be submitted by the bidder separately viz., TECHNICAL BID and PRICE BID and as follows:

TECHNICAL BID AND ENCLOSURES:

2.42 Bidder shall upload their proposal ONLINE through CPP Portal at https://eprocure.gov.in/eprocure/app as manual bids shall not be accepted. The tender shall not contain any erasure or overwriting, except as necessary to correct any error made by the Bidder and, if there is any such correction; the same shall have signature of the person(s) signing the tender.

2.42.1 An EMD for a sum of Rs. 50,00,000 (Rupees Fifty Lakhs Only) in the form of a BG from any nationalised Bank in India or Foreign Bank operating in India favouring Head, Climate Research and Services and payable at Pune.

2.42.2 Details of key personnel who will be involved in providing the services as per the IMD’s Proposal on behalf of the firm/ organization and organizational track- record for this type of work;

2.42.3 Company Profile with all details as required in support of evidences as proof for the Eligibility Criteria at 2.1.and 2.2 above

2.42.4 Complete and comprehensive details of the solution proposed by the bidder vis-à-vis the scope of services including details of operational processes and procedure involved. All technical information should be supported by brochure/ literature to the extent possible.

2.42.5. Details of the Hardware/ software/peripherals/networking components proposed in the solution to this tender document (a) Hardware / equipments, their make(s), model(s), quantities, their technical specifications /brochures and their Non-ICT requirements, etc., (c) proposed architecture, over and above the existing infrastructure. Proposed (d) software(s), licence or upgrade / update details, etc., should be furnished

2.42.6. A proposed work program chart Work Break-down Structure (WBS) with time lines

2.42.7. The details of any component(s) of the proposed work which would be sub-contracted by the firm to a third party. (E.g. Penetration test by CERTIN empanelled firms for vulnerability assessment or security of the contents, Contract Agreement etc.)

2.42.8. The legal constitution of the bidders including documentary proof of the signatory’s authority to bid on behalf of the firm/ organization who will be involved in



providing the services stated in Section 1 of this tender document for, on behalf of the firm/ organization.

2.42.9. Proposal Submission form as at Annexure E, duly filled in and signed.

2.42.10 proposed Solution architecture (hardware architecture as well functional architecture), flow charts and Control data flow. 2.42.11 Pre Contract Integrity Pact as per Annexure I.

2.42.12 One set of Un-priced (Blank) Bill of materials containing make, model, year of manufacturing etc. for all items (as per Annexure B) .

2.42.13. Item-wise compliance statement for each para / sub-para of the tender document. 2.42.14 Bidder shall upload their proposal ONLINE through CPP Portal at https://eprocure.gov.in/eprocure/app as manual bids shall not be accepted. The tender shall not contain any erasure or overwriting, except as necessary to correct any error made by the Bidder and; the same shall have signature of the person(s) signing the tender.

2.43 PRICE BID AND ENCLOSURES

2.43.1 The bidder will not indicate separate discounts. Discounts, if any, should be merged in the rates against the quoted items. Discounts of any type separately shown will not be taken into account for Price Bid evaluation purposes.

2.43.2 The Proposal document MUST be submitted complete in all respects. Incomplete bids or those not conforming to any of the instructions provided in this document would be summarily rejected.

Bidder shall upload following documents on CPP PORTAL


(i) Registration certificate of bidding firm with government body in their country. Credential /

document shall be attached.

(ii) Checklist section (as per Annexure - I) properly filled and signed.

(iii)Scanned copy Earnest Money Deposit (EMD) in the form of BG. Original EMD in

physical form shall be submitted to Purchase Section of IMD, Pune on or before closing

of bids submission date.

(iv) Documentary evidence for fulfilment of Eligibility /Qualification criteria(s).

(v) Copy of agreement between bidding firm in India and their foreign principal indicating

precise relationship between them and their mutual interest in this tender must be

furnished along with their technical bid.




(vi) Tender terms & Conditions Acceptance Form (Annexure – II) duly signed. (i.e. Bidder has

agreed to all the terms & condition of tender enquiry document).

vii) Technical Bid List of deliverables (un-priced/without price) with make & model etc. This

should be exactly same as attached in price bid.

2.44 TENTATIVE COMMENCEMENT OF WORKS

The successful bidder must ensure that the proposed work should commence within 60 days of signing the contract. A written undertaking to this effect will be required before signing the Agreement.

2.45 TENTATIVE COMPLETION DATE

a) Bidders must undertake to complete all aspects of the work as detailed at “DELIVERABLES AND TIMELINES” in this tender document to the best satisfaction of IMD within 15 months from the date of signing the contract.

b) Penalty clause/Liquidated damages clause (LD) for delayed stores & Services:

* The supplier shall deliver the goods and perform the services (like installation & commissioning etc) under the contract within the time schedule specified by the purchaser in the “List of requirements/ technical specifications” section and as incorporated in the contract. The delivery date, unless delivery is divided, on which all the items/stores/materials/services etc as per supply/purchase order are delivered shall be taken into account for penalty/LD purpose.

• The purchaser shall, without prejudice to other rights and remedies available to the purchaser under the contract, deduct as penalty/liquidate damage from the contract price a sum equivalent to 0.5% (half percent) per week of delay or part thereof on delayed supply of goods and/or delayed services subject to a maximum of 10% of the contract price of delayed items. LD shall not be imposed under force majeure conditions. Once the maximum is reached purchaser may also consider followings:

a)Forfeiture of its performance security and b)Termination of the contract for default.

Note: The supplier shall not be held responsible for delay in delivery of stores and their

installation for the following reasons:

(i) Delay in providing Entry permits/Road Permits (if required) to the supplier by the consignee. (ii) Delay in providing proper site(s) by the consignee to the supplier. Site is not ready in all respect (i.e. all civil & electrical at site completed) for installation of stores. (iii) Delay in providing No Objection Certificate (NOC) required from any

other government agency/agencies.


(iv) Communication facility required for project to be provided to the supplier by the consignee if it is not the responsibility of supplier.

(v) Any other reason for which supplier is not responsible.

c) (i) Penalty/Liquidated damages shall be calculated on the purchase / contract price including the element of sales tax, excise duty, service tax etc mentioned in the price bids

(ii) Custom duty shall not be taken for the purpose of Penalty/LD calculations. d) The supplier shall not be held responsible for any delay in custom clearance by

purchaser, handing over proper site by consignee and any other delay in part of consignee/purchaser, if responsible. These periods shall not be counted in LD. The supplier shall not dispatch the goods after expiry of the delivery period. The supplier is required to apply to the purchaser for extension of delivery period and obtain the same before despatch. In case the supplier dispatches the goods without obtaining an extension, it would be doing so at its own risk and no claim for payment for such supply and/or any other expense related to such supply shall be against the purchaser. The supplier shall inform to the purchaser directly in writing about these delays on part of IMD.

2.46 AGENTS

Bids made by only authorised Agents / Representatives of principal bidder will be considered.

2.47 Indian firm (Supplier /Integrator /Distributors/ Distributors /Stockiest etc.) offering imported

stores in response to this tender enquiry shall quote in INR only. No foreign exchange

shall be released by IMD, Pune and also no payment shall be made to their foreign

principal. If the bidder is OEM of foreign origin then they should bid through their Indian

Representative only in INR.

2.48 MODIFICATIONS TO BIDS

The bidder shall make no modifications to the bids after the closing date unless specifically requested for, by IMD. In case certain clarifications are sought by IMD after opening of Proposals, then the reply of the bidder should be restricted to the clarifications sought. Any bidder who modifies his bid (including a modification which has the effect of altering the value of his offer) after the closing date without specific reference by IMD shall make himself liable to be debarred from this Proposal and future tenders of IMD without notice and without further reference to the bidder. In such an event, the EMD against the current Proposal shall be forfeited.

2.49 EXCEPTIONS AND DEVIATIONS

IMD expects the Proposal as submitted by Bidder should meet the requirements, provisions, specifications, drawings, etc. as stipulated in the tender document without any


deviations and exceptions. In case of such deviations, acceptance or rejection, decision of IMD will be final

2.50 DATE OF SUBMISSION / UPLOADING OF TENDER

Bidder shall upload their proposal ONLINE through CPP Portal at https://eprocure.gov.in/eprocure/app as manual bids shall not be accepted. The tender shall not contain any erasure or overwriting, except as necessary to correct any error made by the Bidder and, if there is any such correction; the same shall have signature of the person(s) signing the tender. Bids or modifications to the bids received after closing date and time shall not be considered, and no negotiations in the prices shall be considered. IMD reserves the right to extend the date of submission /closing of the Proposal at the discretion of the Head, Climate Research and Services, IMD, without assigning reasons but with a prior intimation (written) to all those bidders who have been provided this tender document.

2.51 Once the technical evaluation is completed, the Price Bids of only those bidders who are found technically acceptable will be opened in the presence of Authorized Representatives of such bidder(s), if any.

2.52 UNSOLICITED POST-REQUEST FOR PROPOSAL REDUCTION

The bidder shall note that any unsolicited post-Proposal reduction by them would disqualify them from participating in this as well as future Proposals and forfeiture of the EMD.

2.53 SIGNING OF THE AGREEMENT

Telefax / e-mail or letter will communicate acceptance of the proposal by IMD. In case where acceptance is communicated by Telefax/ e-mail, a letter in confirmation of acceptance of the Proposal will be forwarded to the bidder as soon as possible, but instructions contained in the telefax/ e-mail should be acted upon immediately.

2.54 The successful bidder shall be required to execute a formal Agreement in accordance with the requirement of IMD within 21 days from the date of issue of fax/letter of intent by the IMD or within such extended time as may be permitted by IMD. For this purpose the successful bidder may depute his authorized representative along with power of Attorney.

2.55 NON-RESPONSIVE PROPOSALS:

Individual Bid scrutiny will be held and incomplete details as given below will be treated as non-responsive. If proposals (i) are not submitted in as specified in the tender document

(ii) received without Letter of Authorisation (Power of attorney)

(iii) are found with suppression of details

(iv) with incomplete information, subjective, conditional offers and partial offers submitted

(v) submitted without the documents requested in the Annexure K

(vi) non-compliance of any clauses stipulated in tender document

(vii) Lesser validity period

(viii) Non-acceptance of LD clause mentioned in Sec. no. 2.45



2.56 All responsive bids will be considered for further process for bid evaluation as explained in section 3.

END OF SECTION 2

SECTION 3

EVALUATION OF BIDS 3.1 TECHNICAL

TECHNICAL BID EVALUATION CRITERIA

3.1.1 The bidders should have Certification of SEI-CMMi level 3/ 5 and above ( copy of the valid certificate to be enclosed).

3.1.2 In case of multiple products, bidder shall submit a valid memorandum of

Association or Understanding (MoU)/ back-to back support Manufacturers Authorisation

Form (MAF) with from all OEMs for their supporting products among the members

signed by the authorized signatories of the companies dated prior to the submission of

the bid. However, the Purchase Order/work order shall be placed with the prime bidder,

who shall be sole responsible to execute the entire project and support services during

warranty/post warranty/AMC period. Details on the Projects undertaken such as

Awarded year, Nature of Project, modules developed, Client’s name & Full address,

Cost, Status of the project, completion with performance certificate) must be attached as

proof. However, the Purchase Order shall be placed with the prime bidder, who shall be

sole responsible to execute the entire project and support services during warranty/post

warranty/AMC period.

3.1.4 Details on the Projects undertaken such as Awarded year, Nature of Project,

modules developed, Client’s name & Full address, Cost, Status of the project,

completion with performance certificate) must be attached as proof

3.1.5 Bidder should have full-fledged support offices/very centre network at Pune,

Delhi and Hyderabad. A list of such offices should be attached with the technical bid.

3.1.6 The bidder should have an average turnover of at least Rs 10 Cr (Rs. Ten

Crores ) during last three years (copy of audited profit & loss accounts and balance

sheet of three years i.e.; 2016-17, 2017-18 & 2018-19, to be enclosed). ). Bidder should

have earned profit in the last two years out of 3 years period. The information should be

provided duly verified by audit.

3.1.7 Technical suitability of proposed solution in terms of software as well as

robustness of the project management plan shall be considered during the technical bid

evaluation.

3.1.8 Once the technical evaluation is completed, the Price Bids corresponding to only

those bidders who are found technically acceptable will be opened for Price Bid


evaluation in presence of Authorized Representatives of such bidder(s), if any, on a date

and at a venue to be intimated by IMD to the short-listed bidders.

3.2 FINANCIAL

VITAL COMMERCIAL CRITERIA FOR ACCEPTANCE OF BIDS

The following vital commercial conditions should be strictly complied with, failing which the bid will not be considered: 3.2.1 Offers must be kept valid for acceptance initially up to 180 days from the closing date of Proposal. Validity of offers for acceptance less than 180 days will not be considered. IMD shall make efforts to release the EMD of all those unsuccessful bidders at the earliest.

3.2.2 An EMD must accompany the Technical bid. Offers received without EMD will be rejected.

3.2.3 The following standard clauses of IMD as incorporated in this Proposal are to be complied with in toto, failing which the bid will be rejected: (i) Submission of Bank Guarantee for Performance for execution of agreement as well as for satisfactory performance during Agreement period (ii) Jurisdiction clause (iii) Force Majeure clause (iv) Total liability of Personal Income Tax on jobs executed in India (v) Warranty and Guarantee clause

3.2.4 The prices shall be given in Indian Rupees only.

3.3. COST EVALUATION

3.3.1 The evaluation of the cost will be done based on the total cost. The total cost will be calculated from the information provided by the bidders in their Price for all the components as set out in Annexure B. The L1 bid conforming to the lowest cost would then be considered for award of work.

3.3.2 No comparison of the individual components constituting a price bid shall be made with the corresponding component quoted by another firm.

3.3.3 Total price for comparative evaluation shall include the charges and applicable taxes, if any, towards all including but not limited to the scope of services indicated under section 4.

3.3.4 The above method is used for cost evaluation only. The actual payment will be based on the Agreement and as per actual implementation.

3.4 ADDITIONAL CRITERIA FOR BID EVALUATION

The following criteria shall also be adopted for evaluation of the bids:


a) Total cost can reasonably unambiguously / clearly be determined from the bidder’s response b) All necessary supporting documentation required for evaluation of the financial bid has been provided and is found satisfactory 3.4.1 Any other matter, which arises at the time of evaluation, shall be decided by IMD 3.4.2 The decision of IMD shall be final and binding.

END OF SECTION 3

SECTION 4

SCOPE OF WORK AND TECHNICAL SPECIFICATIONS

4.1 SCOPE OF SERVICES AND DELIVERABLES IMD invites b ids for consideration of awarding the work of Design, development and

implementation of Climate Data Services Portal at IMD, Pune.

The detailed scope of work to be taken up by the selected firm, would comprise, but not be

limited to, the following:

• Design, development and implementation of user-friendly portal, UI and required tools for the activities of data acquisition / reception, monitoring, quality processing, archival, data retrieval, data analytics & visualization and commercialisation;

• High level customisation for various tasks and scheduling in assigning data streams towards data acquisition/reception, data cataloguing, data processing, data validation, data storage, data backup & recovery, data analytics & visualization, data sets and data products generation.

• generate auto-message, alerts, sending / receiving the data reception status to ensure acquisition within specified / desired time – latency else to report to the originating Met observatory station or met centre or regional centre responsible and concerned

• Prepare GIS base maps – Survey of India approved with political boundary up to block / taluka level along with all geographical features required for meeting all the functionalities explained

• Auto-flagging the erroneous elements / parameters need to be flagged and sent back to the respective regional centre (real-time data) or responsible section for correction based on manuscript (for past /delayed data) (based on levels 1 & 2 control checks)

• Alert messages and suitable actions at various levels, in case of non-receipts / pending data

• Store Corrected data in the database both in terms of metadata and also physical data after successful checks (i.e., 2 level controls)

• Prepare Data catalogues, meta-data documentation, on data archived, cost-value tagged, etc.

• Scheduled and optional back-up procedures


• Migrate and upload all existing data in various digital media and formats into the new system

• Implementation of Disaster Recovery with complete data and all functionalities at DR site (Delhi)

• Authorisation of user categories, setting-up levels of authorisation, privileges, Data distribution

• Provide Robust search engine(s) for fast retrieval of data -- based on selections of locations, metadata details, types of data, parameters, period, catalogues.

• Integrate retrieval and applications tools to enable value additions to data

• Facilitate various modules towards catering the Commercialisation / Online Payment for Data supply and its management System

• The system should be highly secured and available on 24 x 7.

• Ensure that the current systems are not affected during the migration

• Ensure that all level of security (OS, DB, application and utilities, etc.) to be taken up at the time of implementation on the system.

• Provision of web-enabled user guide, manuals and help menus

• Suitable on-site training including hands-on experience on all the modules & functionalities of the system

• The proposed system should be compatible to BoD (bring own devices) without any customization.

• The proposed system should have admin panel i.e. Content Management System (CMS) for managing the entire system inclusive its database services and etc.

• The proposed system should have designed & implemented such way that to address all security issues.

• Standard software – Licensed (preferred) with technical supported open source

• All GIS Products / Applications / Tools / Utilities developed should be conforming and compliant with Open GIS Consortium protocols (OGC)

• Industry Standard Web Tools and highly secured Data Base( ORACLE, DB2 and HANA), WEBSPHERE, JBOSS, WEBLOGIC

• Web-security audit should be done prior to hosting the system Note : For more details on development of various applications, Sections 4A, 4B, 4C, 4D, 4E and Annexures F, G & H may be referred.


Fig. 1 Overall Functional diagram of CDSP

4.2 FUNCTIONAL ENTITIES & REQUIREMENTS:


Fig. 2. Activities of Task management

SECTION 4.A. DATA ACQUISITION & STORAGE Data Types and source points (numbers indicated inside the brackets) and their details are provided in this section.

(i) MANUAL OBSERVATIONS:

Table 2 Details of reception and Acquisition of Observational Data

S.N.

Data Type & Source Points

Authority /

Location

Reception

Form

Mode of reception

Priority

Return Path

Frequency

Latency Period

(*) (Validati

on by concern

ed Centre Less than)

Reception type

1 Surface Data (550)

Synoptic Hours MOs SYNOPs

AMSS 1 e-mail/SMS

3 hourly 3 Hrs Text file/BUFR

MOs/MCs

MMR Hand held Data Logger

FTP/e-mail/SMS

2 e-mail/SMS

3 Hrs Text file

MOs/MCs

web form interface

3 e-mail/SMS/

week Text file

Day’s Summary MOs SYNOP AMSS 1 e- Once (03 3 Hrs Text


s mail/SMS

UTC) file/BUFR

MOs/MCs

MMR Hand held Data Logger

FTP/e-mail/SMS

2 e-mail/SMS

3 Hrs Text file

MOs/MCs

web form interface

3 e-mail/SMS

week Text file

2 Upperair (RS/RW/PB) (36+65)

MOs TEMP AMSS 1 FTP/e-mail/SMS

6 hourly 6 Hrs Text file/BUFR

MOs Register Form

NDC web interface

3 e-mail /NDC web interface

Text file

3 Rainfall MOs in the form of Days summary

As part of SYNOP(AMSS)/ NDC web interface

1/2/3 FTP/e-mail /NDC web interface

Once 3 Hrs Text file/BUFR

DRF (6000) State rain-gauges Through HS

NDC web interface

2/3 NDC web interface

Monthly/Yearly

week Text file/Excel/E-mail/dBase

DRMS (3000) MCs HS FTP/ MK –rain

2 / 3 FTP/e-mail

Once One day

Text / MK-rain

4 Autographic Rainfall(540), Pressure(160) , temp.(180), R.Hum(180), Wind(60), Sunshine(70)

MOs / MCs

NDC format

NDC web interface

3 e-mail /NDC web interface

Once 6 Hrs Text

5 Ozone (5) MOs /MCs

NDC format

NDC web interface

3 FTP/e-mail

Schedule (offline)

One day

Text

6 Radiation (45) Text / BUFR

7 Marine Gloabl Ship Message

AMSS 1 Nil As per the schedule

Text / BUFR

GCC IMMT format

3 e-mail Once in three offline

IMMT format

8 Agromet Data Evp(89)ET(47)Moist(46)CWS (230)Dew100)

Text/ e-mails/SMSs/BUFR

9 Archived data Text Predefined formats

Predefined formats

3 Offline Text

10 METARs Current Weather (75)

METARs

AMSS /FTP 1 AMSS/FTP/e-mail/SMS

Every half an hour

Text / BUFR

11 Misc. Data Radiometer-sonde Highspeed wind recorders, data loggers (10)

1 Offline Tabular / text files/

12 Environement data (10) format Offline Tabular / text

Note: (*) Latency indicates the time limit period within which the particular observational data needs to be archived after completion of

QA/QC process

ii) AUTOMATIC WEATHER STATIONS:


Table 3. Details of Reception and Acquisition of AWS data

S.N. Data Type Reception from Reception Form Mode of reception

Priority Return Path Frequency* Reception type

1 AWS (2200)*

SYNOPS AWS Mobil Synop FTP/AMSS 1 Every hour Text / BUFR

ARG Mobil Synop FTP/AMSS 1 Every hour Text / BUFR

AWS – Agro Text FTP/AMSS 1 Every Hour Text / BUFR

2 Radiation (45)

Automatic Stations

Text FTP/AMSS 1 Every hour Text / BUFR

MOs/MCs MMR Data logger 2 FTP/e-mail/SMS

Text

3 Marine Bouys and Ships

Ship Synops (Mobil Synop)

AMSS 1 Every hour Text / BUFR

4 Aviation (75) Airports METARs and SPECIs AMSS 1 e-mail/SMS Every half an hour

Text/BUFR

Note: * All AWS data needs to be archived on real-time basis


Fig 3. Schematic Flow of Data types, Sources and Communication

4.A.1. Infrastructure currently available at IMD, Pune

Internet & Networking Components: I M D , P u n e has been provided with 100 Mbps Internet connectivity through National Knowledge Network(NKN) in addition to 30 Mbps leased line connectivity from BSNL, Pune.

Firewall: Checkpoints 5400 series

4.A.2. SIZING AND FUTURE PROJECTIONS:

Anticipated Projections on Data Source Points:

As of now climate data and products including images (jpeg & gif) to the tune of 20 TB are available in the archives in the digital formats. The details of various Data Source Points of AWS, ARG are provided in table 3, which is likely to increase (max. 5000) by 5 years. Some of the Offline data source points are likely to be upgraded to real-time mode. The augmentation and expansion network progress would cause increased inflow of real-time data for permanent archival. The same needs to be facilitated with adequate capacity of networks. 4. A.3. OBSERVATIONAL DATA RECEPTION / INGESTION: Design facilities and develop web-based formats of various types of data for ingestion from different modes and formats. (i) . Modes

o e- mails o SMS o FTP o AMSS (Automatic Message Switching System) / VPN ( Directly from the Mirror-RTH

available at Pune) o Web-based dataset template

(ii). Formats

o ASCII Text o Excel, dBase o Coded Messages (SYNOP, SYNOP MOBIL, TEMP, METAR, BUFR etc) o Data loggers (AWS/ARG, Upper-air, radiation in text/CSV ) o Off-line loading ( ASCII text, pdf, text - tabular form, excel, all image including raster files,

xml. o Existing data from other databases (raster images, text, pdf, grib, etc.,)

(iii). Data monitoring

o Generate automatic alert / confirmation messages within pre-defined latency period from source station (refer Table 2)

o for non-receipt of data from a particular station o for non-receipt of parameters expected


o for non-receipt of validated data

o Visual display of the data reception / non-reception in GIS map form (for a particular hour of observation)

o Data type wise (Surface, Upper-air,.) o Parameter wise

o Visual display of the data reception / non-reception in tabular form (for a particular time

of observation)

o Data type wise (surface, upper-air,….) o Station wise (name, location index,…) o parameter wise

o Report generation

o Listing format o Generating alert messages o Statistics details

o Log generation at each stage of data acquisition / reception

(iv) on-line data Quality Control(QC)

o After Quality Control, the doubtful data to be referred back to station of origin and or other nodal offices

o Receive the validated data and archive the Quality controlled data in the intermediate database.

4.A.4. PROCESSES INVOLVED :

Fig. 4. Flow chart of quality process on data


4.A.5. METADATA (in GIS Compatible format)

Features to be made available:

• Reference date used by the database (GMT, time zone, others);

• History of the values ascribed to the meteorological parameter and any associated flags;

• Instrument used to record the observation, together with more fine detail on its own maintenance program, tolerances, internal parameters, etc;

• Owner/authority/user of the observatory;

• Full details of the station, location (state/district/met. Sub div.), and its history;

• Details of observations in effect at the time and its history;

• The inventory of the elements stored in the database, their units, their boundaries;

• Topographical and ground-cover details of the site, information on surrounding trees, images buildings, etc, and how these have changed with time.

• Updation by respective stations through a login through various networks

• WMO Information System (WIS) compliant. (please refer http://www.wmo.int)

• For more information, refer to “Guidelines on Climate Metadata and Homogenization” (WMO 2003b) in the World Climate Data and Monitoring Programme series of publications.

• Provision may be made for accommodating any new updates as per WMO guidelines

• Complied with WGIS84 projection and OGC, Metadata ISO19115. (ftp://ftp.ncddc.noaa.gov/pub/Metadata/Online_ISO_Training/Intro_to_ISO/workbooks/MD_Metadata.pdf

4.A.6. QUALITY CONTROL (QC) PROCESS:

Level 1: QC (fields/elements/parameters/record)

o Syntax checks for all coded data o Duplicate checks o Gross Limit Outliers(against a declared data set of normally expected values specific to

reporting station) o Internal Consistencies between parameters (details will be provided at the pre-bid stage).

Level 2 : QC

a. Temporal Consistency – Check for the variation in the parameter value with the time (hourly/daily)

o Deviation from climatological means (climatological tables will be provided) o Deviation from previous value

b. Spatial consistency – Check for changes spatially

o Display maps to visualize the spatial distribution o Apply Interpolation techniques to see the variation (methods to be specified)

c. Quality control flags

http://www.wmo.int/

ftp://ftp.ncddc.noaa.gov/pub/Metadata/Online_ISO_Training/Intro_to_ISO/workbooks/MD_Metadata.pdf

ftp://ftp.ncddc.noaa.gov/pub/Metadata/Online_ISO_Training/Intro_to_ISO/workbooks/MD_Metadata.pdf


o assign to each parameter failing the checks listed o flags will be utilized for filtering of data used in the displays (maps and tables)and also

used for sending messages of alerts and validation o Pending flag logs will be created and displayed at monitoring and observatory ends for

reminders and reporting to different levels. o Flag removal will be a mix of automation and manual override o Proper linking would be required with archival into Database after quality control

procedures as well as towards dynamic updations and/or preparations of catalogues. o Additionally, refer WMO 305 Chapter 6 for QC procedure for surface and upper-air data

and similar QC procedures for other types’ data.

4.A.7. DATA STORAGE:

• Proposed to have Data Storage Policy based on hierarchical mechanism.

• Unified Storage is required depending on the utility of data modules.

• The proposed Data Storage should have capability and scalability features for the requirements atleast 10 years.

The maximum 10 GB data flow including real-time and non-real time/offline ingestion per day is expected. 4.A.8. FEATURES REQUIRED DATA BASE:

• Robust and industry Standard leading Relational Data Base Management System with

latest stable version / release

• SQL based front end tools/search engines;

• Facility of OLAP (On-Line Analytical Processing )

• Software Utilities / administration integration;

• Suitable transporting / importing tools from old dBase to new;

• Provision to integrate data mining tools (Data Miner, pattern recognition, etc.,)

• Provision for storing intermediate datasets and other files

• Dynamic catalogues generation whenever data is updated

4.A.9. Data Users expected

(I) Internal Users within IMD / MoES

a) Data acquisition/Reception, Pre-Processing & manipulation: 100

b) Visualization, downloads, Analytics : 1500

(II) External Users

a) Registered for viewing, downloads, analytics (limited) : 1500

b) Guest User (without registration) view / display : 3000

(III) Concurrent users: : 300

(IV) Projection User: There could be increase of 150-200 users per year


4.A.10. Data Loading / Migration : Maximum size of 10 GB data load expected to be migrated into the proposed system. 4.A.11. Applications: For processing events of applications, there could be maximum of 20GB data transaction per event. 4.A.12. LATENCY: For manual observations, the anticipated maximum latency is as indicated in Table 4.A.1 from the stage of data acquisition (of particular time of observation ) up to archival after all QA/QC process and 4.A.13. BACK-UP POLICY:

o Scheduled and optional backups

o Incremental – every day

o Full back-up once in a week

o System / Error Logs should be enabled for generation of reports

4.A.14. DISASTER RECOVERY SYSTEM (DRS) AT IMD, NEW DELHI:

o Mirroring all activities including s/w and hardware of Control site o Full functionalities (end to end) of Control site.

o Ensure minimum downtime to switch over.

o Mock-drill of DR system every quarterly (Business Continuity of the proposed System).

END OF SECTION 4 A

SECTION 4.B.: DATA EXTRACTION / DATA PRODUCTS

4.B.1. TYPES OF DATA EXTRACTION / DATA PRODUCTS

a. Criteria for extraction of data and products:-

▪ Location (s) selection using

(i) Stations from a pre-defined Area (Block/State/District/sub-division boundaries with base maps - Survey of India approved)

(ii) Station-list supported by drop-down / pop-ups

(iii) Grid-wise (latitude/longitude) if pre-defined area

▪ Should be provided to choose type of data from various datasets (like surface, rainfall, upper-air, etc)

▪ List of parameters

▪ With given duration / period (such as from and to year/month/ date/hours)

b. Extraction of Special data products such as extremes and averages.


c. Graph/Plots, GIS based mapping and etc., using Analytical tools (interactive) like, statistical analytics and visualization for the given datasets. The output formats could be in txt, excel, jpg, png, netCDF, grib, pdf, maps (with zoom in/ out) etc.,

d. For external users similar kind modules wherein the data products could be generated after going through the appropriate checks

e. Admin Panel of the proposed system should have data retrieval functions as below:-

▪ Log reports of each user

▪ Data retrieved, generated data products, etc.,

▪ authorizations and privileges for various user’s levels

▪ Policy on Restrictions on data size, types, tools, etc.,

▪ Retrievals / Extractions by Data processing on delayed (non real-time) data

f. Scheduled Automatic generations of products & pre-formatted/customized reporting (please refer paras under Climate Products in Annexure G)

▪ Standard Table form Climate Normal (for various parameters)

▪ Pentad normal (s)

▪ Hourly to daily

▪ Daily to weekly

▪ Daily to monthly

▪ Monthly /Annual Summary (Map and Table form)

▪ Any other desired products :

o Stations specific, Frequency Occurrences events, Wind rose, Area specific state/district level values, maps, charts, etc.,

g. New Registration/Login Module: Basic user details: Date, Name and address details, user category, registration etc., with add/modify/delete, update facility & suitable authentication procedure

h. Data Request Module: Allows to select type of data, frequency, region/location, period, output file format, address and mode for dispatch, requirement of analytical tools for value additions, etc., get confirmation of selection completion

i. For commercial users cost estimation would be done based on charges / rates applicable for various types of datasets, data products then direct to payment gateway (such as Standard and reliable /GePG – Government e-Payment Gateway, Mode of payment options (net-banking / credit / debit cards) processes.

j. Payment related applications logs / system logs should be captured in the proposed system to track any failure events and etc.

k. Report generation (daily, weekly, monthly, any given period) for payment, users, revenue statement along with taxes details.

4.B.2. APPLICATION /ANALYTICAL TOOLS:

▪ Statistical Analytics Tools such as descriptive statistics method - Mean, Mode, Median, Variances, Kurtosis, skewness, etc.


▪ Statistical Analysis : Temporal, spectral analysis, testing techniques., Functional / Frequency curve plots, Sigma and Box plots, Scatter diagram, Regression and Correlations, Interpolations, Multi-dimensional and Multivariate analysis, Factor analysis, Cluster analysis, canonical mapping, data normalization, data homogenization, missing value techniques etc..

▪ Probability of Maximum values like PMP, Assured Max. Rainfall.

▪ data mining techniques and tools

▪ Return period evaluation analysis

▪ GIS base maps (from Survey of India) & layers for India with different types of networks / locations eg., Blocks / Talukas / districts / states / Met. Sub divisions level)

▪ Gridding the data using interpolation (specific type desired/default)

▪ Provision to Integrate with any other models as tools / library

4.B.3. HARDWARE AND SOFTWARE REQUIREMENTS:

(i) NETWORKS:

• Enhancement of existing firewall with High Availability(HA)

• Enhancement of existing IMD LAN (Pune) such as L3 PoE switches, Wireless Access Point (WAP) with OFC / CAT-6 and VLAN Server

• SMS Client Servers

• GPRS interfaces

(ii) OS/ STORAGE / BACKUP:

• Linux OS at both levels of server and

• Linux and Windows applications on clients

• SAS/ SATA storage with Backup on DLT tape (backup) ( 3 tiered)

• Storage server 100% up time

• Storage controller, networked

• Data server – hot standby

• Monitoring terminals (reception, processing and health, etc.,)

• Buffer server at data ingest end hosting Q/C programs and monitoring programs

END OF SECTION 4 B

SECTION 4.C. : ADDITIONAL FEATURES : CLIMATE SERVICES

4.C.1. WEB PORTAL AND LINKS:

(a) Web portal with suitable links to be developed for the following activities:

• User-Login;

• Authentication/Security/password/user-details

• accessibility for data;

• Analytical /application tools, standard products/displays, etc.,

• links to various standard products along with


➢ cataloguing/search-in facility

➢ Viewing / Displaying standard Climate products

(b) Mobile applications on different platforms (eg. Android, IOS, Windows, etc.,) for limited climate products such as

➢ Catalogues and data search

➢ View/display of standard climate products

➢ System Monitoring remotely (Critical SMS alerts)

4.C.2. MoES institutions would have provision to upload their climate datasets and products with valid login credentials into proposed system.

END OF SECTION 4 C SECTION 4 D NON – ICT REQUIREMENTS

4.D.1. TRAINING:

• Imparting on-site Training on system administration, data migrations, applications,

module, DB administration, support and monitoring of system, trouble-shooting of

system (hw/sw), DRC activities, hardware, software and their operations and

maintenance, OS updations and patches, renewal/subscriptions of licenses of all

supplied components to IMD. The vendor is required to submit the detailed syllabus/

topics/ contents to be covered along with duration for each topic well in advance. The

contents, period and number of trainees, will be decided by IMD. Four (4 Nos.) sets of

training materials, hard bound form of manuals/user-guides as well as soft copies on

DVDs covering all aspects of system activities, troubleshoots, etc.,(of system

administration, maintenance and operation and all supplied utilities) should be

supplied by the vendor

4.D.2. SITE PREPARATION: (Vendors/ bidders should make mandatory visit IMD site for the understanding of the site preparation prior to tender submission)

• Successful vendor awarded, must offer consultancy, monitoring and preparation of

the site to be “fit” for the implementation of the entire system/project.

• Vendor has to prepare the site ready with necessary requirements Civil (floor/module),

Electrical (A/C, generator, UPS), cooling, etc., to suit to the specifications of HW

equipments servers / System. Requirement details of UPS, Power maintenance

systems should meet as per the hardware specifications suiting for minimal or NO

fault conditions and optimal energy consumptions.

• The SI must ensure maintenance of the power and energy monitoring for enabling

smooth functioning of the data centre.


• Vendor along with their price bid has to quote their price for shifting and re-

installation at the new site and make the entire system in operational conditions

with full functionalities. This quoted price will form the part for cost evaluation

process.

• However, it is optional on the part of IMD, to use or not the services of shifting and

re-installation to the new site, by the vendor who is awarded the project.

4.D.3. ANTICIPATED POWER LOAD REQUIREMENTS*:

a. SERVERS:

Servers 10 Nos. @ 700 W (internal) : 7000 W

Servers 10 Nos. @ 700 W (external) : 7000 W

b. STORAGE:

SAN ( 1 No.) + TAPE (1 No.) Backup (Internal) : 2000 W

SAN (1 No.) + NAS (1 No.) + TAPE (1 No.) Backup : 3000 W

c. PCs and Peripherals:

Client Machines (15 Nos.) @ 450 W : 6750 W

Network Printers (3 Nos.) @ 450 W : 1350 W

Scanners (2 Nos.) @ 450 W : 900 W

Additional (5 Nos.) @ 500 W : 2500 W

TOTAL (a + b + c) = 14000+5000+10600=29600 W : 30 KW

For buffer backup : 20 KW

UPS requirement : 50 KVA

Backup requirement : 8 Hrs

* Note: These requirements are indicated as tentative. However, vendors are free and may have consultations and ensure before finalising as per the hardware and meet the specs to be supplied

END OF SECTION 4 D

SECTION 4.E GENERAL REQUIREMENTS

• Supply, Install, configure, commission and maintain all necessary and adequate

accessories for respective equipment and/or products supplied for establishment of a

state-of-the-art Climate Data Services Portal and facilities with latest proven technology.

• The system to be developed should be a completely new, self-sufficient and independent

with all upgraded facilities enabled having hot standby mode of configuration for


redundant mode of system operation. Any existing system can be interfaced with the new

system depending upon the requirement.

• Provide integration of the hardware, software, network components, peripherals, etc.,

required for the application deployment (includes existing infrastructure and additional

hardware procured)

• all web – based tools, utilities and interfaces (customization required for operational

convenience, functional flexibility and user friendly appearance must be carried out with

the complete interaction with user)

• Once the functionalities, storage and data base integrated and established with all

features, all the historical data available in the existing storage need to be migrated after

proper testing and to the satisfaction of IMD.

• Carry out user acceptance tests as listed in Section 2

• Comprehensive warranty support is required for 3 (THREE) years from the date of

completion of Go-Alive after the acceptance test as decided by IMD.

• A comprehensive AMC / Post-warranty support for 3 (THREE) years after

completion of the warranty

• Technical support for 24 x7 for all kinds of s/w and h/w (both ICT and non-ICT) of the

system during entire period of warranty / AMC.

• All licensed tools/ utilities, the software (O/S, Application etc.) components

supplied should have life-time validity period

• All applications/utilities to be developed with fast retrieval and large applications and links

to various application servers/tools

• The hardware should be with adequate memory and high speed connectors to facilitate

the features mentioned

• The deployment of suitable positions such as software developers, system/application

administrators, Manager/supervisors, personnel Non-ICT maintenance for the operation

and maintenance would be required

• Adequate number of consumables (Tapes, HDD, toner / cartridges, etc.,) towards

maintenance, repairs, storage and up gradations, etc., during warranty and AMC

period must be assessed and provided by the vendor

4.F. WARRANTY:


4.F.1. The warranty has to be provided by the vendor for FULL 3 (THREE) years after the

Go-Live phase as may be declared by IMD

4.F.2. The warranty mentioned in the Tender shall mean all services in terms of

solution to be covered in the following areas /applications, without additional cost

• To undertake 24 X 7 supportive maintenance of hardware (ICT and non-ICT

system equipments and network) and software components supplied, installed,

integrated to ensure the functionalities and system with no-fault, no-failure

conditions;

• To carry out design & development, implement and integrate any or specific

patch works or modifications or fine-tunings, as mentioned in the Tender, to cope

with performance issue arising over the period

• Bidder will be responsible for vendor management and renewal of license

subscriptions and its related issues.

4.G. COMPREHENSIVE ANNUAL MAINTENANCE CONTRACT (AMC)

4.G.1. Vendor needs to provide the comprehensive post-warranty AMC for FULL 3

(THREE) years after the warranty period of 3 years.

4.G.2 The technical 24 X 7 support and maintenance for business continuity such as

system administration & database and applications support and management. Ensure

that no security breach in Application / OS/ DB level, network related issues/ services

along with the non-ICT components

4.G.3.Technical support in extension of licenses and security client certifications, etc., as

may be required in the AMC period

4.H ACCEPTANCE TESTING AND CERTIFICATION ( to be modified)

4.H.1. Acceptance Tests

The selected bidder in presence of the authorized officials of IMD will conduct acceptance

test at the site. The test will involve installation and commissioning and successful

operation of the hardware, software, communication equipment etc. No additional

charges shall be payable by IMD for carrying out these acceptance tests.

4.H.2 An appropriate team of members constituted by IMD shall make its assessment

and certify for this purpose. The primary goal of Acceptance Testing and Certification is

to ensure that the Project (including all the project components as discussed in the scope


of work) meets requirements, standards, specifications and performance, by ensuring that

the following are associated with clear, quantifiable metrics for accountability:

− Functional requirements – by testing formats / forms as defined under Technical

specifications (Section 4A to 4.E.)

− Infrastructure (Hardware and Network) Compliance Review – by checking with the

Tender specifications and requirements (section 4)

− Availability of the project Services in the defined locations – checks as per scope of Tender

− Performance based on parameters that include (i) events; (ii) time - latency; (iii)

Maximum uploads / downloads depending on each and every component of utilities

and modules provided by the vendor under data acquisition, retrievals, product

generations, e-commercialisation, climate service, etc.,

− Security/firewall – testing for transactions without any spam, virus towards data loss

− Manageability – testing functionalities based on critical and complex events

− SLA Reporting System - compatibilities with reference to Section 5 of Tender

− Project Documentation - at control-site and DRC design, development, configuration,

software development, training, operational and administration manuals requirements

− Data Quality Review – to be decided based on functional and performance categories

mentioned above

- Non – ICT compliances – as per the requirements in Tender

4.H.3. As part of Acceptance testing, the appointed team shall also review all aspects of

project development and implementation covering software, hardware and networking

including the processes relating to the design of solution architecture, design of systems

and sub-systems, coding, testing, business process description, documentation, version

control, change management, security, service oriented architecture, performance in

relation to defined requirements, interoperability, scalability, availability and compliance

with all the technical and functional requirements of the TENDER DOCUMENT and the

agreement.

4.H.4 Go – Live of the System:

The “Go-Live” shall mean the successful implementation of all the deliverables including

hardware and software towards the functionalities of all processes relating to the activities

as envisaged in the TENDER DOCUMENT

4.4. HARDWARE SPECIFICATIONS:


The details of tentative requirements of hardware components and their specifications are

given in Annexure K. The general flow pattern of the entire functional system is presented

as Fig.5.

Fig.5 Flow Chart of functional system

4.5. FOR MORE DETAILS : IMPORTANT 4.5.1. Details of the existing practices on data reception, archival and generation of data products, etc.,: may also be referred at Annexures – F, G & H to this tender document.

END OF SECTION 4

SECTION 5

SERVICE LEVEL AGREEMENT – INDICATIVE*

(*Will be finalised before the project awarded)


The actual SLA shall be finalised with the successful bidder and shall cover, among

others, points mentioned below and in tender document on a non judicial stamp paper of

Rs. 100/-

1.0 Statement of Purposes

1.1 This Agreement is entered into by IMD and the VENDOR - the Service Provider to specify:-

a) The Services to be provided to IMD by the VENDOR – the Service Provider

b) The amounts to be paid by IMD for the services rendered.

c) Confidentiality and security of the Data to be handled

2.0 Definition

2.1 In this Agreement, unless the context otherwise requires:

"Data” means the any climate related data collected and to be archived at the National Climate

Data Centre

"Commencement Date", means the date on which this Agreement comes into effect

pursuant to clause 3.1 of the Agreement;

"Force Majeure" means but not be limited to any act, circumstances or event beyond the control

of either party, including, without limitation, earthquakes, fires, tropical cyclones, other acts of

God, riots, strikes, lock outs, insurrection resulting from rebellions, civil disturbances or orders

from governmental authority. For the avoidance of doubt, equipment breakdown shall not be

considered a Force Majeure event;

"Expiry Date" means the last date i.e.-----------------------, for the performance of any outstanding

obligation under this Agreement,

“Service Provider” means the successful bidder – the vendor with whom this Agreement is

entered into;

2.2 Interpretation-

In this Agreement, unless the context requires otherwise:

(a) Words denoting the singular number shall include the plural and vice versa;

(b) Words denoting any gender shall include all genders;

(c) Where a word or phrase is defined, other parts of speech and grammatical forms of that word

or phrase shall have corresponding meanings;

(d) Words denoting natural persons shall include corporations and vice versa;

(e) References to clauses, sub - clauses, paragraphs, sub -paragraphs and Annexures are to

clauses, sub- clauses, paragraphs, sub -paragraphs and Annexures to this Agreement;

(f) Headings are for convenience only and shall not affect interpretation;


(g) References to any party to this Agreement shall include the parties' successors and

permitted assigns;

(h) References to "IMD, Pune" shall include the Head, Office of Climate Research and

Services, Pune or any duly appointed officer from IMD

(i) References to "VENDOR" or “Service Provider” shall include any servant, agent, employee,

invitee, VENDOR or sub-contractor of the VENDOR.

3.0 Terms of Agreement

3.1 This Agreement shall come into effect on the date of signature and subject to the termination

provisions pursuant to clause 8 or to a variation of date pursuant to clause 14, of this

Agreement, shall end on the Expiry Date.

3.2 The following documents form the Agreement between the parties and shall be read together

as one document. However, in case of any conflict, this Agreement shall prevail.

a. This Agreement

b. The tender document provided by IMD

c. The documents submitted by the bidder substantially in the form set out in the tender

document supplied by IMD, the Appendices and any amendments thereto;

d. The letter of intent, if any, issued by IMD;

e. The letter of award;

f. The Performance Guarantee.

4.0 Obligations of the VENDOR

4.1 The VENDOR agrees to provide to IMD the services specified in this Agreement. 4.2 In performing the services and fulfilling all its obligations under this Agreement the Vendor:

4.2.1 Warrants that the services to be provided will be to the satisfaction and approval of IMD;

and

4.2.2 Assumes full responsibility for providing all personnel, documentation, and

equipment to undertake the Services, and warrants that all equipment, systems, personnel and

facilities to be used will be suitable for their intended use under this Agreement, and to ensure

the quality of results required thereunder; and

4.2.3 assumes full responsibility for the care of all equipment, systems and documentation used

to provide the services from the commencement date until conclusion of the project as declared

so by IMD; and


4.2.4 shall in providing the services under this Agreement, act in a skilful, diligent,Workman like,

careful and proper manner and in accordance with any applicable laws and regulations and with

standards and practices normally exercised by a professional in the performance of the same or

similar services; and

4.2.5 Takes responsibility to ensure that all the personnel are aware of their duties, and that all

possess the skills necessary for the proper execution of the tasks they are to perform; and

4.2.6 Undertakes to provide (including but not limited to) all materials, labour, consumables, and

data media, such as tapes, paper and CD's, as may be required for the performance of the

Services; and

4.2.7 If the VENDOR breaches any of its obligations under this clause, the

VENDOR shall remedy, at its own cost, any defect, which includes any failure to meet the

required standard(s), to the IMD's satisfaction and within such time as may be specified by IMD.

5.0 Obligations of IMD

5.1 IMD agrees to pay to the VENDOR the total agreed price in the manner provided in this

Agreement on complete satisfaction of the performance by the Service Provider of its obligations

under this Agreement.

6.0 Loss of or damage to the data

6.1 The Vendor shall take utmost care that the data is not lost during the development process.

7.0 Use and ownership of information

7.1 The parties recognise that under this Agreement they may each receive trade secrets and

confidential or proprietary information of the other party, including but not limited to information

on the nature of data collected and archived at IMD. All such information would constitute

"Confidential Information".

Each party:

7.1.1 acknowledges the strict confidentiality and proprietary nature of all Confidential Information

and that no right, entitlement or interest in either party's Confidential Information is extended or

conveyed to the other party except for the strict purposes of each party performing its obligations

under this Agreement;

7.1.2 Shall not at any time (other than for the proper performance of its obligations under this

Agreement) disclose, divulge, communicate, publish or make available in any way to any person

or entity any of the Confidential Information. Nor shall either party at any time for that party's own

benefit or the benefit of any other person directly or indirectly take advantage of, use or in any

way exploit the Confidential Information;


7.1.3 shall take all reasonable steps to preserve the confidentiality of the Confidential Information

and each party shall indemnify the other party from all losses, damages and expenses it may

incur or sustain as a result of any unauthorised use or disclosure of one party's Confidential

Information by the other party;

7.1.4 shall upon request by the other party, and upon termination of this Agreement, immediately

deliver to the other party all material relating to that other party's Confidential Information

(including all copies of such material);

7.1.5 acknowledges that the obligations of confidentiality imposed upon each party shall continue

(unless the Confidential Information reaches the public domain other than through the receiving

party's own fault) notwithstanding that this Agreement may in all other respects have terminated.

7.1.6 All intellectual property rights relating to those products or services created under

this Agreement shall be the sole property of IMD.

8.0 Termination

8.1 The Parties may agree to vary the length of the programme on acceptable terms by notice in

writing between them.

8.2 This Agreement shall automatically be terminated on expiry of its term or any extension

thereof.

8.3 IMD may terminate this Agreement:

- in the event of Force Majeure existing for a period longer than one month (30 days); and

- If IMD considers that the performance of the Service Provider is unsatisfactory and/or not up

to the expected standard. In such circumstances, IMD shall notify the Vendor and specify

in detail the causes of dissatisfaction and shall reserve the right to terminate the Agreement by

giving ten (10) days’ notice provided the Vendor fails to rectify at the cost of the VENDOR

the defects within that period.

8.4 Notwithstanding anything contained herein, IMD may at its sole discretion terminate this

Agreement by giving Thirty (30) days written notice without assigning any reasons, whatsoever.

8.5 In all cases of termination herein set forth, the obligation of IMD to pay the rates and/or

any other charges shall be limited to the period up to the date of termination.

8.6 Termination of this Agreement shall be without prejudice to any rights and remedies accrued

to either Party prior to such termination.

8.9 If either party is in default under this Agreement on account of the failure to perform or

observe any obligation or undertaking to be performed or observed on its part under this

Agreement, the party not in default may, subject to Clause 8.10, by notice in writing to the other


party, terminate this Agreement in whole or in part without prejudice to any right of action or

remedy which has accrued or which may Accrue in favour of either party.

8.10 Where the default is capable of being remedied, a party shall not exercise its rights to

terminate this Agreement unless it has given to the defaulting Party a written notice specifying

the default and requiring it to remedy the default within such time (being not less than five 5)

working days) as may be specified in the notice.

8.11 If either Party goes into liquidation or a receiver or receiver and manager or mortgagee's or

charge’s agent is appointed or, in the case of an individual, becomes bankrupt or enters into

a scheme or arrangement with creditors, the other Party may, by notice in writing, terminate this

Agreement without prejudice to any right of action or remedy which has accrued or which may

accrue in favour of either Party.

8.12 The termination of this Agreement shall not affect those terms which, by their nature, are

intended to survive termination.

9.0 Applicable Law & Jurisdiction

9.1 This Agreement, including all matters connected with this agreement, shall be governed by

the Indian Laws both substantive and procedural, for the time being in force and as amended

from time to time and shall be subject to the exclusive jurisdiction of Indian Courts at DELHI /

PUNE, India.

10.0 Force Majeure

Force Majeure means an event beyond the control of the supplier and not involving the supplier’s

fault or negligence and which is not foreseeable. Such events may include, but are not restricted

to, acts of the purchaser either in its sovereign or contractual capacity, wars or revolutions,

hostility, acts of public enemy, civil commotion, sabotage, fires, floods, explosions, epidemics,

quarantine restrictions, strikes, lockouts, and freight embargoes. If there is delay in performance

or other failures by the supplier to perform its obligation under its contract due to event of a Force

Majeure, the supplier shall not be held responsible for such delays/failures. If a Force Majeure

situation arises, the supplier shall promptly notify the purchaser in writing of such

conditions along with supporting documents and the cause thereof within twenty-one days of

occurrence of such event. Unless otherwise directed by the purchaser in writing, the supplier

shall continue to perform its obligations under the contract as far as reasonably practical, and

shall seek all reasonable alternative means for performance not prevented by the Force Majeure

event. If the performance in whole or in part or any obligation under this contract is prevented or

delayed by any reason of Force Majeure for a period exceeding sixty days, either party may at its


option terminate the contract without any financial repercussion on either side. There may be a

Force Majeure situation affecting the purchase organization only. In such a situation the

purchase organization shall take up with the supplier on similar lines as above for further

necessary action.

11.0 Continuance of the Work

11.1 Notwithstanding any disagreement, dispute, protest, request for arbitration or court

proceeding relating directly or indirectly to the works, at all times the Service Provider

shall proceed with the work in accordance with the determinations, instructions and

clarifications of IMD. If the Vendor fails to proceed with the work, he shall be considered

to be in default. Such Vendor shall be held liable for any costs and expenses arising from

its failure to do so. During the period the Vendor is proceeding with the work, he shall be

paid the undisputed portion of his claim or payment, under the Agreement.

12.0 Assignment

12.1 The Vendor may sub-contract the services under this Agreement or any benefits or

interests arising under it, subject to the prior written approval of IMD.

13.0 Warranty and Acceptance of Work

13.1 The Service Provider warrants that the work will be performed in accordance with

this Agreement and good scientific practice and standards.

13.2 The Service Provider hereby agrees to provide a comprehensive warranty for the

total system for a period of THREE (3) YEARS from the date of satisfactory

completion of all deliverables of the project and acceptance test performance i.e., at

GO-LIVE phase as declared by IMD.

14.0 Variations

14.1 This Agreement as specified in Clause 3.2 constitutes the entire agreement of the

Parties.

14.2 No variation in the terms and conditions of this Agreement will be valid unless made

in writing by authorised signatories of both parties.

15.0 No agency

15.1 IMD and the Service Provider act independently of each other. Neither party is agent

for the other and neither party has any authority to enter into any agreement, whether

expressly or by implication, in the name of the other party, without that party's prior written

consent for express purposes connected with the performance of this Agreement.

16.0 Language for Communication


16.1 The language of the Agreement and of all notices and communications hereunder

shall be in English.

17.0 Time is the essence

17.1 Time shall be the essence as regards to any date or period determined under this

Agreement unless any date or period specified in this Agreement is varied or

amended according to Clause 14.0, in which case time shall be of the essence as

regards the varied date or period.

18.0 Public statements

18.1 This Agreement is confidential. Neither party shall publicise its existence or its terms. The

Service Provider shall not use the name or any trade mark or trade name, whether registered or

not, of IMD, in publicity releases or advertising or in any other manner, including any customer

lists, without securing the prior written approval of the IMD.

19.0 Notices

19.1 Any notice given under this Agreement by either party to the other must be in writing and

may be delivered personally or sent by facsimile followed by post with advice of delivery. In the

case of facsimile, the notice will be deemed to have been given upon receipt of the correct

answer-back or receipt code. Notices will be delivered or sent to the parties addresses listed

below or to any other address notified in writing by either party to the other for the purpose of

receiving notices after the date of this Agreement.

19.2 The address for service to IMD is:

HEAD NATIONAL DATA CENTRE, HEAD, CLIMATE RESEACH AND SERVICES, INDIA METEOROLOGICAL DEPARTMENT, SHIVAJINAGAR, PUNE 411005 MAHARASHTRA, INDIA TELEPHONE : +91 20 25535281 19.3 The address for service to the Service Provider is:

• company name

• contact person

• street address 1

• street address 2

• city,

• post code,

• country


FORMAT: SERVICE LEVEL AGREEMENT (SLA) DATED THIS DAY OF -------------

2019

BETWEEN :Office of Climate Research and Services, India Meteorological

Department, Pune hereinafter referred as IMD, Pune, on behalf of President of India

which expression shall include, unless repugnant to context,, represented

by.…………………………..

AND: XXX hereinafter called "VENDOR " represented by holder of General Power of

Attorney dated executed pursuant to Resolution No. dated passed by Board of Directors.

INTRODUCTION

Whereas -

the IMD, Pune requires services to establish and manage state-of-the-art National

Climate Data Centre to be developed with facilities of data Acquisition, QA/QC process,

monitor, archival/ retrieval /e commercialization, data product generation, develop tools

for its smooth functioning facilities at IMD, Pune and the VENDOR agrees to develop

Climate Data Service Portal now wish to record the basis on which the services are to be

provided.

The timings for SLAs are given in the table below:

Table 4. Timings for SLA

Timings 24x7

Prime Hours 9:00 AM to 6.30 PM

Non Prime Hours 6.30 PM to 9:00 AM

Period Contract Period

Locations Pune

1. Purpose of this Agreement

The purpose of this SLA is to clearly define the expected levels of service to be provided by VENDOR to IMD for during the entire duration of this contract or till the amendment of SLA whichever is earlier. The SLA is designed to:


1 Draw the attention VENDOR and IMD to some aspect of performance only when that aspect drops below an agreed upon threshold, or target and leads to consequent defined action.

2 Define unambiguously the performance related expectations of performance required of the VENDOR

3 Assist the IMD to ensure and control levels and performance of services provided by VENDOR

2. Description of Services

VENDOR shall provide service as defined in Details of Proposal

The following section reflects the measurements to be used to track, and monitor systems performance on a regular basis. The targets shown in the following tables are for the entire period of contract and its extension, if any, and would be part of the mechanism for observance or failure to perform as per SLA.

3. General Principles of Service Level Agreement

3.1. The Service Level agreements have been logically segregated in the following

categories and project phase / periods:

• Project Management – IN THE GO-ALIVE PHASE

• Availability Management

• Performance Management DURING WARRANTY & AMC PERIODS

• Service Management

3.2. Availability Management

Table 5. SLA for availability Management Services

Availability of system - software and network

SNo Components Availability / Uptime Penalty

1 Availability of solution & all components including software and related components etc. at IMD. Uptime will be calculated for all days on a basis of 24 / 7 * 365/366 days availability as applicable

97% (as per monthly status

report)

5 % of

monthly

AMC


Table 6. SLA for service level maintenance

S No

Parameter Service Level

Validation tools/method

Penalty

1 Resolution of issue

logged as per the

Severity definition

chart

99% Reports

generated

from Issue

logging system

95%-99% calls resolved in

specified time: 2% penalty on the

monthly AMC charges

90% - 95% calls resolved in

specified time: 5% penalty on the

monthly AMC charges

2 Evaluation of

VENDOR

Performance

including security

and vulnerability

assessment

(Penetration test,

by CERTIN

empanelled firm) on

ID/IPs to report

quarterly

100% Management

approval of

VENDOR

Performance

evaluation

report

0.5% of Quarterly AMC charges

3 Tracking of VENDOR

SLA & issues logged

with VENDOR

95% Status of

Issues logged

with VENDOR

0.5% of monthly AMC charges

6 The VENDOR should

take backup as per

the backup schedule

defined by IMD

99% Report If the negligence is found in

monthly audit, the Bidder would

be penalized upto a sum of Rs.

5,000/- per negligence.


7 IMD would

periodically (once a

quarter on a

random day)

request the

VENDOR to restore

the backup data

100% Report Rs. 5,000/- or upto 0.5% of

monthly AMC charges for every

restore test failure

8 VENDOR shall

analyze all the

incidents and

provide a root cause

report every month

if there are more

than 10 incidents of

the same type.

VENDOR shall take

the needed

corrective action to

prevent further

issues due to the

same cause.

100%

timely

submissio

n covering

all

incidents

logged in

that

month

• Root cause

report

• Incident

report

stating

problems

faced by

the users

• Document

detailing

corrective

action

• 5% penalty on the monthly

AMC charges of that Project

Area, if the VENDOR does not

submit a problem report for

that month.

• 5% penalty on the monthly

AMC charges of that Project

Area, if the VENDOR does not

perform the corrective action

for more than one calendar

month.

9 Resolution of

Change

Management ticket

logged in Change

Management tool

99% Reports

generated

from Change

Management

System

Covered under 5.1

10 Monthly status

report

95% Report 0.2% of monthly AMC charges

3.3 Problem Notification & Resolution Time Matrix

Maximum time to restore Solution Availability is defined as the time taken to resolve

the problem, starting from the time of logging the complaint and within the time

specified in table below. VENDOR should notify the end user within 20 min after

resolution of problem.

Table 7 . SLA for solution availability


S. No Parameter Maximum time to restore

1 Software REMOTE SUPPORT 2 HRS

ONSITE SUPPORT 24 HRS

ONSITE SUPPORT IN NORTH EAST 36 HRS

VERY IMPORTANT NOTE:

• During the warranty period the penalty payments will be adjusted in the security (PBG)

amount submitted by the vendor and only the balance PBG will be paid to the vendor

• If the VENDOR is not able to meet the above SLA with regard to project timelines for a

period of 5 continuous weeks or 30 days (including Public holidays & non-working days),

IMD may initiate proceedings for termination of the contract

3.3 SLA Supervision

1 Reporting Procedures

The VENDOR’s representative will prepare and distribute SLA performance reports in

an agreed upon format by the 10th working day of subsequent month of the reporting

period. The reports will include “actual versus target” SLA performance, a variance

analysis and discussion of appropriate issues or significant events. Performance reports

will be distributed to the IMD’s IT Team.

2 Monitoring and Auditing

IT Team of IMD will review the performance of VENDOR against the SLA parameters

each month, or at any periodicity defined in the contract document. The review / audit

report will form basis of any action relating to imposing penalty or breach of contract.

Any such review / audit can be scheduled or unscheduled. The results will be shared

with the VENDOR as soon as possible. IMD reserves the right to appoint a third-party

auditor to validate the SLA.

3 SLA Change Control


General

It is acknowledged that SLA may change as IMD’s business needs evolve over the course

of the contract period. As such, this document also defines the following management

procedures:

1 A process for negotiating changes to the SLA.

2 An issue management process for documenting and resolving particularly difficult

issues.

3 IMD and VENDOR management escalation process to be used in the event that an

issue is not being resolved in a timely manner.

Any changes to the levels of service provided during the term of this agreement will be

requested, documented and negotiated in good faith by both parties. Either party can

request a change. Changes will be documented as an addendum to this document and

consequently the contract.

SLA Change Process

Both the parties may amend this SLA by mutual agreement in accordance. Changes can

be proposed by either party. Normally the forum for negotiating SLA changes will be

IMD’s monthly review meetings.

Version Control

All negotiated SLA changes will require changing the version control number. As

appropriate, minor changes may be accumulated for periodic release (e.g. every quarter)

or for release when a critical threshold of change has occurred.

3.4 Risk and Cost Factor

In the event of termination of contract on the basis of non-performance by the VENDOR as

per SLA, VENDOR will be solely responsible for risk and cost factor thereon.


1 Breach of SLA

In case the VENDOR does not meet the service levels mentioned here in, for three (3)

continuous time-periods as specified in the relevant clause, the IMD will treat it as a case of

breach of Service Level Agreement. The following steps will be taken in such a case:-

1. IMD issues a show cause notice to the VENDOR.

2. VENDOR should reply to the notice within three working days.

3. If the IMD authorities are not satisfied with the reply, the IMD will initiate termination

process.

2 Exclusions

The VENDOR will be exempted from any delays or slippages on SLA parameters arising

out of following reasons:-

• Delay in execution due to delay (in approval, review etc.) from IMD’s side. Any such

delays will be notified in written to the IT Team.

• Force Majeure

• The network links will be provided by a third party and the VENDOR will monitor and

report any problems on behalf of third party. If VENDOR notifies and IMD approves that

the delay or fault was due to the third party link services then such loss will not be

considered for tracking VENDOR’s SLA parameters (Also reduced from total service

time).

3 Signature

IN WITNESS WHEREOF, the parties hereto have caused this Service Level Agreement

to be executed by their respective authorized representatives as of the date first written

above.

VENDOR IMD

Signature ------------------------ Signature ------------------------

Name ------------------------ Name ------------------------

Address ------------------------ Designation ------------------------

Company ------------------------

Date ------------------------ Date ------------------------

3.4 Issue Management Procedures


General

This process provides an appropriate management structure for the orderly consideration and

resolution of business and operational issues in the event that quick consensus is not reached

between IMD and VENDOR. It is expected that this pre-defined process will only be used on an

exception basis if issues are not resolved at lower management levels.

Issue Management Process

• Either IMD or VENDOR may raise an issue by documenting the business or technical

problem, which presents a reasonably objective summary of both points of view and

identifies specific points of disagreement with possible solutions.

• IMD and the VENDOR’s representative will determine which committee or executive level

should logically be involved in resolution.

• A meeting or conference call will be conducted to resolve the issue in a timely manner.

The documented issues will be distributed to the participants at least 24 hours prior to the

discussion if the issue is not an emergency requiring immediate attention.

• Management of IMD and VENDOR will develop a temporary, if needed, and the

permanent solution for the problem at hand. The VENDOR will then communicate the

resolution to all interested parties.

• In the event a significant business issue is still unresolved, the arbitration procedures

described in the Contract will be used.

END OF SECTION 5


Annexure-I

CHECKLIST

S. N Activity Compliance

Yes/ No/ NA

Page No.

of your bid

1 Is Firm Registration certificate from Government bodies in

their country attached with technical bid?

(i) Have you enclosed EMD (Bank Guarantee) of required

amount?

(ii) Is the EMD submitted by firm other than participating

firm? If yes, then bid is likely to be ignored.

(iii)Is Registration certificate from NSIC/Government bodies on

SSI attached for relaxation of EMD?

(iv)EMD shall be valid for 240 days.

3. Have you kept validity of your bid as per the TE document?

4. Have you enclosed Tender Terms & Conditions Acceptance

Form duly filled and signed (i.e. terms and conditions are

acceptable) with original set of tender? Tenders may be

ignored if not signed.

5. Have you enclosed clause-by-clause compliance statement for

the “List of requirements/ technical specifications” section?

6. Have you submitted copy of the last purchase order(s) and end

user certificate?

7.

Is tender Submitted by an OEM?

Is tender Submitted by an integrator Agent/ Dealer/ Supplier/

Distributor/ Stockiest etc. of OEM? Whether Back-to-back

support agreement with equipment manufacturer and

software developer company attached?

8. (i) Permanent Account No. of bidding firm with proof.

(ii) Is sales & service tax /GST number with registration

certificate attached?

9. Name of the firm who quoted the price

10. Name of tender currency given in which order to be placed?

11. Name of the supplier with complete address to whom supply

order to be placed to be submitted on company’s letter head

in original from authorized signatory.

(Name & Signature with date and firm/company seal)


Annexure-II

Tender Terms & Conditions Acceptance Form

(For all the terms & conditions of tender document are acceptable to Bidder)

To

The Head, Climate Research and Services,

India Meteorological Department,

Shivajinagar, Pune – 411 005.

Ref: TE document No. CRS/SID/PUD/9016 (CPPP)/0719/05 dated _________

I/We, the undersigned have examined the above mentioned TE document, including

amendment/corrigendum No. __________, dated ________ (if any), the receipt of which is hereby

confirmed. We now offer to supply and deliver the goods and services in conformity with your above

referred document.

If our tender is accepted, we undertake to supply the goods and perform the services (Installation &

commissioning etc.) as mentioned in tender document with the delivery schedule specified in the “RFP-

List of requirements / technical specifications”.

I/We further confirm that, if supply / purchase order is placed to firm, we shall provide performance

security of required amount in an acceptable form for due performance of the contract.

I/We agree to keep our tender valid for acceptance as required in tender document or for subsequently

extended period, if any, agreed to by us. I/We also accordingly confirm to abide by this tender up to the

aforesaid period and this tender may be accepted any time before the expiry of the aforesaid period.

I/We further confirm that, until a formal contract is executed, this tender read with your written

acceptance thereof within the aforesaid period shall constitute a binding contract between us.

I/We further understand that you are not bound to accept the lowest or any tender you may receive

against your above-referred tender enquiry.

We confirm that we do not stand deregistered/banned/blacklisted by any Govt. Authorities. I/We confirm

that we fully accept and agree to all the terms and conditions specified in above mentioned TE document,

including amendment/ corrigendum etc. if any.

(Signature with date and seal of the company)

(Name and designation)

Duly authorized to sign tender for and on behalf of Bidder

Note: 1. Firm/company shall use its own printed letter head for issuing this certificate.

2. Acceptance shall be unconditional.


Annexure – III

MODEL BANK GUARANTEE FORMAT FOR FURNISHING EMD

(Format only)

Whereas …………………………………………………………………………………….

(hereinafter called the “Bidder”)

has submitted their offer dated ………………………….……………………………… for the supply of ….

………………………………………………………………………..

(hereinafter called the “tender”)

against the purchaser’s tender enquiry No. ……………………………………………… KNOW ALL MEN by these

presents that WE.…………………………………………...

of ……………………………………………. having our registered office at

……………………………………………………………. are bound unto ………………

(hereinafter called the “Purchaser)

in the sum of …………………………………………………………………………….…

for which payment will and truly to be made to the said Purchaser, the Bank binds itself, its successors

and assigns by these presents. Sealed with the Common Seal of the said Bank this…………… day of

…………….20……

THE CONDITIONS OF THIS OBLIGATION ARE:

(1) If the Bidder withdraws or amends, impairs or derogates from the tender in any respect within the

period of validity of this tender.

(2) If the Bidder having been notified of the acceptance of his tender by the Purchaser during the period

of its validity.

(3) If the Bidder fails to furnish the Performance Security for the due performance of the contract.

(4) If the Bidder fails or refuses to accept/execute the contract.

WE undertake to pay the “The, Head, Climate Research and Services, India Meteorological Department,

Pune”, up to the above amount upon receipt of its first written demand, without the Purchaser having to

substantiate its demand, provided that in its demand the Purchaser will note that the amount claimed by

it is due to it owing to the occurrence of one or both the two conditions, specifying the occurred

condition or conditions.

This guarantee will remain in force up to and including 60 days after the period of tender validity and any

demand in respect thereof should reach the Bank not later than the above date.

Bank Guarantee issued with the tender enquiry reference No. CRS/SID/PUD/9016 (CPPP) /0719/05 Dated

_______

(Signature of the authorized officer of the Bank)

………………………………………………………….

Name and designation of the officer

………………………………………………………….

Seal, name & address of the Bank and address of the Branch


ANNEXURE - A

PROFORMA FOR PERFORMANCE BANK GUARANTEE (PBG)

(To be stamped in accordance with Indian Stamp Act)

Bank Guarantee No. __________________ Date: __________

Valid upto __________________________ Amount: __________

To

The Office of Head, Climate Research and Services

INDIA METEOROLOGICAL DEPARTMENT, PUNE

Dear Sir,

1. In consideration of Office of Climate Research and Services at INDIA METEOROLOGICAL

DEPARTMENT, PUNE having its office at Shivajinagar, PUNE 411005 (hereinafter referred to as

“IMD” which expression shall unless repugnant to the context or meaning thereof, include all its

successors, executors, administrators and assignees) and having entered into an Agreement

dated ____________________ (hereinafter referred to as “Contract” which expression shall

include all amendments thereto) with M/s.______________________________________ having

its Head/ Registered office at ___________________________________ (hereinafter referred to

as “Service Provider” which expression unless repugnant to the context or meaning thereof, shall

include all its successors, executors, administrators and assignees) and the Agreement having

been unequivocally accepted by the Service Provider resulting into a contract with IMD, PUNE

(Scope of Work) ________________ and the IMD, PUNE having agreed that the Service

Provider shall furnish to the IMD a Performance Guarantee for the faithful performance of the

entire Contract (including but not limited to Guarantee Warranty, Satisfactory

Installation/Commissioning/Performance of the Equipment/ Product/System/Services to the

extent of 10% of the value of the Contract, i.e., Indian Rupees________________ (in words), We

_________ (Bank) _________________ having its Registered office at

_________________________ (hereinafter referred to as “BANK” which expression shall unless

repugnant to the context or meaning thereof, include all its successors, administrators, executors

and assignees) do hereby undertake to pay on demand to the IMD any money or all monies to


the extent of Indian Rupees________________ (Indian Rupees _______________ ) in

aggregate at any time without any demur, reservation, recourse, contest or protest and /or

without any reference to the Service Provider. Any such demand made by the IMD on the BANK

shall be conclusive and binding notwithstanding any difference between the IMD and the Service

Provider or any dispute pending before any Court, Arbitrator, Tribunal or any other authority. We

agree that Guarantee herein contained shall be Irrevocable and shall continue to be enforceable

till it is discharged by the IMD in writing.

2. IMD shall have the fullest liberty, without affecting in any way the liability of the BANK under

the Guarantee, from time to time, to extend the time for performance of the Contract by the

Service Provider, or vary the terms of the Contract. IMD shall have the fullest liberty without

affecting this Guarantee to postpone, from time to time, the exercise power vested in them or of

any right which they might have against the Service Provider and to exercise the same at any

time in any manner and either to enforce, or to forebear to enforce, any covenants contained or

implied in the Contract between IMD and the Service Provider or any other course or remedy or

security available to IMD. The BANK shall not be released of its obligations under these presents

by any exercise by IMD of its liberty with reference to the matters aforesaid or any of them or by

reason of any other action or forbearance or other acts of omission of commission on the part of

IMD or any other indulgence shown by IMD or by any other matter or thing whatsoever, which

under law would, but for this provision, have the effect of relieving the BANK.

3. The BANK also agrees that IMD at its option shall be entitled to enforce this Guarantee against

the BANK as a principal debtor, in the first instance, without proceeding against Service Provider

& notwithstanding any security or other Guarantee that IMD may have in relation to the Service

Providers liabilities.

4. The BANK further agrees that the Guarantee herein contained shall remain in full force during

the period that is taken for the performance of the Contract and it shall continue to be

enforceable till all the dues of IMD under or by virtue of this Contract have been fully paid and its

claims satisfied or discharged or till IMD discharges the Guarantee in writing.

5. We further agree that as between us and IMD for the purpose of this Guarantee any notice

given to us by IMD that the money is payable by the Service Provider and any amount claimed in

such notice by IMD shall be conclusive and binding on us notwithstanding any difference

between IMD and the Service Provider or any dispute pending before any Court, Tribunal,

Arbitrator or any authority. We further agree that this Guarantee shall not be affected by any


change in our Constitution or that of the Service Provider. We also undertake not to revoke this

Guarantee during its currency.

6. Notwithstanding anything contained hereinabove, our liability under this Guarantee is limited to

Indian Rupees_______ (Indian Rupees _____________________) in aggregate and it shall

remain in full force up to and including 60 days after ___________unless extended further, from

time to time, for such as may be instructed in writing by M/s. __________________ on whose

behalf this Guarantee has been given, in which case it shall remain in full force up to and

including 60 days after the extended date. Any claim under this Guarantee must be received by

us before the expiry of 60 days from ____________ or before the expiry of the 60 days from the

extended date, if any, if no such claim has been received by us within the 60 days after the said

date/extended date, IMD’s right under this Guarantee will cease. However if such a claim has

been received by us within and up to 60 days after the said date/extended date, all the IMD’s

rights under this Guarantee shall be valid and shall not cease until we have satisfied that claim.

7. We further confirm that this Guarantee has been issued with the approval of the appropriate

Exchange Control Authorities in _______(if required) and that the issue of this guarantee is in

order and in accordance with the Laws and Regulations in force in ______________.

8. We also agree that this Guarantee shall be governed by and construed in accordance with

Indian Laws.

Dated this _____ day of _____________ 2019 at __________ .

Yours faithfully,

___________________

WITNESS No. 1 (Signature)

______________ Name in full __________________

(Signature with full name and Designation _________________

address) (With Bank stamp)

WITNESS No. 2 _____________________ Attorney/Code No.___Date ______ (Signature with full name and address)

END OF ANNEXURE - A


ANNEXURE - B PROFORMA OF PRICE BID

(To be submitted in Duplicate)

Tender for: Design, development and implementation of Climate Data Services Portal at IMD,

Pune.

a) Note: Total price for comparative evaluation shall include all charges including application development, charges towards preparation of SRS, metadata generation, Data Migration, Database Design, Application Development, Database Generation, Integration, Testing, Commissioning and vendor management responsibilities, Charges/ remuneration of the personnel to be stationed at IMD during the execution of the project, Comprehensive Maintenance Contract charges for three years for the total system on expiry of the two years Warranty.

b) Bidders should quote the rates strictly in accordance with the formats given below failing which their offer shall be rejected.

c) The quoted price shall include all activities required by the Service Provider and shall include but not be limited to the Analysis & Design of the Total System based on the functional requirements of IMD, Preparation and submission of a detailed proposal to IMD for consideration, with generic specifications of the Hardware, Software, Networking Components and any other component proposed in the above Architecture, Application Software Development and deployment based on the Functional Requirements described in this Document, Data Migration, Database Design, Database Generation, Integration, Testing & Commissioning including vendor management responsibilities, three years Warranty etc. The fees for Annual Maintenance Support for three years on expiry of the warranty should be provided separately. However, the evaluation of the bids will be done on the basis of formula detailed at 3.3.1 of the Tender Document.

B 1 Analysis and design of the total system, preparation of SRS document, Data Organization, Data Migration, Database Design, Database Generation, Integration, Testing & Commissioning, two years comprehensive warranty and vendor management responsibilities

Details AMOUNT IN INDIAN RUPEES

In figures In Words

Analysis and design of the total system, preparation of SRS document, Data Organization, Data Migration, Database Design, Database Generation, Integration, Testing and Commissioning, two years comprehensive warranty and vendor management responsibilities.


B 2 Application Software Developments and Deployment


In Figures In Words

Customised Application software development for

design, development and implementation of user-

friendly portal, UI and required tools for the activities of

data acquisition / reception, monitoring, quality

processing, archival, data retrieval data analytics and

visualization and commercialization.

B 3 Taxes if any (Please indicate % of taxes applied on the above)


In Figures In Words

I) Total: B1+B2+B3

B 4 Post-Warranty Annual Maintenance Support for three years


In Figures In Words

Post-Warranty Annual

Maintenance Support, total

for three years

B 5 Any other taxes (Please indicate % of taxes applied on B4)


In Figures In Words

Taxes

II) Total: B4+B5

III) Grand Total : Total of I + Total of II

Date: Signature of the bidder

Name and full address

END OF ANNEXURE B


ANNEXURE ‘C’ PAYMENT SCHEDULE

TERMS OF PAYMENT

C1 The Service Provider shall issue invoices in Duplicate, complete in all respects

with supporting certification for completion of each milestone (as detailed

below), duly signed and submit to the IMD, Pune for verification and payment.

C2 The payment shall be released within 30 days of receipt of invoice based on

the satisfactory completion of milestones and duly certified by IMD, Pune as

detailed below:

Table 8. PAYMENT SCHEDULES WITH MILESTONES

Milestones Deliverables Percentage of

total value [(III)

Grand Total} as

described in

Annexure B

On finalization of Agreement,

Submission of Performance Bank

Guarantee (PBG) and completion of

System Requirement Specification (SRS);

Ref: section 4.1.

➢ Project kick off / Sign of document

➢ Complete Project Plan along with slippage details

➢ SRS document

10 %

On (a) completion of organizing and

migration of all existing datasets from

various media to centralized storage

facilities, and (b) meta-data generation;

Ref: section 4.1.

➢ Procedure or document for how to Migrate Datasets

➢ Database Design Document

➢ Migrated datasets (it is an iterative step)

➢ Metadata form ➢ Wireframe work

document for application software and admin panel

10 %

On completion of design and generation

of database, application software

➢ Test Cases (UTC, System Integration

10 %


development based on functionalities;

Ref: section 4.1.

Test Cases) in the form document (hard and soft copies)

➢ Alpha version of the application software and admin panel

➢ Source Code for alpha version application software and admin panel

➢ Servers: Application Server, DB Server, Backup Server

➢ Storage System

On completion of system integration,

commissioning of hardware, software,

network components, peripherals, etc

for the application deployment; Ref:

section 4.1

➢ System/Server Administration Document

➢ How to Document for Admin Panel

➢ List of reports to be generated


➢ Storage System

15 %

User training/ User acceptance testing;

Ref: section 4.1

➢ Beta Version of application software and Admin Panel

➢ Source Code for Beta Version Application Software and Admin Panel


➢ Storage System

25 %

On completion of the project and after

receipt of all deliverables to the full

satisfaction of IMD

➢ Final version of Application Software and Admin Panel

➢ Source code for Final version of

30 %


Application Software and Admin Panel

➢ Monitoring System for MGSDB


➢ Storage System

AMC (shall be entered separately) Quarterly (pro-rata basis on agreed amount

for three-years), against submission of the

invoice in original and subject to satisfactory

performance. For quarterly advance

payment, a Bank Guarantee from a

Nationalized Bank for the AMC value for year

to year basis should be provided.

C3 IMD, Pune will pay all the amount of fees in Indian Rupees, as per Annexure ‘B’,

to the account of the Service Provider. Taxes if any, to be deducted at source, shall be

so deducted from the payment, as provided in clause 3.3 of Section 3.

C4. Payment of Comprehensive Annual Maintenance/Technical Support (AMC):

C 4.1. All the following payments for the services will be made after being subjected to

SLA penalty / performance / support clauses, if any during the period.

C 4.2. AMC Payment along with applicable taxes for the first year will be made on

submission of invoices after delivery of Software licenses and the source codes for

various modules and application utilities. The entire packages of software thus

developed will become the property of IMD.

C4.3 . AMC Payment along with applicable taxes for operational and maintenance from

the second year onwards will be made against submission of invoice, one month prior to

expiry of previous year of support. Vendor should ensure that there is no reinstatement of

software license.

END OF ANNEXURE C


ANNEXURE D

DELIVERABLES AND TIME LINES

1 Issue of Tender Document W

2 Firm to submit queries on Tender, if any (via

e-mail)

[Note: Firm may submit a consolidate query

only once]

W+2

3a Pre-bid Meeting

W+4

3b Presentation by bidders on technical

solution keeping into consideration Tender

section 4 (max. 30 mins/bidder) [Mandatory

for all bidders]

W+4

4 Issue of final Tender Document W+6

5a Submission of Technical and Financial bids W+10

5b Opening of the Technical bid W+10

6 Opening of Financial bid W+16

7 Award of contract W+18

• The dates mentioned in the NIT may be seen

END OF ANNEXURE D


ANNEXURE E

PROPOSAL DOCUMENT SUBMISSION FORM

To: India Meteorological Department, Pune – 411 005, India

1. Having examined the Tender Document dated ________ including the Service Agreement and all the Annexures for the performance of the Services tendered for, we, the undersigned, hereby offer to perform the Services in conformity with all the Conditions set out in the Tender Document.

2. We undertake, if our Bid is accepted, to perform the whole of the Services comprised in the Agreement within the time schedule provided and at the rates quoted by us, if found acceptable to IMD.

3. We agree to abide by this Tender for a period of 180 days from the last date fixed for receiving the same and it shall remain binding upon us and may be accepted by you at any time before the expiration of that period.

4. This Bid is submitted under our covering letter reference ……………………….dated ………………………., and the completed documents and information required as enclosed therewith, shall be read and construed as forming part of our Bid.

5. This Bid with your written acceptance thereof shall constitute a binding agreement between us.

6. We understand that you are not bound to accept the lowest or any Bid received. 7. I agree and accept all the terms and clauses of this Tender document.

Signature……………………………………... Name………………………………………….. For and on behalf of …………………………………………………. ………………………………………………….

…………………………………………………. Duly authorized to sign Bids for and on behalf of the bidder ……………………………………………………………………………………………… Date:

END OF ANNEXURE E


ANNEXURE F

EXISTING MODES OF IMD DATA RECEPTION AND REQUIREMENTS IN THE PROPOSED DATA ACQUISITION SYSTEM

F1. INTRODUCTION

F1.1. Data Generation and Reception

India Meteorological Department generates lot observational data every day, consisting of

parameters like Temperature, pressure, wind, rainfall and cloud, visibility, environmental

parameters etc. These data are generated by manual observations at the meteorological

observing stations (MO) or/and by the Automatic Weather Station(AWS).

The purpose of the proposal is to develop a portal supported by National Climate Data

management activities to facilitate the following and to provide a state-of-art data centre

capabilities

• receive data from various sources (existing and future augmentations)

• Monitor data reception and alert the originating station if not received

• Apply on-line quality controls by two-way communication for data errors

• Archive quality controlled data in a relational data base form

• All these activities to be on-line with minimum manual interventions

In addition, the system should cater generation of various data products through user-friendly

tools and enable data visualization and value-additions on the data. There should be a on-line

system for supply of data, payment and commercialization and remote accessibility for climate

service procedures

In the first stage, the data generation and reception are discussed followed by the facilities

available in the existing and the proposed systems.

F1.2. Observations and Network

The network of meteorological observatories existing in the country is listed as below based on types of observational data.

Surface Observatory


o Departmental (200) o Non-departmental (350)

Upper air Observatory

o Radiosonde (RS) & Radiowind (RW) – 36 o Upper wind – 65

Rainfall

o DRMS (2700) o State Raingauges (6000)

Autographic Data ( Hourly Data)

o Temperature (180) o Pressure (160) o Rainfall (540) o Sunshine (70) o Relative Humidity (180) o Wind (60)

Automatic Weather Stations

o AWS and ARG (1500) o Radiation (45) (at 10 Min Interval)

Agrometeorological Data

o Evaporation(89) o Evapotraspiration (47) o Soilmoisture (46) o Crop Weather Scheme (230) o Dew (100)

Radiation Data

o Global (37) o Diffused (33) o Bimetallic (7) o Terrestrial (12) o Direct Solar (13) o Global On Inclined Plane (1) o Net (5) o Direct (9) o Reflected (1) o Radiometersonde (5)


Environmental Data o Air pollution and Atmospheric Chemistry (10)

Ozone Data

o Surface, Total, Ozonesonde etc (5) Marine Data (Global) Expeditions Data - Antarctica, MONEX etc., Air Port Observations

o Current Wx and Significant Wx Data (75) High Speed Wind recorder Data F 1.3. DATA SAMPLE FORMATS: F.1.3.1. AWS code

F 1.3.2. surface data format

F 1.3.3. ozone data

F 1.3.4. Binary Universal Format for Representation (BUFR)

The above codes and format along with explanation and details will be supplied as document file for vendors’ use.

F1.4. Modes of Data Generation:

There are two modes of data generation and reception being practiced at IMD. One is manual

and the other one is automatic way of generation and reception. They are explained in the

following sections in detail.

F2. Procedures in the data reception through Manual Observations

The observer records the meteorological observations at Met Observatories (MO) and writes

them in observer log books, and transmits the observations to Met. Centres (MC) in the form of

coded messages like SYNOP, TEMP, METAR etc., being used or operational weather forecasting.

This transmission is done using VPN network / Phone. This meets the forecasting needs of the


department. These coded messages are not archived at any central locations. These

observations are written in the paper form. These manuscripts are sent to the MCs regularly. The

frequency of transfer of these manuscripts to MCs is normally one month. These data are

manually scrutinized at MCs for gross error checks, writing them in proper formats, checking for

the valid calculations etc. After the scrutiny data are keyed-in at MCs and they are then

transferred to National Data Centre (NDC), Pune for further processing. The mode of transfer is

through e-mail / CDs (mainly through e-mails). At NDC, these data are subjected to different

checks, like valid character checks, duplicate check, sequence check for checking the availability

of continuous records, and quality checks (outliers, internal consistency between the parameters

and climatological checks). The doubtful values / errors are sent back to the MCs for clarification

and validation. After the validation data are archived at NDC. These data bear no quality flags.

These archived data are supplied to different users as per their requirements. This cycle of data

observation to the archival at NDC takes few months to one year. The delay at MCs to scrutinize,

keying and validation mainly occurs due to shortage in the manpower as they are mainly utilized

for operational forecasting jobs.

It is natural that, the delay in the data reception at NDC will be minimized if NDC receives these

data directly from the observing stations and in the electronic form. In this direction, some

efforts are on, like the surface observations, to disseminate data through hand-held data loggers.

This eliminates the manuscript recording form and once the data in the electronic form can be

transmitted to NDC quickly. Any data generated at MOs should reach NDC in a real-time mode.

However, till such a real-time system is evolved in the entire network of observations, system for

receiving the data on delayed mode too needs to be continued.

F3. Automatic Data Reception

These data are generated at AWS / ARG / Agro AWS stations. The data generated are received

through satellite communication channel at the receiving station at centralized computer system

at Pune. These data are properly coded in the specific format and are sent to AMSS network for

the operational use. They are also stored at central station. However at present all the data are


not transmitted in the AMSS network. For this reason even though NDC has AMSS connectivity it

could not receive all the data generated by these automatic stations. Hence it will be better to

have an alternative to establish a suitable FTP server so that all the data are received by NDC.

Different types of data generated at MOs, their possible ways of transmission to MCs and NDC

along with other details are indicated in the tables F1 and F2.

Table 9. Reception Details for various Data Types

1. SURFACE DATA

Data Type Synoptic Hour

Synoptic Hour

Day’s Summary

Day’s Summary

Autographic

Reception From

MC/MO MC / MO MC/MO MC / MO MC

Reception Mode

AMSS FTP / e-mail / SMS

AMSS FTP / e-mail / SMS

FTP / e-mail

Reception Form

SYNOPs Hand Held Data Logger / MMR

SYNOPs Hand Held Data Logger / MMR

Tabulation Sheets

Reception Type Coded Text / BUFR

Text File Coded Text / BUFR

Text File Text file

Return Path FTP / e-mail / SMS

FTP / e-mail / SMS

FTP / e-mail / SMS

FTP / e-mail / SMS

FTP / e-mail

Frequency 3 Hourly 3 Hourly Daily at 3 UTC

Daily at 3 UTC

Once a Month

Validation within

One hour One Hour One hour One Hour One day

No. Of Stations 530 530 530 530 Abt 500 stns for Rainfall and 200 stations for other Parameters

Remarks This has higher priority as

This has higher priority as

These data are tabulated at MCs and are keyed in


rainfall data up to one place of decimal

rainfall data up to one place of decimal

electronic form

2. RAINFALL DATA

Data Type DRMS (Daily Rainfall Measuring Scheme

State Rain gauge

Reception From

MC Hydrology section

Reception Mode

FTP / e-mail FTP / e-mail

Reception Form

Text Text

Reception Type

Text / Excel Text / Excel

Return Path FTP / e-mail FTP / e-mail

Frequency Once a day As and when received from State authority

Validation within

One hour One week

No. Of Stations

3300 6000

Remarks

3. UPPER – AIR OBSERVATION

Data Type Radiosonde Radiosonde Pilot Ballon

Manual Flights

Reception From MOs / MCs MOs / MCs MOs / MCs Upper-air section


Reception Mode

AMSS AMSS AMSS FTP / e-mail

Reception Form TEMP TEMP / PILOT TEMP / PILOT

Reception Type Coded text / BUFR

Text Coded text / BUFR

Text

Return Path FTP / e-mail FTP / e-mail FTP / e-mail FTP / e-mail

Frequency 6 or 12 hourly 6 or 12 hourly 6 or 12 hourly

Once a month

Validation within

One hour One hour One hour One week

No. Of Stations 39 39 62

Remarks The text files generated consisting of high resolution data (at 50 hpa interval) Provision to store the original data

4. RADIATION DATA

Radiation Ozone Radiometer Sonde (RS)

Environmental Data

High Speed Wind recorder

Data Type Global, Diffused, Bimetallic, Direct, net , Reflected, Direct Solar, Terrestrial

Surface, Total, Ozonesonde

Turbidity, Precipitation Chemistry

Reception From Radiation Unit

Ozone Centre

Air Pollution Section

Reception Mode FTP / e-mail /other electronic

FTP / e-mail /other electronic



other electronic


media media media media media

Reception Form Text files Text Files Text Files Text Files Text Files

Reception Type Text Text Text Text Text

Return Path FTP / e-mail/ other electronic media

FTP / e-mail /other electronic media



other electronic media

Frequency Once a month

As per the schedule

As per the schedule

As per the schedule

As per the schedule

Validation within

One week One week One week One week One week

No. Of Stations 45 6 including Antarctica

Remarks

5. MARINE DATA (SHIP DATA)

Data Type

Reception From Ship GCC – UK

Reception Mode AMSS AMSS

Reception Form SYNOPs e-mail

Reception Type Coded Text / BUFR Coded Text

Return Path

Frequency Hourly / 3 Hourly Once in 3 months

Validation within Only data quality flagging To be loaded to Data base

No. Of Stations 1500 1500


Remarks To be loaded to Data base as it is a quality checked data

6. AGROMETEOROLOGICAL DATA

Data Type CWS Evaporation Evapotranspiration Soil moisture

Dew

Reception From

Agrimet Division

Agrimet Division

Agrimet Division Agrimet Division

Agrimet Division

Reception Mode

FTP /e-mail/other electronic media





Reception Form

Predefined Text format





Reception Type Coded text Coded text Coded text Coded text Coded text

Return Path FTP /e-mail/other electronic media





Frequency *** *** *** *** ***

Validation within

*** *** *** *** ***

No. Of Stations 250 60 50 15 70

Remarks

Note: *** Data reception need to be studied before fixing latency period

7. AVIATION DATA

Data Type Current Weather data at Airports


Reception From IMD Airport stations

Reception Mode AMSS / FTP

Reception Form METAR / SPECI

Reception Type Coded Text / BUFR

Return Path

Frequency Hourly or half hourly

Validation within data quality flagging

No. Of Stations 70

Remarks

Table 10 . Reception details of Automatic Stations

S.N. Data Type

Reception from

Reception Form

Mode of reception

Priority

Return Path

Frequency

Reception type

Remarks

1 AWS

SYNOPS

AWS Mobil Synop

FTP/AMSS

1 Every hour

Text / BUFR

Doubtful data to be flagged

ARG Mobil Synop

FTP/AMSS

1 Every hour

Text / BUFR


AWS – Agro

Text FTP/AMSS

1 Every Hour

Text / BUFR


FTP/AMSS

2 Radiation

Automatic Stations

Text FTP/AMSS

1 Every hour

Text / BUFR


MOs/MCs

MMR Data logger

2 FTP/e-mail/SMS

Text

3 Marine Bouys Ship AMSS 1 Every Text / Doubtful


and Ships

Synops (Mobil Synop)

hour BUFR data to be flagged

Note: Presently there are about 1500 stations however the number would increase three folds in future

F4. BASE – DATA ENTRY FORMS:

To achieve the on-line data entry, base – data entry forms have to be developed for

each type of manual data and the validation through a based from. The formats for

each type of data and their explanations will be made available to vendors at the

pre-bid meeting or before awarding the work.

The entry formats are required (templates) to be made available on the screen and in

customized fashion so as to optimize the efficiency of data entry. The system should

also, as far as possible, validate data as they are entered - catching errors and, where

possible, suggesting alternative values based on climate/extremes of the respective

parameter corresponding to the stations. By this way, it is also possible to use / replace

with default (suggested) values, if possible. First level data quality checks are to be

applied, while entering the data through the entry form. These could be gross limit

checks, station level climatological outliers, and simple internal consistency checks

between the parameters. Second level quality checks consisting of deviation from

normal, time consistency, checking with nearby station, visualization by plotting and

analyzing the data have to be applied at the main data centre.

F5. Metadata documentation and management

In order that meteorological data be useful for future users, it is essential that an

adequate set of metadata be available. Such metadata records (ideally), state precisely

where the measurements were made, by whom, using what instruments, the quality that

has been ascribed to the data, etc. An important general point in this context is that the

innate structure of the metadata in an ideal system will be considerably more complex

than the innate structure of the climate data itself.

F6. Example:


Consider a rainfall observation. Commonly, the essential information content of the data

will be simply of the general form “at station x, for an elapsed period of time ending at

time t, the precipitation was p mm.” The associated metadata, which is needed to fully

interpret the data, could include

• Reference date used by the database (GMT, time zone, others);

• Quality which has been ascribed to the observation;

• History of the values ascribed to the meteorological parameter and any associated

flags;

• Instrument used to record the observation, together with more fine detail on its

own maintenance program, tolerances, internal parameters, etc;

• Name of the observer;

• Full details of the station and its history;

• Details of observations in effect at the time and its history;

• The inventory of the elements stored in the database, their units, their boundaries;

and

• Topographical and ground-cover details of the site, information on surrounding

trees, buildings, etc, and how these have changed with time.

For recording all the above information (meta data) in detail, a computer system is

required with a complex data structure and ability to store graphics (site plans, photos,

possibly images of old documents, etc). Therefore, the hardware should be adequately

sophisticated in order to capture and reproduce a range of images and the underlying

software to be used as the database management system. There is also a need to

provide metadata at the dataset level. The details compiled in the existing metadata

will be made available to vendors along with other documents, if required.

Data may also be the subject of homogenization work, which is intended to remove from

a data set all influences other than those from the underlying climate. Data that has been

the subject of such exercises has a need for additional associated metadata, in order to


accurately represent the nature of the homogenization work. Homogenized data sets

should be a product of the CDMS and never considered as a replacement.

For a detailed treatment of station’s (specific) metadata may be referred from the report

“Guidelines on Climate Metadata and Homogenization” (WMO 2003b) in the World

Climate Data and Monitoring Programme series of publications. These will be given to

the vendors on request.

F7. Quality Control on Data

Quality control is an integral part of any data centre. Quality control is the operational

techniques and activities that are used to fulfil the requirements for Quality of data. The

primary purpose of quality control of observational data is missing data detection, error

detection and possible error corrections in order to ensure the highest possible reasonable

standard of accuracy for the optimum use of these data by all possible users.

NDC at present processes the data in off-line mode i.e. at each stage, be it reception,

quality control, validation and archival, manual intervention is required. This is one of the

major drawbacks which delays the archival of the quality controlled data. Once a two-

way communication system (such as automatic messaging, alerts and reception of

data) with MOs is established, it is possible to apply the real time quality checks and

validation of doubtful values.

F8. Quality Control Checks on Automatic Data generation Stations

F8.1. Quality control, quality assurance

To ensure the quality of automatically generated data such as AWS, etc., a well-

designed quality control system is vital. Efforts shall be made to correct all erroneous

data and validate suspicious data detected by QC procedures and flag the same. The

quality of AWS data shall be known using such quality flag types which have to be

developed. The suitable quality checks and flagging system could be developed as per

the guidelines of the World Meteorological Organization (WMO). The algorithms for

quality checks are to be developed for this purpose. However, it is not possible to


validate the data by these stations as they are automatic stations, we may be required to

only flag the data as doubtful or otherwise. A visualization tool has to be developed for

spatial consistency checks. Some standard types of errors are listed as mentioned

below:

F8.2. Types of errors to assess quality of data

• Random errors are distributed more or less symmetrically around zero and do

not depend on the measured value. Random errors sometimes result in

overestimation and sometimes in underestimation of the actual value. On average,

the errors cancel each other out.

• Systematic errors on the other hand, are distributed asymmetrically around zero.

On average these errors tend to bias the measured value either above or below

the actual value. One reason of random errors is a long-term drift of sensors.

• Large (rough) errors are caused by malfunctioning of measurement devices or

by mistakes made during data processing; errors are easily detected by checks.

• Micrometeorological (representativeness) errors are the result of small-scale

perturbations or weather systems affecting a weather observation. These systems

are not completely observable by the observing system due to the temporal or

spatial resolution of the observing system. Nevertheless when such a

phenomenon occurs during a routine observation, the results may look strange

compared to surrounding observations taking place at the same time.

F8.3. Quality assurance on Data:

All the planned and systematic activities implemented within the quality system, and

demonstrated as needed, to provide adequate confidence that an entity will fulfil

requirements for quality. The primary objective of the quality assurance system is to

ensure that data are consistent, meet the data quality objectives and are supported by

comprehensive description of Methodology. Quality assurance and quality control are

two terms that have many interpretations because of the multiple definitions for the words

"assurance" and "control."


The user should be in a position to know the details on quality flags based on the

procedures followed to understand the flag-type assigned to the data. One should know

whether the data are checked or not; original or derived, or the methodology adopted to

correct the data, etc., and accordingly, he should be provided with the details about the

quality of the data. Hence, a proper quality flagging system for each parameter has to be

adopted.

Some suggestive flagging model is given below: Whether a data (value) is:

• Checked or not;

• Original or not;

• Suspect or not;

• Erroneous or not;

• Correct or not; and

• Calculated (or derived) or not. The flagging model can also describe if a value has been:

• Checked automatically or by an operator;

• Calculated with non-suspect values; and

• Calculated with non-missing values. F8.4. Auto-Quality Control procedures on Manual Data

Once the manual observation data are received in near real time mode rigorous quality checks can be applied. Each type of data are subjected to the quality checks and the errors / doubtful data flags are generated automatically. Only the spatial quality checks which needs visualization by climatologist need human intervention. There should be time bound error flag generation. The doubtful data are to be sent to the concerned MOs automatically and the error flags have to be validated by the observer who has taken the observation within a specified time. This time bound two-way communication can eliminate the time delay from months to hours and archive the quality data. The tables listed under Table F2 above, summarises the different types of data generation, their frequency, validation, mode of reception at Data Centre, mode of return of the error records, and the time schedule within which the flags have to be removed by the observer.

F8.5. Automatic Quality Control Procedures for AWS data

a) Plausible value check:

The aim of the check is to verify if the values of instantaneous data (one-minute average or sum; in case of wind 2- and 10-minute averages) are within acceptable range limits.


Limits of different meteorological parameters depend on the climatological conditions of AWS site and on a season.

In the first stage, QC they can be independent of them and they can be set as broad and general. Most of these thresholds and ranges are pre-set in the AWS systems. However, it is also necessary to know in case the values fall as outliers with respect to station level range for specific parameters. These need to be cross-checked before allowing as quality data. Otherwise, the data needs to be suitably flagged.

Existing limit/range values implemented at any AWS are follows:

• Air temperature: -80 °C . +60 °C;

• Dew point temperature: -80 °C . 35 °C;

• Ground temperature: -80 °C . +80 °C;

• Soil temperature: -50 °C . +50 °C;

• Relative humidity: 0 . 100 %;

• Atmospheric pressure at the station level: 500 . 1100 hPa;

• Wind direction: 0 . 360 degrees;

• Wind speed: 0 . 75 ms-1 (2-minute, 10-minute average);

• Solar radiation: 0 . 1600 Wm-2;

• Precipitation intensity: 0 . 40 mm/minute. b) Time consistency check:

The aim of the check is to verify the rate of change of instantaneous data (detection of unrealistic jumps in values or .dead band. caused by blocked sensors). This is achieved by introducing a step-check test as explained here below:

Based on a maximum allowed variability of any instantaneous value, if the current instantaneous value differs from the previous value(s) by more than a specific limit (step), then, the current instantaneous value falls under the category of error. Some possible limits of a maximum variability for various parameters are listed:

• Air temperature: 3 °C;

• Dew point temperature: 2 °C;

• Ground temperature: 5 °C;

• Soil temperature 5 cm: 1°C;



• Soil temperature 50 cm: 0.5°C;

• Soil temperature 100 cm: 0.1°C;

• Relative humidity: 10 %;

• Atmospheric pressure: 0.5 hPa;

• Wind speed: 20 ms-1 (as 2-minute average);

• Solar radiation: 1000 Wm-2. c) Standard Algorithm to check Variability between two instantaneous values:


In order to compare the possible variability difference between the current instantaneous value with the previous and the succeeding values, the following algorithm can be used. If the condition is not satisfied with the parameters, then the current instantaneous value is erroneous and hence needs to be flagged.

|Vi - Vi-1| + |Vi - Vi+1| ≤ 4·σV , where:

Vi is the current value of the parameter,

Vi-1 is the previous value of the parameter,

Vi+1 is the next value of the parameter,

σV is the standard deviation of the parameter calculated at least from the last 10 minute period.

In the case when the previous value or the next one is missing, the corresponding part of the formula is omitted and but the comparison term instead will be 2·σV .

d) Standard Minimum required variability of instantaneous observations and duration:

This may be also called a persistence test. Once the measurement of the parameter is done for at least 60 minutes using these values available on the data-logger check can be made. If the one-minute values do not vary over the past 60/120/240 minutes by more than the specified limit (a threshold value, as cited below) then the current one-minute value may be treated as erroneous and flagged suitably. Some Possible limits of minimum required variability are stated below:

• Air temperature: 0.1°C over the past 60 minutes;

• Dew point temperature: 0.1°C over the past 60 minutes;

• Ground temperature: 0.1°C over the past 60 minutes;

• Soil temperature 5 cm: 0.1°C over the past 120 minutes;





• Relative humidity: 1% over the past 60 minutes;

• Atmospheric pressure: 0.1hPa over the past 60 minutes;

• Wind direction: 10 degrees over the past 60 minutes;

• Wind speed: 0.5 metre per second (ms-1) over the past 60 minutes.

It is recommended that calculation of a standard deviation of basic variables such as temperature, pressure, humidity, wind at least for the last one-hour period will be of very much use. If the standard deviation of the parameter is below an acceptable minimum, all data from the period should be flagged as suspect.


In combination with the persistence test, the standard deviation is a very good tool for detection of a blocked sensor as well as a long-term sensor drift.

e) Checks for Internal consistencies:

The following are the basic algorithms used for checking internal consistency of data using the relation between two parameters. They may be taken as correct if the following conditions are true, otherwise suspect (erroneous)

• dew point temperature ≤ air temperature;

• wind speed = 00 and wind direction = 00;

• wind speed ≠ 00 and wind direction ≠ 00;

• wind gust (speed) ≥ wind speed;

• both elements are suspect, if total cloud cover = 0 and amount of precipitation > 0;

• both elements are suspect, if total cloud cover = 8 and sunshine duration > 0;

• both elements are suspect, if sunshine duration > 0 and solar radiation = 0;

• both elements are suspect, if solar radiation > 500 Wm-2 and sunshine duration = 0;

• both elements are suspect, if amount of precipitation > 0 and precipitation duration = 0;

• both the elements are suspect, if precipitation duration > 0 and weather phenomenon is different from precipitation type; (1: possible used only for data from a period not longer than 10 minutes). If the value fails the time consistency checks it should be flagged as inconsistent

A technical monitoring of all crucial parts of AWS including all sensors is an inseparable part of the QA system. It provides information on quality of data through the technical status of the instrument and information on the internal measurement status. Corresponding information should be exchanged together with measured data.

F9. Extended or Secondary Checks

F9.1. Internal consistency checks of data

The different parameters in the AWS BUFR N-minute data report (N ≤ 10 minutes) are checked against each other. In the description below, the suggested checking algorithms have been divided into areas where the physical parameters are closely connected. The symbolic names of parameters with the corresponding BUFR descriptors used in the algorithms are explained in the table (Vendor may refer to the document on weather codes to be given separately).

(i) Wind direction and wind speed

The wind information is considered to be erroneous in the following cases:

• wind direction = 00 and wind speed ≠ 00;

• wind direction ≠ 00 and wind speed = 00;


• wind gust (speed) ≤ wind speed; (ii) Air temperature and dew point temperature

The temperature information is considered to be erroneous in the following case:

• dew point temperature > air temperature;

• air temperature - dew point temperature > 5°C and obscuration is from {1, 2, 3}; (iii) Dry temperature and present weather

Both elements are considered suspect when:

• air temperature > +5°C and precipitation type is from {6, ., 12};

• air temperature < -2°C and precipitation type is from {2};

• air temperature > +3°C and precipitation type is from {3};

• air temperature < -10°C and precipitation type is from {3};

• air temperature > +3°C and obscuration is from {2} or

• (obscuration is from {1} and character of obscuration is from {4}); (iv) Visibility and present weather

The values for visibility and weather are considered suspect when:

• obscuration is from {1, 2, 3} and visibility > 1 000 m;

• obscuration is from {7, 8, 9, 11, 12, 13} and visibility > 10 000 m;

• visibility < 1 000 m and obscuration is not from {1, 2, 3, 8, 9, 10, 11, 12, 13}

• and precipitation type is not from {1, . , 14};

• obscuration = 7 and visibility < 1 000 m;

• visibility > 10 000 m and precipitation type is missing and obscuration is missing and weather phenomenon is missing;

(v) Present weather and cloud information

Clouds and weather are considered suspect when:

• total cloud cover = 0 and precipitation type is from {1, ., 11, 13, 14}

• weather phenomenon is from {2, 5, . , 10}; (vi) Present weather and duration of precipitation

Present weather and duration of precipitation are considered suspect when:

• precipitation type is from {1, . , 10, 13, 14} and precipitation duration = 0;

• precipitation type is not from {1, . , 10, 13, 14} and precipitation duration > 0; (vii) Cloud information and precipitation information

Clouds and precipitation are considered suspect when:

• total cloud cover = 0 and amount of precipitation > 0; (viii) Duration of precipitation and other precipitation information

Precipitation data are considered suspect when:

• amount of precipitation > 0 and precipitation duration = 0;


(ix) Cloud information and sunshine duration

Clouds and sunshine duration are considered suspect when:

• total cloud cover = 100 and sunshine duration > 0;

If the value fails the internal consistency checks it should be correspondingly flagged as suspect or erroneous.

F10. Details on the System presently available at National Data Centre: The existing data base management system with in-built tools called CliSys is installed. It has data storage around a RDBMS with dynamic data structure based on an underlying data model. F 10.1. Hardware: The specification and details on the hardware / servers available in the existing System are given below in the Table.

Table 11. The Hardware details of CliSys

F10.2. Meta Data Scheme:

At NDC data are being stored using a Meta Data Scheme explained in the Fig. 6, where

in tables linking with different station parameters and the types of data generated over

various observatories / locations are kept. The data are retrieved along with the meta

data details. In the proposed system also, a similar met data scheme needs to be

present in order to store various types of data and to be made available along with these

whenever data are retrieved from the data base.


Fig. 6. Present Metadata Schema available at NDC

F11. DATA RECEPTION AND PROCESSING IN THE PROPOSED SYSTEM: The details mentioned in the preceding paragraphs may be kindly referred to enable the

required facilities in the proposed system sought to be developed. They may be

summarized in the Technical Requirements Section 4 of this Tender document.

F11.2. Quality Control Process in the proposed system: As discussed earlier in the paragraphs of F 7 to F 9, there are TWO stages of Quality

control checks required to be applied. The procedures should be for each and every type

of data and all the quality control applications should have (configurable) features and

provisions suitable for editions, additions, modifications, etc., for further aspects, if so

desired. These are detailed in Section 4 comprehensively. Same are explained in the

following paras:


F 11.2.1. Stage 1 Control Checks: Procedures may be accordingly set through software systems to be used for various

types of like Surface parameters (Temperature, rainfall, clouds, wind, etc.), , broadly may

consist:

o Syntax

o Duplicate

o Gross Limit Outliers

o Station Outliers

o Internal Consistencies

For upper air data in addition we may have,

o Lapse rate check for vertical Temperature profile

o Check for consistency between Standard and significant data

o Check Hydrostatic balance between standard level height and temperature

o Check for vertical wind sheer

F 11.2.2. Stage 2 Control Checks: In the extended or advanced level of control procedures, the following steps may be kept

in mind to be implemented:

Time Consistency – Check for the variation in the parameter value with the time

(hourly/daily)

o Deviation from climatological means

Spatial consistency – Check for changes spatially

o Display maps to visualize the spatial distribution

o Apply Interpolation techniques to see the variation

o Flag the doubtful values and generate the error message

Quality control flags

o assign to each parameter failing the checks listed

F 11.3. Meta Data Scheme (Data about Data) in the proposed system: As already explained in the paragraph F5 and F10 above, the following features need to

be made available in providing every type of data generated:


o Station Location – latitude, longitude, country, Met. sub-division, state,

district, exposure images etc.,

o Parameter specific details - frequency, type, limits of the parameter etc.,

o History of location and parameter

o WMO Information System (WIS) compliant. (http://www.wmo.int)

F11.4. Back-up Policy and Data Recovery System: The proposed system must have a suitable policy for transporting as Back-up /External

storage media procedures based on the following:

• Frequency of the data that are interrogated

• Health of the system hardware such as bad sectors, h/w issues, failures with

check for in-built solutions

• Aging of the data – which are older and lesser queried for retrieval, etc.,

• Scheduled / Automatic back-ups on to Off-line / external storage media

• Optional back-ups in case of emergency, etc.,

The vendor must propose a solution to meet with a proper Data Recovery (DR) System

considering the following minimum requirements

• To automate with the DR mechanism

• DR of all the data after carrying out the QC

• DR of Data along with the functionalities

• DR all Meta data with eligibility, authorizations for data access, etc.,

• To train the staff with technical process and imparting knowledge

• To ensure the down-time to be minimum

F 12. ARCHIVAL AND AVAILABILITY OF DATA CATALOGUES

There should be a suitable policy to be provided by the vendor for archiving the data after

the QA/QC procedures are applied and checked as quality data along with suitable link

table prepared. . The availability of such data archived and put into RDBMS needs to be

prepared as and when required or in a scheduled manner (daily basis). Suitable

catalogues need to be created along with the data availability tables/templates so as to


update the features required for the users for the retrieval or on-line data supply

purposes.

The availability of data along with its meta-information should be available in template

forms / catalogues which are user-friendly and be on active display (i.e. updated

dynamically) and to be used and interfaced with retrieval and on-line supply of data

management tools.

The inter-links are as per the latest available meta-data and with possibility of recovering

old meta-data details too.

F 13. MIGRATION OF DATA:

Once the functionalities, storage and data base integrated and established with all

features, all the historical data available in the existing storage need to be migrated after

proper testing and to the satisfaction of IMD. Vendors must complete this task along with

the other installation, implementation and integration of all components into the new

system.

F 14. RELATED HARDWARE AND SOFTWARE COMPONENTS: Vendor needs to examine the criticality of different components and requirements in the

light of scope of services and provide solutions. These would include Supply, Installation,

Acceptance Testing, Configuration, Commissioning, and Training of various equipments

and components (like Routers, Switches, Load Balancer, Bandwidth Optimizer, Storage

Area Network, Tape Library, SAN switch, SAN Management Software, Backup Software,

Firewall, IDS/IPS, High End Servers, Network Management Software, Enterprise

Management Software, Anti-Virus, Anti-SPAM, Anti-Spyware, Anti-Adware, Racks,

Network Cabling, etc,

END OF ANNEXURE F


ANNEXURE G DATA PRODUCTS GENERATION TOOLS

G 1. INTRODUCTION G 1.1 DATA RETRIEVAL IN THE EXISITING SYSTEM:

The meteorological data are used for lot of activities such as laying runways, town planning, air-conditioning, industry, port installations, installation of high towers, bridges and other structures, operation of multi-purpose hydel-projects, water and power management, environmental studies, non-conventional energy sources, etc.. Considering the increasing demands of climatological data in these fields of application, by research institutions, Private Sectors, Public undertakings Industries, etc., the data retrieval and supply at National Data Centre (NDC) are being done with some imitations. Handling of huge quantum of data for various data and desired and special product generations are generally consuming time and give rise to problems due to over-size of data. As per the departmental policy and without compromising the national interests, NDC supplies the basic data and products on electronic media as well as hardcopies, tailored to the users’ requirements to all the users community from Indian and foreign countries. Based on the statistics of last few years, annually, there are around 600 users and data of around 63 Billion records are being supplied from this centre. Depending on the query and requested data, basic data and their products are generated using the software (Fortran and C) programming till recently. Later when NDC has been equipped under CliSys System under modernisation, specialised tools in built were used to get some standard products such as Wind Roses, Bar charts, contour maps, etc., However, there are some features still required in fine tuning to the desired products. In the proposed system sought to be developed the process of data and products generation must conform to already existing techniques and in addition to have utilities user friendly for extraction of data, visualisation and generation of products along with advanced analytics. G2. Requirements of Tools The requirements for the basic data and products are many, such as, climatology, data analysis and interpretations and predictions or simulation studies, to mention a few. The climatological data is useful for making inferences towards past, present and futuristic extensions. The data analytics on the data help making some value additions for which many tools like data visualization, Geo Information System (GIS) as basic layered information and graphical user interface (GUI) solutions are required to be integrated in the Data Production tool. Although standard statistics tools are required for deriving any mean, average, standard deviation, variation, etc., some advanced level features would also be needed. In fact such analysis will help in transforming the data into much useful information as value additions. G3. CLIMATOLOGICAL DATA:


The climatological data can be derived generally from the basic parameters from any particular type of data, like, surface, upper-air, radiation, etc., However, for deriving the climatology, there are standard procedures and guidelines given by World Meteorological Organisation (WMO) are available (WMO, Tech. note) and being followed by NDC. There is some standard period of years for making the climatology as per the guidelines. This type of normal is used by the National Met. Services (NMS) and shared for WMO purposes. Further there are additional requirements such as extremes, anomalies, deviations with desired percentiles, annual Climatological Summary, etc., for the operational units of NMS. Now a days, the averages with respect to time (monthly, seasonal, annual, decadal, etc.,) and area specific (Area weighted rainfall, district, state and sub-divisional, homogeneous regions and country as a whole rainfall) are the general but national demands due to expanded forecast practices. Similarly, users are also in need of short period averages such as 10 years or 5 years or for the desired period of years. Thus, there are two types of requirements of Climatological Normal

(i) Standard and Scheduled type of Climatological Normal generation needs to be automatically consider the period and scheduled and give alerts for data assimilation

(ii) Desired / Optional normal generation – as and when in demand by user as special request or application

G 4. RETRIEVING FACILITIES IN THE PROPOSED SYSTEM: In the recent years, there has been a steep increase in the users’ numbers and their variety of requirements. In the absence of proper and essential tools in the present system, the data products could not be generated or if generated there are limitations and with consumption of time and hence sometimes such products are not provided to them. Due to this, even departmental users are being left with no other option than to manually interpret carrying lot of errors in the results or interpretations. The advantage with the enhanced capabilities in the Climate Data Centre activities sought to be developed must help sorting the problems of handling huge data, visualization, analytical tools, etc., Hence, it is suggested to have the retrieval with following general features:

o SQL program and query based o User- Interface through a template / catalogue (refer to F 12) o Options for user choosing / selecting using Dialog enabled

▪ Location (s), Table (list) of stations or Area (map based), drop-down menu ▪ Zoom out / in for maps, visualization enabled selections ▪ Type of Data (automatic pop-ups for next selection) ▪ Parameter (s) ▪ Period (From and to year/month/ date/hours) ▪ Special requirements (Extremes, threshold, check-values) ▪ Analysis requirements (statistical, graph Plots, GIS, etc.,) ▪ Output formats (select from text, excel, html, etc.,)


▪ Enable Verification / confirmation once selection is over

o Administration of retrieval functions to generate ▪ Log reports of users ▪ Data retrieved, products, etc., ▪ authorizations and privileges for various user’s levels ▪ Policy on Restrictions on data size, types, tools, etc., ▪ Retrievals / Extractions by Data processing on delayed (non real-time) data ▪ Catalogue based search and selections through above stated options

o Auto Reports / generations of

▪ Standard Table form Climate Normals (for various parameters) ▪ Hourly to daily ▪ Daily to weekly ▪ Daily to monthly ▪ Scheduled Monthly /Annual Summary (Map and Table form) ▪ Table Form (event reporting such as occurrences and their frequencies) ▪ Wind roses along with Table (scheduled / optional) ▪ State level / District level / Taluka level / station level (optional) ▪ Graphical / bar charts / tables (whenever desired/optional) ▪ Maps at different levels (state/Met. sub-divisions/districts/taluka/station) to

be from those approved by Survey of India ▪ Any display/table contents required for departmental site / remote users

G 5. APPLICATION TOOLS FOR DATA PRODUCTION:

The use of data in various applications can be enhanced if appropriate tools for data analyses are available in the data production system. It will be helpful to all the users community be it research or operational or even a commercial user. In the present system no tools are directly available in order to process / apply various statistical analyses on the data. The following are some climate data products that would be required in the proposed system.

Table 12 . Details of Climate Data Products

Sr. No.

Input Data

Product Name

Description Frequency Format Infrastructu

re Target Users

Modes of Publication

1. Rainfall Gridded Data

1°X1° (1951-2012), 0.5° X 0.5°(1971-2005), 0.25° X 0.25° (1901-2013)

Yearly Binary Workstations, Internet and various softwares (MS Office)

Operational Services, researchers in climate science and allied subjects

2. Surface Climatological Summaries

State and District Climatological summaries of the states in

Once data sets are ready

Text, Tables, Self-explana-tory

WorkstationDesktop Computers, Internet,MS Office

District gazetteers units for different states,Govt

Hard copy and soft copy


India Maps Tools,Fortran,Surfer,Coral Draw, Photoshop, Adobe Acrobat (Reader + Writer)

Organisations, various sectors like Agriculture,aviation,power and energy,tourism,shipping,transport etc. Educational institutes

3. Surface (Monthly)

Summary State Climate Summary, Aeronautical Climatological Summary

6 5 years (ACS)

Text, Tables

MS office tools

HQ, Aviation section, private parties, NCDC USA

4. RS/RW data (Monthly CLIMAT temp)

Atlas and normals

Climatological Atlas, CLIMAT (temp), RS/RW normals

10 years

Tables, Contours Maps, Text

- “ -

5. Agrimet data Daily / Weekly

Maps Aridity and Outlook maps

Weekly, Biweekly and Monthly

Text and Display

Fortran software of preparation of Aridity Indices, Grads software for preparation of Maps

DGM, IITM, Ministry of Agriculture and Agrimet Division of AAS

6. Rainfall Daily

SPI maps,

atlas

Cumulative

standardized

precipitation

index maps

(SPI), rainfall

data series

CD ROM,

Rainfall atlas

of India,

Rainfall

normal and %

departure

Weekly,

monthly,

seasonal

and

annual

Excel,

Text

Fortran, surfer, coral draw and Photoshop, VB

7. Extended Range Weather Forecast

Climate

Information

for Health

Temporal

evolution of

spatial

distribution of

transmission

window for

vector borne

disease,

based on

extended

range

weather

forecast

Weekly Text and

Self

explanato

ry Maps

(bulletin)

Desktop computers, internet, MS office tools

Govt. Health

organizations,

local self

Govt.

Authorities

Weekly Bulletin (Experimental Basis)


8. Regional Climate Products - Climate prediction

a. Observe

d Data

SST,

OLR,

MJO

propagati

on, Snow

Cover &

MMCFS

Forecast

Data

(Precipita

tion,

Temperat

ure, SST)

Seasonal

Climate

Outlook for

South Asia

Observed

Global

climate

conditions

(SST, OLR,

snow cover,

MJO activity,

Nino Indices,

DMI, etc)

along with

Forecast

Outlook for

South Asian

region on

Spatial &

Temporal

Scales

(Precipitation,

Temperature)

Monthly PDF (Text & Tables &Maps)

MS Office,

HPCS,

Internet

Facility,

Software

like Ferret,

NCL,

Grads, etc

Operational

services from

RA II Region

(South Asian

Countries),

Researchers

and Users

from Climate

Science and

forecasting

community

Website

b. Observed

Data SST

&MMCFS

Forecast

Data

(SST)

ENSO Bulletin Observed

global oceanic

conditions ,

ENSO

conditions, IOD

condition &

spatial SST

anomaly

forecast for

global region,

plume and

probability

forecast for

ENSO and IOD

Monthly PDF

(Text

&Maps)

MS Office,

HPCS,

Internet

Facility,

Software

like Ferret,

NCL,

Grads, etc

Operational

services

(Government

Sectors) within

and outside of

India (as per

their

requirements),

Researchers

and Users from

various

subjects

Website

c MMCFS Forecast Data (Temp- erature )

Seasonal

Outlook for

Temperature

Spatial

temperature

anomaly

forecast for

subdivisions of

India

Monthly PDF (Text & Maps

MS Office,

HPCS,

Internet

Facility,

Software

like NCL,

Grads, etc

Operational

services

(Government

Sectors) within

and outside of

India (as per

their

requirements),

Researchers

and Users from

various

subjects

Website

d Observed

Data for

Rainfall,

Temperatu

re, OLR,

Velocity

Potential &

Climate

Diagnostic

Bulletin of

India

Summary of

Observed

climate

conditions for

India like

Rainfall,

Temperature,

Monthly PDF and

Hard copy

(Text-

Tables

&Maps,

ContourPlo

MS Office,

Internet

Facility,

Software

like Grads,

g77 Fortran

Operational

services

(Government

Sectors) within

and outside of

India (as per

their

Website,

Hard Copy


Streamfun

ction, Low

pressure

systems,

significant

weather

events,

SPI, SST

&MMCFS

Forecast

Data

OLR, Velocity

Potential &

Stream

function, Heat

& Cold Wave

Status, Warm &

Cold Nights

Status, Low

pressure

systems,

significant

weather events,

SPI & Global

Oceanic

Conditions,

ENSO Outlook

ts)

etc

requirements),

Researchers

and Users from

various

subjects

e Observed

Data for

Rainfall,

Temperatu

re, OLR,

Velocity

Potential &

Stream

function,

Low

pressure

systems,

significant

weather

events,

SPI & SST

Annual

Climate

Summary of

India

Summary of

Observed

climate

conditions for

India for all the

seasons like

Rainfall,

Temperature,

OLR, Velocity

Potential &

Stream

function, Heat

& Cold Wave

Status, Warm &

Cold Nights

Status, Low

pressure

systems,

significant

weather events,

SPI & Global

Oceanic

Conditions

Yearly PDF and

Hard copy

(Text-

Tables

&Maps,

ContourPlo

ts)

MS Office,

Internet

Facility,

Software

like Grads,

g77 Fortran

etc

Operational

services

(Government

Sectors) within

and outside of

India (as per

their

requirements),

Researchers

and Users from

various

subjects

Website,

Hard Copy

f MMCFS

Post

processed

Data

(Precipitati

on & SST)

SASCOF

Forecast

Outlook /

Consensus

Statement

Rainfall

forecast outlook

for all South

Asian countries

and review of

global

atmospheric

(MJO, SOI) and

oceanic

(ENSO,

IOD)conditions

Six Monthly PDF (Text

& Tables

&Maps)

MS Office,

HPCS,

Internet

Facility,

Software-

Ferret,

Grads, etc

Operational

services from

RA II Region

(South Asian

Countries),

Researchers

and Users from

various

subjects and

forecasting

community

Website,

Press

g Mean Sea Level Pressure, Temperature , Rainfall, Mean

Climate Moni-

toring

Products

Observed

climate

(atmospheric

as well as

oceanic)

conditions for

Monthly Maps MS Office,

HPCS,

Internet

Facility,

Software

like Ferret,

Researchers

and Users from

Climate

Science and

allied subjects

Website

Display


Wind, Velocity Potential, Stream Function, OLR Anomaly, ENSO Indices - Nino 1 + 2, Nino 3.4, Nino 3, Nino 4, Indian Ocean Dipole

previous month

(updated as per

available of

observed

monthly data)

NCL,

Grads, etc

h MMCFS

Post

processed

Data

(Precipitati

on & SST)

SASCOF

Forecast

Outlook /

Consensus

Statement

Rainfall

forecast outlook

for all South

Asian countries

and review of

global

atmospheric

(MJO, SOI) and

oceanic

(ENSO,

IOD)conditions

Six Monthly PDF (Text

& Tables

&Maps)

MS Office,

HPCS,

Internet

Facility,

Software-

Ferret,

Grads, etc

Operational

services from

RA II Region

(South Asian

Countries),

Researchers

and Users from

various

subjects and

forecasting

community

Website,

Press

i Mean Sea Level Pressure, Temperature , Rainfall, Mean Wind, Velocity Potential, Stream Function, OLR Anomaly, ENSO Indices - Nino 1 + 2, Nino 3.4, Nino 3, Nino 4, Indian Ocean Dipole

Climate Moni-toring Products

Observed climate (atmospheric as well as oceanic) conditions for previous month (updated as per available of observed monthly data)

Monthly Maps MS Office, HPCS, Internet Facility, Software like Ferret, NCL, Grads, etc

Researchers and Users from Climate Science and allied subjects

Website Display

9. Extended Ranger Weather Forecast

Climate Prediction

Apart from the above climate products, real-time maps / charts along with statistics of various synoptic events as mentioned below are useful for the forecasting / research community:

• Real-time threshold maps

• On-line charts for display

• Climatology maps / table - monthly climatology of all stations (parameter based)


• Forecast model outputs overlayed cloud imagery

• Statistics on Oceanic systems through links

• Windrose Diagrams / mixing heights

• Monthly, ozone / radiation data station based

• E-commercialization with meta data

• Extreme events (latest 10 years)

• Trends / Averages / Extremes with ± 5 days values (parameter wise)

• Cold wave / Heat wave

• Current weather data along with pressure / temperature departures (based on climatological tables)

• Preparation of tools for charts/ maps / reports for different scales of climate prediction (short, medium, long range and extended )

• Program/software based tools with customization for plotting and contour analysis

STANDARD TOOLS: Vendor may develop the applications / tools / utilities as part of retrieval and data product generation system using any standard or specialized available software package or using open-source tools combined with any standard software for providing the requirements as mentioned below.

o Standard Statistical Tools

▪ elementary statistics (Mean, Mode, Median, Variances, Kurtosis, skewness, etc.,)

▪ Time series Analysis and testing techniques ▪ Analysis on discrete and continuous data sets ▪ Functional / Frequency curve plots ▪ Sigma and Box plots ▪ Scatter diagram ▪ Regression and correlations ▪ Interpolations ▪ Multi-dimensional and Multi-variable analysis (Principal Component

Analysis, Factor analysis, Cluster analysis, canonical mapping, etc.,) ▪ Data normalization, homogenization ▪ Missing value techniques/smoothening etc., ▪ Probability of Maximum values (like PMP, Assured Max. rainfall, etc.)

o data mining tools (data miner, pattern recognition, analytics, etc., ) o Return period evaluation analysis o GIS base map for India with different types of networks / locations based on area

levels of states/met. Sub- divisions,/districts/taluka/stations o Enable different layers


o Gridding the data using interpolation (specific type desired/default)

The software / utilities / tools to be designed by the vendor for the applications mentioned above should support all kinds of extraction / retrieval of all the basic data and products from the data base. G 6. SCOPE OF ADVANCED AND ADDITIONAL TOOLS / UTILITIES: As indicated earlier, the tools stated in G 4 are not the exhaustive list. The Climate Data Centre sought to be developed must be a model and state-of-art data centre and hence vendors are advised to implement advanced and specialized tools being used for various applications in the sites of data centres of international repute. In order to provide suitable software or application tools, vendors may kindly check and refer to the climate data utility and services of some standard meteorological sites. http://www.esrl.noaa.gov;

http://www.wmo.int;

http://www.kma.go.kr;

www.ncdc.noaa.gov;

www.jma.go.jp

Some application based climate products can be also seen at the following sites:

http://www.ecad.eu/indicesextremes/customquerytimeseriesplots.php

www.esrl.noaa.gov/psd/data

END OF ANNEXURE G

http://www.esrl.noaa.govl/

http://www.wmo.int/

http://www.kma.go.kr/

http://www.ncdc.noaa.gov/

http://www.jma.go.jp/


http://www.esrl.noaa.gov/psd/data


ANNEXURE - H

ON-LINE DATA SUPPLY AND COMMERCIALISATION FEATURES

H1. INTRODUCTION:

H1.1. EXISTING DATA SUPPLY PROCEDURE:

India Meteorological Department (IMD) since established has a large network of observatories for monitoring the weather and National Meteorological and Hydrological Services (NMHS). The department has been collecting systematically the observations from remote field locations and they are meticulously archived after quality control programmes in the data base in Relational Data Base System (RDBMS) format at a central location National Data Centre (NDC), Pune. There are about 15 types of data / met. Parameters like Surface, rainfall, autographic, upper-air data, radiation data, air-pollution data, etc., A robust relational data base management system called CliSys has been installed at NDC and the activities of data acquisition both real-time data such as automatic weather stations (AWS) and non-real time delayed data ingested into the system. The system contains built-in processing control system and archives in the relational data base (Oracle 10). As of now climate data and products including images ( jpeg and gif ) to the tune of 20 TB are available in the archives in the digital formats. It is expected to grow in size. Based on the users’ requests, various type of basic data and derived products, data are retrieved and supplied. The data requirements once received from the party are classified as (i) free-supply, (ii) concessional or (iii) commercial categories and they are manually registered / entered and processed for the supply of data after providing the necessary details of availability of data, period and their fields, etc., along with the cost for the data and procedure for the procurement. Later the users are informed depending upon their categories for the next course of action. Free supply of data is generally made for those users from IMD and other institutions under MoES and those under Memorandum of Understanding (MOU) on some project mode. The concessions (of 95% on data cost) are applicable to those research and educational institutions. The commercial and concessional categories, the cost of the data are levied as per the departmental policy provided in the guidelines. In the present practice, the requests are being received in all the forms including POST, FAX and e-mail, and manual intervention is at every stage right from registration, making the request in standard form and sending for retrieval system, data dispatch, details of revenue entries, calculation of monthly accumulated service Tax dues, generating related reports, data users list, etc.,. Therefore, the complete process is required to be automated as an end-to-end. This will also ease out the tedious works manually being done that consumes a considerable amount of time. Towards this, a Data supply Management System needs to be developed which forms as part of scope of services in this Request For Proposal.

H 2. REQUIREMENTS OF COMPONENTS IN THE PROPOSED SYSTEM: The flow chart presented in Fig. 7 gives various stages of the existing activities involved in the data enquiry and supply services at NDC. Due to more manual and routine type of activities involved in the data enquiry and supply, delays in services, at times, become inevitable. The climate data centre sought to be developed has a component of developing and implementing an on-line supply management and commercialization


system to enable the systematically and automatically handled with minimal manual intervention, if at all. H 2.1. General Requirements A based on-line Data Supply Management System (DSMS) needs to be developed with all utilities and interfaces would be required in order to facilitate the following modules. The following are only suggestive and indicative but not exhaustive requirements and hence vendor needs to understand the full scope for implementation. H 2.1.1. Software Modules: Following software modules would be required for specific purposes as indicated below

a) NEW USER REGISTRATION MODULE: The new user registration (LOGIN) needs to be created for any user with usual practice and the details for monitoring the users’ details, frequency of use and by maintaining their login usages/visit to the portal.


Fig. 7. Flow chart of Data supply Management

• Create a database of the New Users/Institutions comprising, of following items. i. Date of Registration. ii. Enrolment of Institution with IMD iii. Name, Address, Contact Information iv. Type of user category v. Management details etc.

• The system shall have the provision to add, modify and delete the User registration information.

b) DATA REQUEST MODULE: Data Request Module should capture all the new data requests from the user. All the new data requests should include user friendly Graphic User interface / dialog box, templates or the catalogues, drop down input, pop-ups facilities enabled automatically.

• Type of data required

• The frequency of data

• Region for which data is requested

• Request Period

• Output File type & format (default if no standard option provided)

• Address where data to be supplied (E mail or default location)

• Verify / Confirm the request is complete

• Understand category (concessional / commercial)

• Estimate the cost based on the type and no. of parameter/values (following departmental policy)

• Connect to payment module / Payment gateway

It may be noted that while preparing this module the requirements under Annexure G may be referred by the vendor as they need to be similar.

c) REQUEST STATUS MODULE: The purpose of this module is to inform the user the details with regard to

i. status of each request to the user and the respective departments. ii. track details the current status of the data request. iii. Work-flow should be in place so that a request from one department

can pass to request to other department. iv. number of requests pending in their bucket v. keep alerts in case of pending request vi. to keep update and update with every other module related to data

supply and data requests and status in particular


d) REPORT MODULE: This module should produce different reports automatically get generated

i. Details about the number of data requests for a specific period. ii. Scheduled reports as may be necessary with regard to

• Data Users

• Data supplied

• Weekly, monthly, Revenue Statements

• Taxes to be paid (to Service Tax dept.)

e) PAYMENT MODULE:

The payment module must automatically generate the following list.

• Ensure the Selection of the requirements by the users is complete

• Proceed to Payment Gateway (standard and reliable) preferably SBI

• On-line Payment details (instructions) step-by-step

• Mode of payment options (net-banking / credit/ debit cards) process

• Successful Return (attempts)

• Alerts in case of failures

• Proceed for Retrieval and Supply process

• Alert for logs for revenue report generation H 2.1.2. SOFTWARE CUSTOMISATION AND CONFIGURATION:

The -portal needs to meet the entire specified process requirements of on-line

payment to IMD and on-line supply of data to users by the desired means. It would be the responsibility of the Vendor to prepare Status Reports (SR) catering to the entire functional specifications required of each module; the specifications enclosed are indicative and broad in nature. The same may/may not include the entire process to be taken care of at the time of implementation. It is expected to absorb all such processes / functionalities which may or may not be explicitly brought out in the annexed specifications. H 3. Nature of activities to be carried out by Vendor: In order to effectively develop and implement the on-line Supply Data Management System, vendor needs to carry out the following activities and ascertain the requirements.

i. Need to understand current commercialisation processes of IMD. ii. Provide best solution and software to effect best practices in the existing

processes; iii. Identify areas of differences between the best practices and the current

business processes of IMD including redundancies & duplications in its current business process and take efforts to streamline the ‘best’ practice.

iv. Design all desired access security and data validation controls; v. Document the configuration done and prepare user manuals for

maintenance of the configuration / customization and training documentation


H 4. IMPLEMENTATION / INSTALLATION: This is also applicable to all the development tools, utilities and applications which are mentioned as requirements and scope detailed in the Request for Proposal. However, for online supply data management System the implementation and installation of applications, utilities to be developed are discussed below. The vendor remains fully responsible for the roll out of all applications at NDC. The actual go-live phase for the package implementation will cover the following activities:

i. Carrying out the final testing of the configured software and obtaining the user and IT level sign-offs. This will include documentation of the testing procedures and results obtained.

ii. Transferring the duly tested configuration to the production environment. iii. Populating the master records, as appropriate iv. Installation of the software and handing over of related documentation and

media to IMD. v. Assist in clearing the initial transactions. vi. Development of the necessary Reports – generation of these reports for the

month / quarter which will be duly approved by the client; vii. Implement all designed access security and data validation controls viii. Implementation vendor would provide all the necessary

manuals/Documentations which must include following minimum documents:

a. User Manuals; Programmer’s Manual, Operator’s, Design document, SRs.

b. Error messages, meanings, troubleshoots and solutions ; c. Training Manuals/materials; d. Configuration Manuals with the relevant data flow diagram, entity

relationship diagrams, schemas etc; e. Additions / Changes to the documents after the upgrades;

H5. HANDHOLDING SUPPORT RESOURCES:

The details of the Role and Responsibilities of Handholding Support Resources are indicated below:

1. To provide all the necessary help/guidance to users in understanding and operating the system.

2. Help/operational troubleshoot for day to day operations in the software a. Software Local data backup. b. Operations approval appraisals to/from state offices. c. Necessary Masters Updation /modifications requests in central server / local

server. 3. Software Installations (if any as required)/Virus updation. 4. On-line context-based help facilities at field level and also online help at function

screen and field level. 5. Co-ordination and support between H/w, S/w support calls.


6. Assist in Internet operations – Mailing/FTP (upload/download (if any) etc.,

H6. BASIC APPLICATION ARCHITECTURE:

The Online Data Supply Management will be basically a single unified information system totally integrated with IMD data base. The portal will be, essentially characterized by the following features:

a. Modularity: The system will initially be required to cover a range of modules, but it should allow addition of more modules or more users in any module as and when required, which should seamlessly integrate into the core system.

b. Flexibility: The system should support customization to IMD’s requirements and should be adaptable to changing practices.

c. Open Architecture: The system should be open to allow interoperability with general-purpose software and have the facility to export/ import data files from other applications.

d. Integration: The system should be fully integrated across modules and functional areas and also across geographical location of sites. It should have the ability to assign validation on specific fields based on entries in the data validation reference file. It should be fully compatible for data exchange with legacy systems & other systems.

e. Workflow integration approach: The system should support workflow to automatically raise alerts, messaging etc. across functional areas/modules.

f. Internet and Intranet enabled: The system should be able to function in Internet, Intranet and . Client server architecture at the Institutional level and Browser based/-services above the level of Institutions with capability of batch processing for data porting.

g. Scalability: Scalability (i) in terms of the volumes of transactions handled: This provides the facility to enhance software capacities to maintain the performance levels and (ii) in terms of integration with existing software: This provides seamless integration with heterogeneous systems at the backend with ease of deployment of the applications and services.

H 7. SECURITIES: The system must have proper security and maintenance facility which limited access to the system and its various functions to the users delegated with appropriate authority.

• Access to modules / functions within modules restricted to authorized users

• It should provide logging by user and terminal, the date and time of all transactions with details of creation, reading, updating, deletion or printing.

• Access should be restricted to different levels as program, module, transaction, etc.

• Set up user access, according to user defined rank, etc.

• Control on scope of activity of each user (data file, program, module, screen, data table, record, field, etc.)


• Notify security administrator of unauthorized access or attempted access and record in a log with reporting

• Multi-level security system at operator, supervisors, module owners, administrator level

H 8. SYSTEM CONTROL AND AUDIT: The system should be able to define audit trails, audit logs and transaction logging requirements (what, when, who has changed). It should enable audit trails on-line, tailor audit requirements by modules, call audit records to an archive based on date or other recorded audit details. The system should allow recovery of data in case of hardware failure and data corruption. It should be able to perform recovery (DR) to a point of time, to known backup database. H 9. USER INTERFACE: The user interfaces should be friendly and GUI/browser based. There should be sufficient edit and validation checks in the system. It should provide safeguards to prevent damage to data from operator errors, simultaneous updates, module unavailability or system failures. It should have facility to display confirmation / warning windows for deletes changes etc. H10. CLIMATE SERVICES INFORMATION TO REMOTE USERS: H10.1.The portal (Gateway) needs to be developed in which all kinds of users need to be provided with application tools based on the user and privileges. However, for a remote user following features may be enabled. In this connection vendor may refer the scope of works partly similar to those indicated under Retrieval and application tools at technical specifications at Section 4 as well as G 4 and G 5 in the Annexure G and points under software module specified under H 2.1.1.

• LOGIN registration

• Accessibility with authorizations

• Maps / Data (Limited to size or period) view/display or obtain data

• Application (Elementary Statistical ) tools for use

• Averages (mean), extremes (standard products)

• Standard Normal (Climatology)

• Forecasts (links)

• Trigger for catalogues table (updates) / links of different institutes of MoES

• Links to other data bases / or climate products

• Interface with latest mobile technology (platform independent)

H10.2. Vendors may kindly refer to the sites of the following institutes under MoES for setting up the links and feasibility for the tasks in this regard: IMD : www.imd.gov.in

http://www.imd.gov.in/


NCMWRF : www.ncmrwf.gov.in IITM : www.tropmet.res.in INCOIS : www.incois.gov.in NCPOR : www.ncaor.gov.in / www.npdc.ncaor.gov.in; NIOT : www.niot.res.in H10.3. The standard Climate products and other derivates from the above MoES sites are required to be catalogued and made under climate services along with the links for view and display. H 10.4. Climate services provided through different data centres for reference are given below:

www.cpc.ncep.noaa.gov/products www.esl.noaa.gov/psd/data http://www.ecad.eu/indicesextremes/customquerytimeseriesplots.php

END OF ANNEXURE H

http://www.ncmrwf.gov.in/

http://www.tropmet.res.in/

http://www.incois.gov.in/

http://www.ncaor.gov.in/

http://www.npdc.ncaor.gov.in/

http://www.niot.res.in/

http://www.cpc.ncep.noaa.gov/products

http://www.esl.noaa.gov/psd/data



ANNEXURE ‘I’

PRE CONTRACT INTEGRITY PACT

General

This pre-bid pre-contract Agreement (hereinafter called the Integrity Pact) is made on_______ day of the month of________ 2019, between, on one hand, the President of India acting through Shri................, Designation of the officer, Ministry/Department, Government of India (hereinafter called the "BUYER", which expression shall mean and include, unless the context otherwise requires, his successors in office and assigns) of the First Part and M/s_______represented by Shri_____, Chief Executive Officer (hereinafter called the "BIDDER/Seller" which expression shall mean and include, unless the context otherwise requires, his successors and permitted assigns) of the Second Part.

WHEREAS the BUYER proposes to procure (Name of the Stores/Equipment/ltem) and the BIDDER/Seller is willing to offer/has offered the stores and

WHEREAS the BIDDER is a private company/public company/Government undertaking/partnership/registered export agency, constituted in accordance with the relevant law in the matter and the BUYER is a Ministry/Department of the Government of India/PSU performing its functions on behalf of the President of India. NOW, THEREFORE,

To avoid all forms of corruption by following a system that is fair, transparent and free from any influence/prejudiced dealings prior to, during and subsequent to the currency of the contract to be entered into with a view to : Enabling the BUYER to obtain the desired said stores/equipment at a competitive price in conformity with the defined specifications by avoiding the high cost and the distortionary impact of corruption on public procurement, and Enabling BIDDERs to abstain from bribing or indulging in any corrupt practice in order to secure the contract by providing assurance to them that their competitors will also abstain from bribing and other corrupt practices and the BUYER will commit to prevent corruption, in any form, by its officials by following transparent procedures.

The parties hereto hereby agree to enter into this Integrity Pact and agree as follows: Commitments of the BUYER

1.1 The BUYER undertakes that no official of the BUYER, connected directly or indirectly with the

contract, will demand, take a promise for or accept, directly or through intermediaries, any bribe, consideration, gift, reward, favour or any material or immaterial benefit or any other advantage from the BIDDER, either for themselves or for any person, organisation or third party related to the contract in exchange for an advantage in the bidding process, bid evaluation, contracting or implementation process related to the contract.

1.2 The BUYER will, during the pre-contract stage, treat all BIDDERs alike, and will provide to all

BIDDERs the same information and will not provide any such information to any particular BIDDER which could afford an advantage to that particular BIDDER in comparison to other BIDDERs.

1.3 All the officials of the BUYER will report to the appropriate Government office any attempted or

completed breaches of the above commitments as well as any substantial suspicion of such a breach.

2. In case any such preceding misconduct on the part of such official(s) is reported by the BIDDER to the


BUYER with full and verifiable facts and the same is prima facie found to be correct by the BUYER, necessary disciplinary proceedings, or any other action as deemed fit, including criminal proceedings may be initiated by the BUYER and such a person shall be debarred from further dealings related to the contract process. In such a case while an enquiry is being conducted by the BUYER the proceedings under the contract would not be stalled.

Commitments of BIDDERs

3. The BIDDER commits itself to take all measures necessary to prevent corrupt practices, unfair means and

illegal activities during any stage of its bid or during any pre-contract or post-contract stage in order to secure the contract or in furtherance to secure it and in particular commit itself to the following:

3.1 The BIDDER will not offer, directly or through intermediaries, any bribe, gift, consideration, reward,

favour, any material or immaterial benefit or other advantage, commission, fees, brokerage or inducement to any official of the BUYER, connected directly or indirectly with the bidding process, or to any person, organisation or third party related to the contract in exchange for any advantage in the bidding, evaluation, contracting and implementation of the contract.

3.2 The BIDDER further undertakes that it has not given, offered or promised to give, directly or

indirectly any bribe, gift, consideration, reward, favour, any material or immaterial benefit or other advantage, commission, fees, brokerage or inducement to any official of the BUYER or otherwise in procuring the Contract or forbearing to do or having done any act in relation to the obtaining or execution of the contract or any other contract with the Government for showing or forbearing to show favour or disfavour to any person in relation to the contract or any other contract with the Government.

3.3 BIDDERS shall disclose the name and address of agents and representatives and Indian BIDDERS

shall disclose their foreign principals or associates

3.4* BIDDERs shall disclose the payments to be made by them to agents/brokers or any other intermediary, in connection with this bid/contract.

3.5* The BIDDER further confirms and declares to the BUYER that the BIDDER is the original

manufacturer/integrator/authorised government sponsored export entity of the defence stores and has not engaged any individual or firm or company whether Indian or foreign to intercede, facilitate or in any way to recommend to the BUYER or any of its functionaries, whether officially or unofficially to the award of the contract to the BIDDER, nor has any amount been paid, promised or intended to be paid to any such individual, firm or company in respect of any such intercession, facilitation or recommendation.

3.6 The BIDDER, either while presenting the bid or during pre-contract negotiations or before signing

the contract, shall disclose any payments he has made, is committed to or intends to make to officials of the BUYER or their family members, agents, brokers or any other intermediaries in connection with the contract and the details of services agreed upon for such payments.

3.7 The BIDDER will not collude with other parties interested in the contract to impair the transparency,

fairness and progress of the bidding process, bid evaluation, contracting and implementation of the contract.

3.8 The BIDDER will not accept any advantage in exchange for any corrupt practice, unfair means and

illegal activities.

3.9 The BIDDER shall not use improperly, for purposes of competition or personal gain, or pass on to others, any information provided by the BUYER as part of the business relationship, regarding


plans, technical proposals and business details, including information contained in any electronic data carrier. The BIDDER also undertakes to exercise due and adequate care lest any such information is divulged.

3.10 The BIDDER commits to refrain from giving any complaint directly or through any other manner

without supporting it with full and verifiable facts.

3.11 The BIDDER shall not instigate or cause to instigate any third person to commit any of the actions mentioned above.

3.12 If the BIDDER or any employee of the BIDDER or any person acting on behalf of the BIDDER,

either directly or indirectly, is a relative of any of the officers of the BUYER, or alternatively, if any relative of an officer of the BUYER has financial interest/stake in the BIDDER's firm, the same shall be disclosed by the BIDDER at the time of filing of tender.

The term 'relative' for this purpose would be as defined in Section 6 of the Companies Act 1956.

3.13 The BIDDER shall not lend to or borrow any money from or enter into any monetary dealings or transactions, directly or indirectly, with any employee of the BUYER.

4. Previous Transgression

4.1 The BIDDER declares that no previous transgression occurred in the last three years immediately

before signing of this Integrity Pact, with any other company in any country in respect of any corrupt practices envisaged hereunder or with any Public Sector Enterprise in India or any Government Department in India that could justify BIDDER's exclusion from the tender process.

4.2 The BIDDER agrees that if it makes incorrect statement on this subject, BIDDER can be

disqualified from the tender process or the contract, if already awarded, can be terminated for such reason.

5. Earnest Money (Security Deposit)

5.1 While submitting commercial bid, the BIDDER shall deposit an amount of Rs. 10 lakhs) as Earnest

Money/Security Deposit, with the BUYER through any of the following instruments:

(i) Bank Draft or a Pay Order in favour of _________________ (ii) A confirmed guarantee by an Indian Nationalised Bank, promising payment of the

guaranteed sum to the BUYER on demand within three working days without any demur whatsoever and without seeking any reasons whatsoever. The demand for payment by the BUYER shall be treated as conclusive proof of payment.

(iii) Any other mode or through any other instrument.

5.2 The Earnest Money/Security Deposit shall be valid up to a period of five years or the complete conclusion of the contractual obligations to the complete satisfaction of both the BIDDER and the BUYER, including warranty period, whichever is later.

5.3 In case of the successful BIDDER a clause would also be incorporated in the Article pertaining to

Performance Bond in the Purchase Contract that the provisions of Sanctions for Violation shall be applicable for forfeiture of Performance Bond in case of a decision by the BUYER to forfeit the same without assigning any reason for imposing sanction for violation of this Pact.

5.4 No interest shall be payable by the BUYER to the BIDDER on Earnest Money/Security Deposit for

the period of its currency.


6. Sanctions for Violations

6.1 Any breach of the aforesaid provisions by the BIDDER or anyone employed by it or acting on its

behalf (whether with or without the knowledge of the BIDDER) shall entitle the BUYER to take all or

any one of the following actions, wherever required:

(i) To immediately call off the pre contract negotiations without assigning any reason or giving any

compensation to the BIDDER. However, the proceedings with the other BIDDER(s) would continue.

(ii) The Earnest Money Deposit (in pre-contract stage) and/or Security Deposit/Performance Bond

(after the contract is signed) shall stand forfeited either fully or partially, as decided by the BUYER

and the BUYER shall not be required to assign any reason therefore.

(iii) To immediately cancel the contract, if already signed, without giving any compensation to the

BIDDER.

(iv) To recover all sums already paid by the BUYER, and in case of an Indian BIDDER with interest

thereon at 2% higher than the prevailing Prime Lending Rate of State Bank of India, while in case

of a BIDDER from a country other than India with interest thereon at 2% higher than the UBOR. If

any outstanding payment is due to the BIDDER from the BUYER in connection with any other

contract for any other stores, such outstanding payment could also be utilised to recover the

aforesaid sum and interest.

(v) To encash the advance bank guarantee and performance bond/warranty bond, if furnished by the

BIDDER, in order to recover the payments, already made by the BUYER, along with interest.

(vi) To cancel all or any other Contracts with the BIDDER. The BIDDER shall be liable to pay

compensation for any loss 'or damage to the BUYER resulting from such cancellation/rescission

and the BUYER shall be entitled to deduct the amount so payable from the money(s) due to the

BIDDER.

(vii) To debar the BIDDER from participating in future bidding processes of the Government of India for a

minimum period of five years, which may be further extended at the discretion of the BUYER.

(viii) To recover all sums paid in violation of this Pact by BIDDER(s) to any middleman or agent or broker

with a view to securing the contract.

(ix) In cases where irrevocable Letters of Credit have been received in respect of any contract signed

by the BUYER with the BIDDER, the same shall not be opened.

(x) Forfeiture of Performance Bond in case of a decision by the BUYER to forfeit the same without

assigning any reason for imposing sanction for violation of this Pact.

6.2 The BUYER will be entitled to take all or any of the actions mentioned at para 6.1 (i) to (x) of this

Pact also on the Commission by the BIDDER or anyone employed by it or acting on its behalf

(whether with or without the knowledge of the BIDDER), of an offence as defined in Chapter IX of the

Indian Penal code, 1860 or Prevention of Corruption Act, 1988 or any other statute enacted for

prevention of corruption.

6.3 The decision of the BUYER to the effect that a breach of the provisions of this Pact has been

committed by the BIDDER shall be final and conclusive on the BIDDER. However, the BIDDER can

approach the Independent Monitor(s) appointed for the purposes of this Pact.

7. Fall Clause

7.1 The BIDDER undertakes that it has not supplied/is not supplying similar product/systems or


subsystems at a price lower than that offered in the present bid in respect of any other

Ministry/Department of the Government of India or PSU and if it is found at any stage that similar

product/systems or sub systems was supplied by the BIDDER to any other

Ministry/Department of the Government of India or a PSU at a lower price, then

that very price, with due allowance for elapsed time, will be applicable to the

present case and the difference in the cost would be refunded by the BIDDER to

the BUYER, if the contract has already been concluded.

8. Independent Monitors 8.1 The MoES has appointed Independent Monitors (hereinafter referred to as

Monitors) for this Pact in consultation with the Central Vigilance Commission

1) Shri. Arun Kumar, Ex-Secretary, Oil Industry Development Board (OIDB), B-38, Vrindavan Apartment, Plot No.1, Sector-6, Dwarka, NEW DELHI – 110 075. ([email protected] 09810621113) 2) Shri. Sushil Gupta, Ex-Chairman, Central Ground Water Board (CGWB), No. B-702, Aravali Heights, Sector 21C, FARIDABAD – 121 001. ([email protected] 09999744061)

8.2 The task of the Monitors shall be to review independently and objectively, whether

and to what extent the parties comply with the obligations under this Pact.

8.3 The Monitors shall not be subject to instructions by the representatives of the parties

and perform their functions neutrally and independently.

8.4 Both the parties accept that the Monitors have the right to access all the documents

relating to the project/procurement, including minutes of meetings.

8.5 As soon as the Monitor notices, or has reason to believe, a violation of this Pact, he

will so inform the Authority designated by the BUYER.

8.6 The BIDDER(s) accepts that the Monitor has the right to access without restriction to

all Project documentation of the BUYER including that provided by the BIDDER. The

BIDDER will also grant the Monitor, upon his request and demonstration of a valid

interest, unrestricted and unconditional access to his project documentation. The

same is applicable to Subcontractors. The Monitor shall be under contractual

obligation to treat the information and documents of the BIDDER/Subcontractor(s)

with confidentiality.

8.7 The BUYER will provide to the Monitor sufficient information about all meetings

among the parties related to the Project provided such meetings could have an

impact on the contractual relations between the parties. The parties will offer to the

Monitor the option to participate in such meetings.

8.8 The Monitor will submit a written report to the designated Authority of

BUYER/Secretary in the Department/ within 8 to 10 weeks from the date of

reference or intimation to him by the BUYER / BIDDER and, should the occasion


arise, submit proposals for correcting problematic situations.

9. Facilitation of Investigation

In case of any allegation of violation of any provisions of this Pact or payment of commission, the

BUYER or its agencies shall be entitled to examine all the documents including the Books of

Accounts of the BIDDER and the BIDDER shall provide necessary information and documents in

English and shall extend all possible help for the purpose of such examination.

10. Law and Place of Jurisdiction

This Pact is subject to Indian Law. The place of performance and jurisdiction is the seat of the

BUYER.

11. Other Legal Actions The actions stipulated in this Integrity Pact are without prejudice to any other legal action that may

follow in accordance with the provisions of the extant law in force relating to any civil or criminal

proceedings.

12. Validity

12.1 The validity of this Integrity Pact shall be from date of its signing and extend up to 5 years or the complete execution of the contract to the satisfaction of both the BUYER and the BIDDER/Seller, including warranty period, whichever is later. In case BIDDER is unsuccessful, this Integrity Pact shall expire after six months from the date of the signing of the contract.

12.2 Should one or several provisions of this Pact turn out to be invalid; the remainder of this Pact shall remain valid. In this case, the parties will strive to come to an agreement to their original intentions.

13. The parties hereby sign this Integrity Pact at____________ on ____ BUYER BIDDER Name of the Officer: CHIEF EXECUTIVE OFFICER Designation Deptt./MINISTRY/ PSU Witness: Witness: 1. _________________________1._________________________ 2._________________________ 2.________________________ * Provisions of these clauses would need to be amended / deleted in line with the policy of the

BUYER in regard to involvement of Indian agents of foreign suppliers.

END OF ANNEXURE ‘I’


ANNEXURE - J

SPECIFICATIONS OF HARDWARE/SOFTWARE/PERIPHERALS

Please provide details of the following (additional details may be furnished on separate paper together with Brochures, etc.). The details shall be provided in the format provided below, to the extent possible. However, if the space provided for any particular item is inadequate, the information may be provided as an appendix on a separate paper, and reference about the appendix may be made in the appropriate column in the format.

J1. Details of Software/ peripherals available at IMD proposed to be used for the

project (with details of upgradation if any):

J 1.1 Software

J 1.2 Peripherals (Networking Components etc.)

J 2. Generic specifications of Hardware, software, peripherals, networking, etc.

components proposed over and above the existing infrastructure:

J 2.1 Generic Specifications of the Hardware: (Configuration, etc.)

J 2.2 Software

J 2.3 Peripherals (Networking Components, Plotter, Printers, etc.)

J 3. Auxiliary/Other Equipment, if any:

END OF ANNEXURE J


ANNEXURE- K

PROPOSED DETAILS OF HARDWARE

1. Specification for Rack Mountable Servers (# of Servers: 06)

Components Minimum Required Specs.

Processor Intel Xeon E5-2600v4 series, 2.6GHz (Base Frequency) or higher

Front Side Bus Intel QPI– 9.0 GT/s or higher

# Processors 2

# Cores per

processor

14 or higher

Cache 35 MB or higher

Memory 128 GB DDR 42400MHz ECC RAM(or higher).Must have free slots to upgrade to 256GB.

Hard Disk Drives 4x600 GBusing15Krpmhot swap SFFSAS drives. Bidder must specify the exact number

and size of disks to be provided in BOQ. RAID 0, 1 and 5 configurable

I/O Slots PCI Express 3.0 slots, at least2 x16 slots

Network Interface 2x1Gbps +2x10GbpsEthernet fully loaded, long with network cables with appropriate

length for all the ports.

FC HBA Dual port16 Gbps FC HBA or better for SAN connectivity along with cables of appropriate

length for each port

Graphics Integrated Graphics controller

USB ports At least1 Internal

RAID support Integrated PCI 3.0 RAID Controller with 1GB or higher cache. Support forRAID5 and 6

Form Factor 2U or lesser along rack mountable accessories.

Power Supply Redundant power supply (N+N) hot swappable along with Indian standard power cable.

Operating system

support

Server should be certified for RHEL, Windows Server and preferably other Linux

distribution.

Virtualization Support Must be compatible with latest versions of KVM, VMWARE, V center & Hyper-V.

Server Management Must provide server management software to remotely manage all servers from a single

console.

Management Software deployment to be included for automating deployment of OS image. Should be

possible to manage the servers and get access to critical information about the health of

the server with just the help of standard web browser (http and https). Integrated

management system with dedicated RJ45 port providing out of band access. Should be

possible to manage each server individually.

Server Management Software should be of same brand as of the same supplier. Should

support access rights for administrators for each server individually.

Warranty 3 years comprehensive onsite OEM warranty

Operating System OEM supported RHEL latest version at the time of deployment.


Virtualization Software and

Support

VMware vSphere (ESXi) 6.0 or latest which support all the Enterprise Operating of

Windows and Linux.

B. Specifications for Unified Storage (# 01)

S.N.

Parameter

Specifications

1 Make and Model To be provided by bidder

2

Storage Model

& Architecture

Architecture-Storage must feature SAS architecture

Should not be a SAN emulated on File System

Type-Unified Storage (support both Block &File Protocols)

Protocols-(Block)FC, iSCSI&(File)CIFS, NFS and SMB

Equipped with N+N(minimum2 Array Controllers populated)Nos. of array

Controllers in Active-Active Mode with automatic failover to each other in case of failure

Storage Array should be configured in No-Single-Point-of-Failure Architecture(with all

redundant components)

FrontendInterfaces-8 X16GFCportsand8X10G Ethernet Ports across

Controllers, Ethernet ports shall support both Block (iSCSI)and File(NFS, CIFS)

Protocols simultaneously Back Plane & Ports-4-12Gb/s SAS ports with 4 lane each and with minimum

throughputof192Gbps across storage controllers. Ports have to be redundant for each

controller

3

Upgrades

The system should support future addition of enclosures and disks.

Storage system should support non-disruptive field replacement capabilities for

Components like Disk Drives, Disk Enclosures, Disk connections, power supplies,

controllers etc &upgrade of core software, BIOS, snapshot, clone, remote mirroring and

management software without shutting down the storage system.

All host-attached servers must remain fully operational during system level

maintenance upgrade procedures

4

Spindle

Total usable capacity of 100TB with scalability > 200TB by adding disks and enclosure

Capacity 40 TB using SAS1.2 TB or better(10K/15KRPM)

Capacity of 60TB using NL SAS-4 TB(7.2KRPM)or higher

RAID 6 + DP, LUN size should not be more than 10 disks. Each lun should have minimum

one spare disks per LUN.


Type, usable

capacity and

scalability

Mix &Match of different type of spindles behind same pair of controllers

5

Cache Memory

&Protection

Minimum of 48 GB Cache Memory or higher

Cache should be flexibly usable for Read &Write operations

Storage management should show the promotions/utilization of extended cache

Must support either Cache battery backup or fully automatic de-stage of cache to disks or its

should be non-volatile DIMM (NVDIMM) during power failure to prevent possible data loss.

6

OS Support Industry leading Operating System platforms including :Windows Server®

2008/2012, Linux®2.6 and above, RHEL-5/6/7®,VMware® ESX, Hyper-V®.


7

Global Hot

Sparing

System should have capability to designate multiple global hot spares that

can automatically be used to replace a failed drive anywhere in the system.

8

RAID level

support&

Expansion

Storage system to support HARDWARE based RAID only.

Must support various Hardware RAID levels suchas10, 5 and 6.

Must support inter-mixing different RAID groups within one storage system.

Different type of RAID levels should co-exist within the same array simultaneously

to match different protection requirements of data.

Must support online expansion of RAID Group of all RAID configurations(10, 5

and 6). Must be able to add additional disks on the fly to expand the RAID group

capacity.

License should be provided for RAID 6, 5 and 1/0

9

Online LUN

migration

The array should support online LUN migration (transparent movement of volumes

within the array).The functionality should allow cross RAID migration and cross

spindle migration.

10

Array

Management

Entire System Manageable through direct single secure web based interface

without requirement of management device or server

Management system must include comprehensive online and remote

monitoring abilities without third party hardware or software.

At-a-glance, comparable views of current aggregate capacity statistics and

overall storage resource objects for all SANs of same series from the vendor

Software for auto alerts for disk failures, degradation, critical system errors

through e-mail alerts, self-healing of disks and necessary reporting mechanism

for performance monitoring and capacity planning

11

Auto-Tiering

Data must be automatically moved in a Bi-Directional manner in all the tiers

available and also should support Auto-Tiering among all drives in the same policy

(SAS and NL-SAS), using all tiers in same pool.

12

Thin

Provisioning

Should be configured with required licenses to enable thin provisioning to allow

physical allocation of just the storage that is needed or over provisioning of

capacity

13

Snapshot

Shall be configured with required feature license to snap shot and restore file

and block data

14

Remote

Replication

The storage array should support hardware based data replication at the

array controller level across all models of the offered family.

Support synchronous, asynchronous replication. Further, the replication must be

bi- direction alto support multiple replication options.(Licenses to be included)

Replication shall support incremental replication after resumption from Link Failure

or fail back situations.


Specifications for SAN Switch (# 01)

S.N.

Parameter

Specifications for SAN Switch

1 SAN Switch 24 Port 16 Gbps SAN Switch

2

2

FC ports minimum 24 ports of 16Gbps

3 Configured

Ports

8 ports activated with licenses

4 Scalability Full-fabric architecture with a maximum of 239 switches

5 Aggregate

Bandwidth

384 Gbps end-to-end full duplex

6 Ports minimum One USB port for system log file downloads or firmware upgrades

7 Management

access

Copper Gigabit Ethernet (RJ-45), in-band over Fibre Channel, serial port (RJ-

45), and one USB port

8 Form Factor 1U Rack mountable

9 Support

Management

software

HTTP, SNMP v1/v3 (FE MIB, FC Management MIB), SSH; Auditing, Syslog;

Brocade Advanced Web Tools; Brocade Network Advisor SAN Enterprise or

Brocade Network Advisor SAN Professional/ Professional Plus; Command

Line Interface (CLI); SMI-S compliant; Administrative Domains; trial licenses

for add-on capabilities.

10

Security DH-CHAP (between switches and end devices), FCAP switch authentication;

HTTPS, IPsec, IP filtering, LDAP with IPv6, OpenLDAP, Port Binding,

RADIUS, TACACS+, User-defined Role-Based Access Control (RBAC),

Secure Copy (SCP), Secure RPC, SFTP, SSH v2, SSL, Switch Binding,

Trusted Switch 11

Warranty Warranty includes 3-Year Parts, 3-Year Labour, 3-Year Onsite support with

24x7 support and 4hrs response

15 Licenses TheStoragetoincludelicensesforRAID6,5and1/0,Snapshots, LUN copy & Thin

Provisioning, Replication (Multi-Site).

16

Mount Kits &

Cables

Rack Mount Kits & all Cables as required to complete the connectivity

17

Warranty

3 Years comprehensive (including all Parts-Labor-Service) with4 Hrs ResponseTime

& Resolution within1 day


I. Backup Software: Licensed Industry Standard Backup Software with OEM support compatible with Windows and LINUX environment.

II. Specification for Network Chassis Switch (# 02) and Distribution Switch

Schedule Name of Schedule Quantity

Number

1 Chassis Switch 2

1.1 Power Supply Module for Chassis Switch 4

1.2 Control Module for Chassis Switch 2

1.3 Line card with 20x1000Base-T Ports & 4 Combo GE/SFP

Ports for Chassis Switch 2

1.4 Line card with 20x1000Base-SFP Ports & 4 Combo

GE/SFP Ports for Chassis Switch 2

1.5 Line card with 12x10GBase-SFP+ Ports for Chassis

Switch 4

2 Layer 2 POE Switch, 24 Port 18

3 10G SFP+ Fiber Transceivers 46

III. Chassis Switch and its Components

Description of Your offer

Technical

Details &

compliance

Remarks

General

2 open slot for CPU modules and 4 open slots for I/O modules with

fan module

The Switch shall have Min. 960 Gbps Switching capacity & 1920

Mbps forwarding rate


Management

The Switch shall have 1 x 10/100/1000Mbps RJ45 out of band

management port support out of band SNMP, Web, telnet RFC854,

SSHv2 management

Line Card/IO Module Specification

Should support two numbers of Control Modules from day 1

Line card should support MPLS, RIPNG, OSPF v3 and BGP v4

features

Line card should support stacking & VRF

Loaded Line Cards

Chassis should be loaded with Line card of 20x1000Base-T and 4

Gigabit combo ports

Chassis should be loaded with Line card of 20x1000Base-SFP and

4 Gigabit combo ports

Chassis should be loaded with 2 Line cards of 12x10GBase-SFP

Power Module Specification

The Switch shall provide Redundant power supply with 1+1 backup

capability on 2 power supplies

Reliability

Chassis should be redundant at Control Module, Line card with hot

swap, power supply and fan module level and VSS support

L2 Features

Should support L2 features like STP, IPMB, ERPS, IGMP, MLD,

LBD, VLANs

Layer3 Features

The switch shall support min. 3,500 IP interfaces

Should support L3 features like RIP, OSPF, BGP, VRRP, IPv6


Neighbor Discovery, IPv6 tunnelling

L3 Routing

Chassis should support L3 routing (upto BGPv4+), ECMP, L3

Multicasting features

Quality of Service (QoS)

Should support min 4096 QoS profiles, support 802.1p, WRR,

WDRR, port based bw control

Access Control List (ACL)

Should support IPv4 and IPv6 Access Control List

Security

Support SSH v2 , DoS prevention, CPU protect from broadcast,

multicast, unicast flooding, Database support for Access

Management

Management

Should support Loopback &Cable Diagnostics, 802.3ah, 802.1ag,

link detect, Web Based GUI, CLI, SNMP, RMON, sFLOW,

LLDP/LLDP-MED, IPv6 & IPv6 ping and traceroute

Specification For 24 Port POE L2 Switch


Technical

Details &

compliance

Remarks

Architecture

Proposed Switch should have minimum 20 10/100/1000BASE-T

PoE ports 4 Combo 10/100/1000BASE-T/SFP ports and 4 SFP+

ports with support for Redundant Power Supply

Performance


The Switch shall have Non-blocking wire speed switch fabric with

Min. 128 Gbps Back plane with min 95Mpps forwarding rate

The switch shall be loaded with 10G SFP+ modules from day 1

The Switch shall support Min. 16K Mac address

The Switch shall have min. 40 Gigabit Stacking Backplane

Should support PoE standards 802.3af and 802.3at with 370W,

upgradable to 740W with RPS

Switch should support IEEE 802.3az standard which can reduce

the energy consumption of a link when no packets are being sent.

Layer 2 switching

Switch should support ARP, Proxy & Gratuitous ARP, 802.1Q

VLAN, MAC based VLANs, Protocol based VLANs, STP, RSTP,

MSTP, 802.3ad, IGMP, MLD, LBD

Layer 3 Routing Features

Switch should support Static routing and RIP/RIPng for IPv4 &

IPv6, dynamic routing, Policy based routing, VRRP, IPv6

tunnelling

Quality of service

Should support support 802.1p, WRR, WDRR, port based bw

control, Broadcast and storm control, DSCP, WRED.

Security

Switch should support encryption protocols, ACL for IPv4/IPv6,

802.1X, IPMB, BPDU & ARP attack protection, SSHv2, SNMPv3,

802.1Qbb

Management

Should support Web GUI and CLI, RMON, TFTP, SNMP

Certification

IPv6 Ready Logo Phase 2

Switch should be CE,FCC,UL,VCCI certified


Specification For 10G SFP+ Transceiver


Technical

Details &

compliance

Remarks

Standard

Standard Compliance IEEE-802.3ae 10GBASE-SR SFP+

Multimode type with LC duplex connector

Distance Capacity

Should support min 82m at OM2 and min 300m at OM3

Features

Transceiver should be Hot pluggable, MSA & ROHS compliant &

10Gbps full duplex

Should support min 10Gbps Speed

Physical and Environmental

Operating Temperature: 0 to 70 °C at least Operating Humidity: 5

to 85% at least

Certifications

Should be CE, FCC, VCCI, UL, TUV, CDRH certified


Specification for Wireless Controller (# 1 )


Technical

Details &

compliance

Remarks

Interfaces

It should have minimum 4x 10/100/1000 Base T and

4x100/1000 Mbps SFP combo Ports for connecting to

LAN, USB and one console port.

Controller should support 256APs standalone and 1024

in cluster

Controller should have capacity to handle minimum

12000 or more concurrent devices with 4Gbps or more

Wi-Fi throughput

Wireless Features

Should support detection of interference and auto

channel selection

Should support VLAN per SSID

AP should discover Controller without any configuration

on the AP

System should support IDS and IPS

Controller should detect any Rogue APs in the network

System must be able to provide L2/L3/L4 Access Control

AP should support user isolation on wireless

Should support IPv4 & IPv6, support internal or external

DHCP server

Controller should support MAC authentication for

wireless users with support for at least 1024 entries

The controller shall be manageable using CLI,

Telnet/SSH, HTTP based GUI and SNMPv2/v3.


Access Points should not be fully dependable on

Controller; in case of downtime of the controller, basic

functions like SSID broadcast and connectivity to AP

should be possible.

Controller should support per SSID bandwidth Rate

Limiting, self healing in case of RF coverage loss, band

steering, guest login portal

The controller should support 802.11ac standard.

The Controller RF management algorithm must allow

adjacent APs to operate on different channels, in order to

maximize available bandwidth and avoid interference.

The controller should support advance QOS to

implement role based access for data, voice and video

applications. It should support session prioritization, as

well like Voice, Video and Data, should get different

QOS.

Controller should support reliable fast roaming standards

802.11k

Should be WiFi Certified, FCC, CE, C-Tick, IC, cUL, LVD

certified

Specification for Indoor Access Point 802.11ac( # 10)


Technical

Details &

compliance

Remarks

Standards

Should support IEEE 802.11ac with backward

compatibility up to 802.11a & b

Compliant with IEEE 802.3ab,IEEE 802.3u and IEEE

802.3x

Compliant with IEEE 802.11i for enhanced security


Should support 802.3at POE standard

All the Access points supplied should support IPv6&

IPv4 from day one.

Modulation types support- BPSK, QPSK, 16QAM,

64QAM, OFDM,DQPSK, DBPSK and CCK

Support for IEEE 802.11e U-APSD & 802.11h

Interface and antenna

Should Have minimum 2 x auto-sensing RJ-45

10/100/1000 Mbps Gigabit Ethernet ports & one console

Port

Should support Internal array of min 6 omni-directional

antennas

Minimum antenna gain of 5 dbi for 2.4GHz and 6.5 dBi

for 5 GHz

The min transmit power of AP should be atleast 18 dBm

for 2.4GHz and atleast 15 dBm for 5GHz radio while in

accordance to WPC with MIMO: 3x3 with 3 spatial

streams

Features

Should support at least 1300Mbps at 5GHz and

450Mbps at 2.4GHz

It should support to work in Stand-Alone Mode and in

Managed Mode

Should support atleast 30 configurable SSIDs.

Should support Beamforming technology and

Bandsteering functionality

It should support Wi-Fi Multimedia (WMM) for QoS

The Access point should support Static Link Aggregation

Security


support for SSID Broadcast Enable/Disable option to

prevent detection of the AP network

Support for Static & Dynamic WEP encryption, WPA

personal/Enterprise with PSK, TKIP & AES

Isolation between two wireless clients associated with an

access point

Access point Management & Maintenance

Remote configuration and management through Web

browser,SNMP or telnet with command line interface

(CLI), TFTP/HTTP, WebGUI, NTP

Certifications

UL 2043, Wi-Fi, LVD, VCCI, CE, FCC, cUL, IC,C-Tick,

NCC and TELEC

AP should be as per WPC norms for indoor AP. OEM

should give a undertaking letter stating that the AP will

configured as per WPC guidelines for indoor AP and also

submit the WPC certificate showing approval.

Memory & Environmental conditions

Operating Temperature 0 ~ 40°C

2U Standard Server Rack (#01)

Specifications for Server Rack with Wheel (Black color rack only)

Sl.No Item Specification

1 42 U Black Color Server Rack with PDU’s that can accommodate fully populated

rack, with power from two sources (2X24 Outlets)

2 19 inch sliding TFT Color Monitor (rack mounted monitor with required cables,

keyboard, mouse and touch pad)

3 16 port IP based KVM Switch along with required cables

Tape Library (#01)


Item Description of Requirement

Backup Device Tape Library with 2 x LTO7 drives (FC) & 10 Media Slots; Media

Included for all slots: - 1 Nos. One cleaning cartridge.

Capacity 1. Shall support Native data capacity of 100TB (uncompressed)

expandable to 200TB (2.5:1 compressed) using LTO-7 Technology.

2. Shall be offered with Minimum of two LTO-7 FC tape drive. Drive shall

support encryption and WORM tapes.

3. Shall be offered with 10 Cartridge slots.

Tape Drive

Architecture

1. Offered LTO-7 drive in the Library shall conform to the Data rate

matching technique for higher reliability.

2. Tape Drive Architecture in the Library shall conform to the

INCITS/T10 SCSI-3 standard or newer standards.

Scalability Tape Library shall be scalable to quad number of LTO-7 drives

Speed Offered LTO-7 drive shall support 300MB/sec in Native mode.

Connectivity Offered Tape Library shall provide native FC connectivity to SAN

switches.

Partitioning Offered Tape Library shall have at-least two partition support so that

drives can be configured in a partition with dedicated slots.

Management Tape Library shall provide web based remote management.

Barcode Reader

and Mail slots

Tape library shall support Barcode Reader. Should support email alerts

and Barcode Label should be given with tape.

Other Features 1. Tape Library shall have GUI Panel

2. Shall be rack mountable.

3. Shall have option for redundant power supply

Warranty Tape library Warranty (Hardware) includes with 3 years Technical

Support having no additional cost to IMD, Pune for change, replacement

of parts, labour, consumable, insurance and shipment etc. 24x7 support

with 4 hours of response time & 48-hour resolution time

Cleaning Media 2 Nos. Separate cleaning tape slot for housing cleaning media.

Scalability Tape Library shall be scalable to quad number of LTO-7 drives


Connectivity Offered Tape Library shall provide native FC connectivity to SAN

switches.

Management Tape Library shall provide web based remote management.

Licenses Supply should include perpetual licenses for Tape library, drives, logical

partitioning and management. Also, the license should include for all

available data slots.

Warranty and Support

i. All systems must have 5 years comprehensive onsite OEM warranty. ii. Both the bidder and the OEM will be responsible for providing support to the system during

the warranty period. IMD, Pune must be able to contact both the bidder and the OEM for service during the entire warranty period.

iii. The bidder must provide a write up on its service and maintenance capability, and the escalation support matrix suggested for the Institute.

iv. The OEM must provide details of support structure and escalation matrix.

END OF ANNEXURE K

OFFICE OF HEAD, CLIMATE RESEARCH AND …imdpune.gov.in/Links/tenders/TD.CDSP.NDC.pdfTender Document...

Documents

Transcript of OFFICE OF HEAD, CLIMATE RESEARCH AND …imdpune.gov.in/Links/tenders/TD.CDSP.NDC.pdfTender Document...