Part-II
Of Tender For
FOIS EDW
Solution
2013
Centre for Railway Information Systems, ChanakyaPuri,
New Delhi-110021
Page 2 of 70
Table of Content
Chapter Title Page
1 Key Dates 5
2 Project Background 6
2.1 About Indian Railways 6
2.2 About CRIS 6
2.3 Background of FOIS 6
2.3.1 Functionalities of Projects 6
2.3.2 Integration of other application with FOIS 8 2.4 Current Reporting System in FOIS and other Projects 8
2.5 Objective of EDW Solution 8
3.0 Instructions to Bidder 9
3.1 Tender Questions and Clarifications 9
3.2 Tender Response Format 10
3.2.1 Consortium 10
3.2.2 General Instruction to Bidder 11
3.2.3 Financial Information 11
3.3 Proposal Submission 11
3.3.1 Proposal Submission for Stage – 1 11
3.3.2 Proposal Submission for Stage – 2 12
3.4 Proposal Evaluation for Stage 1 12
3.4.1 Details of Screening of bids (Step I of Stage 1) 12 3.4.2 Detailed Technical Evaluation (Step II of Stage 1) 13 3.4.3 Final Performance Benchmark and Invitation for Stage 2 14
3.5 Proposal Evaluation for Stage 2 14
3.6 Notification of Award 15
3.7 References 15
4.0 Scope and Description of Work 16
4.1 Scope of Work 16
4.1.1 Solution provider should keep the following requirement while
designing the solution to match the above scope 16
4.2 Location of Work 18
4.3 Tentative Project Plan 18
4.4 Participation of CRIS Team 19
4.5 Hardware and Operating System 19
4.6 System Performance, Monitoring and Availability 20
4.7 System Security and Audit 21
4.8 Backups and Recovery 21
Page 3 of 70
4.10 Patches and Updates 23
4.11 Network Design 23
4.12 Testing Tool 24
4.13 Description of Data Warehouse Workloads and Sizing 24
4.14 Development Setup 24
4.15 Software License 25
4.16 Acceptance Criteria 25
4.17 Offer Validity 26
4.18 Requirement of Near Real Time Data Integration/CDC 26 4.19 Existing Source Infrastructure and Standards 26
4.20 Bank Guarantee 27
4.21 Payment Schedule 27
4.22 Warranty and Support Period 28
4.23 Terms and Conditions for Penalties 28
5.0 Solution Development Support and Consultancy 29
5.0.1 Intellectual Property 30
5.1 POC Verification Procedure 30
6.0 Bid Forms Stage - 1 32
7.0 Bid Forms Stage - 2 34
Annexure-I Bidder Selection Criteria 35
Annexure-II Proposed Solution And Approach 37
Annexure-III Features Compliance Matrix 38
Annexure-IV POC 53
Annexure-V Non-Disclosure Agreement for Use of Data for POC 66
Annexure-VI Mandatory Items 67
Page 4 of 70
List of Tables
Table 1 Key Dates 5
Table 2 Eligibility for bidding 9
Table 3 Marks for Green Solution 13
Table 4 Marks for Feature Compliance Matrix 13
Table 5 Customer Reference 15
Table 6 Tentative Project Plan 18
Table 7 SAN Switch & Tape Library Detail 21
Table 8 Training Requirement 22
Table 9 Near Real Time Data Integration/CDC Requirement 26 Table 10 Configuration of FOIS Source Database & Hardware 26 Table 11 Configuration of ICMS Source Database & Hardware 26 Table 12 Configuration of COA Source Database & Hardware 27 Table 13 Configuration of CMS Source Database & Hardware 27
Table 14 Payment Schedule 27
Table 15 Support required in man days for various components 29 Table 16 Questionnaire Format for Technical Bid 33
Table 17 Bidder Selection Criteria 35
Table 18 Marking Criteria for Essential Features 39 Table 19 Marking Criteria for Important Features 39 Table 20 Marking Criteria for Good To Have Features 40 Table 21 Compliance Matrix for General, OLAP and Data Mining
Features
41
Table 22 Compliance Matrix for BI features 43
Table 23 Compliance Matrix for EDW database features 48 Table 24 Compliance Matrix for ETL & Near Real Time Data
Integration/CDC features
50 Table 25 EDW solution Performance POC – Response Sheet 62 Table 26 Feature Demonstration POC – Response Sheet 65
Page 5 of 70
1. Key Dates
Table 1 – Key Dates Date of Publishing of
Tender 31-12-2013
Tender NO: 2013/CRIS/940 Last date of receipt
of queries on Tender
10-01-2014
The queries may be addressed in writing to :
Dy. Manager/Purchase, CRIS, Chanakyapuri, New Delhi
Date & venue of Pre-bid Conference
16-01-2014 at 15.00 hrs. in Conference Room CRIS, Chanakyapuri,
New Delhi, Pin- 110021 Last date for
submission and opening of bid (only technical) for Stage 1
28-02-2014 at 15.00 hrs. The bids to be addressed to :
Dy. Manager/Purchase, CRIS, Chanakyapuri, New Delhi
Date & Venue of Invitation for Stage 2
11-04-2014 at 11.00 hrs and Venue is:- Conference Room
CRIS, Chanakyapuri, New Delhi
Last date for submission and opening of bid
(techno-commercial) for Stage 2
05-05-2014 at 15.00 hrs. The bids to be addressed to : Dy. Manager/Purchase, CRIS, Chanakyapuri, New Delhi
Pin- 110021 EMD Amount 10 Lakhs Cost of the Tender Rs. 10000/-
Page 6 of 70
2. Project Background
2.1 About Indian Railways
Indian Railways are amongst the largest Railway networks in the world, providing a significant part of the country’s transportation needs, both in the passenger and freight segment.
Indian Railways are divided into 16 Zonal Railways, each headed by a General Manager. The General Managers of the 16 Zonal Railways and the 6 Production Units report to the Railway Board. Each Zonal Railway is further divided into Divisions. There are 68 Divisions in the Indian Railways at present.
2.2 About CRIS
Ministry of Railways established Centre for Railway Information Systems (CRIS) in 1986 as the umbrella organization for all IT activities for Indian Railways (IR).
CRIS has developed the Freight Operations Information System and acts as the sole repository of all effects accruing from the project, including know-how, design and drawings, documentation, software packages and equipment on behalf of the Indian Railway.
2.3 Background of FOIS
The Freight Operations Information System (FOIS) is used for logistic management of freight traffic and it’s accountal. This system is currently accessible to the users from different zones/divisions of Indian Railway that are connected to the dedicated network of Railways. FOIS has users at different levels like Railway Board, Zonal, Divisional and Station. All these users have a definite scope to see the data.
2.3.1 Functionality of Projects FOIS
Commercial functions of FOIS provide Acceptance, Booking and Delivery of Consignments, Collection of Freight, RR generation and Transmission, Station Accounting. Collection of RR through E-Payment with B2B Integration with different Banks is also available with the system. Commercial transactions for freight loading and unloading are reported from over 1500 locations throughout the country.
Operational functions of FOIS provide facility of acceptance of customer’s order, Supply of Rakes/Wagons, Movement and Delivery at destination and Consignment Tracking.
Page 7 of 70
COA
Train operations on the Indian Railways are controlled and monitored by the Control Rooms in each of the seventy seven divisional offices. The Control Room is the nerve centre of the division. The fluidity of train movements over the jurisdiction of the division is dependent on the efficiency of the Control Room operations. The Control office, by its very nature never shuts down and works all hours of the day and every day of the week. The Control Office Application has changed the way the trains are monitored as train movements are captured in real time and movement of scheduled and unscheduled trains planned and controlled through the computer aided interface.
Along with Freight Operations Information System (FOIS), COA has led to all information on train operations being computer generated. It is this application that feeds the National Train Enquiry System (NTES) that provides passengers up to date information on train running. The objective of the Indian Railways is to further improve the operations by using technological aids that enable quicker data capture and intelligent applications that provide better planning and forecasting tools.
ICMS
Millions of passengers book their journeys everyday with the confidence that when their train rolls up on the appointed day, it would bring a coach which has place for them. To meet this expectation day in day out, Indian Railways need to track over 50 thousand coaches. By efficiently deploying the fleet, railways are able to run more services for the benefit of their passengers, while minimizing any chances of disruption and disappointment. IR also must ensure that these assets receive timely servicing and maintenance. Depending upon the need, the system can deliver historical records from past years in printed reports, or up-to-the-minute information on an official’s cell phone.
The Integrated Coach Management System does exactly all this and more. There are three modules that give a comprehensive view to the managers and facilitate quick identification of available resources and their allocation as per the requirements.
CMS
"Indian Railways have more than 600 lobbies. CMS application started since 2007.A significant number of lobbies is part of Crew Management System (CMS) - the tool to manage crew movement. The CMS application has been developed in house and aims to optimize the crew booked on trains. CMS has a database covering more than 1,00,000 crew members and over 45,000 crew members are being booked daily. It allows us to supervise and analyze crew operations for express, passenger, and freight trains. The Crew Management system (CMS) application is a web based application developed based on rational application development tool and DB2 Database. The CMS application is being accessed through a browser. The application development has been done using MVC software architecture. The browser based CMS application is developed using J2EE 1.4 technology. The Clients are thin Clients connected over IP based wide area network linked to Central Server at CRIS."
Page 8 of 70
2.3.2 Integration of other applications with FOIS
FOIS is currently integrated with ICMS (Integrated Coach Management System), COA (Control Office Application), RBS (Rate Branch System), CMS (Crew Management System), LMS (Loco Management System), FMM (Freight Maintenance Management) and Parcel Management System (PMS).
2.4 Current Reporting System in FOIS and other Projects
FOIS, CMS, ICMS and COA projects currently provide a number of MIS reports to Railway Board, Zones, Divisions and Stations which contains operational details and/or commercial information. These reports are currently being provided mainly through following two functionalities: -
Dynamic reports are accessible to user through desktop application as well as through browser, both on Intranet ( FOIS network) and Internet. These reports are mainly form-based reports.
Static reports are pixel perfect and are published through a web-based application. There are thousands of static reports. These reports mostly include daily/weekly/monthly reports for Railway Board, Zones & Divisions on different parameters and performance indices.
2.5 Objectives of EDW Solution
The proposed EDW solution will function as an MIS repository for FOIS, CMS, ICMS and CO
A. The EDW solutions shall also provide additional functionalities like drill (up/down/through), selective printing etc. In addition, Indian Railways increasingly require complex analysis to support their business. The advanced analytical capability can be provided only with a dedicated decision support system. The EDW solution is also expected to play this role in addition to functioning as an MIS repository.
CRIS therefore envisages the implementation of EDW solution to meet the following major objectives:
• An integrated, centralized and detailed repository of historical and transactional data from different data sources.
• Create an information infrastructure that can be leveraged for consistent data access across Indian Railways and which will form the basis for advanced analytical solutions.
• Enable faster decision-making by supporting Ad-hoc queries, data analysis queries across organizational hierarchies and functional boundaries.
• Transfer Query Load from transactional (OLTP) system to EDW.
• Enable information elaboration using data drills and ad-hoc queries, dashboards, alerts, SMSs, emails and any other related methods.
Page 9 of 70 • Setup of Testing/Development Environment.
All the web-based and other reports of FOIS shall be covered under the scope of the EDW, and shall be provided as part of the present work. The EDW shall also be extendable to cover the information requirements of the other applications that would interchange information with FOIS in future.
3.0 Instructions to Bidders
Bidder proposals in response to this Tender will be accepted by CRIS as indicated in the Key Dates section of this document.
Bidder must use the product (at least warehouse DB, ETL & BI) which lies in
Gartner Leaders Magic Quadrant as of 2013, the proof of same must be enclosed
with the bid. The proposal should be techno-commercial and should be in the format mentioned below. The proposal should be signed by a person or persons (authorized signatory) duly authorized to bind the bidder to contracts. The bidder shall also sign all pages of the original bid document and submit the same along with the technical proposal.
The bidders shall be required to submit the following for being eligible Table 2 – Eligibility for bidding
1. Payment for supply of data for POC
Vendor should make payment of Rs 1,00,000/- and bring a 1TB of HDD to get the data from CRIS. The payment shall be in form of demand draft in favor of “CRIS, New Delhi”.
Bids of only such bidders who have made this payment shall be eligible for evaluation. Interested bidders should take the data within one month from issue date of tender.
The bidder shall sign a Non- disclosure agreement for the data supplied to them for the POC as per Annexure - V.
2 Earnest Money Deposit
The bidder shall submit Earnest Money Deposit with the tender, as prescribed.
Rs 10 Lakhs (Rs.10,00,000/-)
All financial information submitted by the Bidder will be used for evaluation purposes only and will be held in confidence.
3.1 Tender Questions and Clarifications
A pre-bid conference shall be held with all prospective bidders as indicated in the Key Dates section of this document to clarify any doubts or concerns. The bidders must submit their queries in writing by the date indicated in the Key Dates section of this document. No modifications to the tender document or assumptions be drawn
Page 10 of 70
by the bidder (other than what is stated in the tender document) while bidding.
All clarifications/questions must refer to the appropriate Tender page and section number. Bidders must inquire in writing as to any ambiguity, conflict, discrepancy, exclusionary specification, omission or other error in this Tender prior to submitting the proposal. If a Bidder fails to notify CRIS of any error, ambiguity, conflict, discrepancy, exclusionary specification or omission, the Bidder shall submit the proposal at its own risk and, if awarded the contract, shall have waived any claim that the Tender and contract were ambiguous and shall not contest CRIS’s interpretation. If no error or ambiguity is reported by the deadline for submitting written questions, the Bidder shall not be entitled to additional compensation, relief or time by reason of the error or its later correction. CRIS will post answers on its website to all written questions received by the deadline for submitting written questions. CRIS reserves the right to amend answers prior to the proposal submission deadline. Reply/Clarification given by CRIS shall be treated as final. Once clarifications are issued, the bidder should submit a bid which adheres to Tender requirements. Corrigendum or addendum regarding this Tender, if any, will be published on the CRIS website http://www.cris.org.in.
3.2 Tender Response Format
Bidders must address all information specified as per section 6.0, scope of work and all annexure of this document. All questions must be answered completely. CRIS reserves the right to verify any information contained in the Bidder's Tender response, and to request additional information after the Tender response has been received. The response to the clarifications asked by CRIS must be submitted within a week.
Marketing brochures included as part of the main body of the bid response shall not be considered. Such material must be submitted only as attachments and must not be used as a substitute for written responses. In case of any conflict between the content in the attachments and a Bidder's answers in the body of the proposal, the latter will prevail.
3.2.1 Consortium
In case of consortium, bids submitted by a Consortium would be bound by the following additional stipulations:
a) Members of the Consortium shall nominate one member as the Lead Member. He shall be referred to as the ‘Bidder’.
b) The above mentioned lead member (‘Bidder’) of the consortium can submit the bid on behalf of the consortium.
c) The bidder shall fulfill all the selection criteria as indicated in Annexure-I (Bidder Selection Criterion).
d) Number of members in a consortium should be limited to 3.
e) The bidder or any member of the consortium should have bought the data for POC from CRIS and have the certificate for the same.
f) The Bid should contain the information of all members of the consortium. g) In case of consortium, CRIS will interact only will the lead member of the
Page 11 of 70
3.2.2 General Instruction to Bidder:-
In this tender, either the System Integrator on behalf of the Principal/OEM or Principal/OEM itself can bid but both cannot bid simultaneously for the same item/product.
If a System Integrator submits bid on behalf of the Principal/OEM, the same System Integrator shall not submit a bid on behalf of another Principal/OEM in this tender for the same item/product.
The support of hardware & software will be directly provided by their respective OEM, not by the System Integrator or any third party. The contract declaration agreement of the OEM for the same must be enclosed in the bid in original. The support escalation matrix of each OEM for hardware & software support must be placed in the bid.
The system integrator must have a back-to-back agreement with all the participating OEMs for each component/deliverable envisaged to be provided as part of bid.
3.2.3 Financial Information
The Bidder shall provide a complete set of audited financial statements for the past three financial years. All financial statements should be adhered to generally accepted accounting principles. Each Bidder should note that CRIS reserves the right to purchase credit reports and additional financial information, as it deems necessary.
3.3 Bid Submission
A two stage bidding process is being followed for this tender, details of which are given below:-
Stage – 1: The bidders shall submit only their technical bid. The technical bids will
be evaluated by CRIS and final performance benchmarks will be shared after clarification meeting. Based on the mentioned benchmarks bidders shall be requested to submit their revised technical proposal and commercial bid.
Stage – 2: Submission and Evaluation of techno-commercial bids.
3.3.1 Bid Submission for Stage – 1
As part of stage 1 the bidder shall submit his technical bid in a sealed envelope. The envelope shall contain 3 sets of document as given below:
1. Bidder Selection Criteria – Annexure-I also called screening document 2. Technical proposal – Consisting of Proposed Solution and Approach
Annexure-II, Feature Compliance Matrix Annexure-III and Unpriced Bill of Material.
Page 12 of 70
The envelope should be labelled as ‘Response to Tender for FOIS EDW
Solution: Technical Bid (Stage-1)’.
A duplicate hard copy and a soft copy of the proposal should be submitted in the form of CD/DVD in their respective sealed envelope and all versions should be properly checked.
General response should be limited to a maximum of three paragraphs and should address every point as directly and factually as possible. Supplementary information may be attached as an addendum to the proposal. Lengthy narratives should not be inserted into the body of a direct response, and template or "boilerplate" information is discouraged.
CRIS will be the sole judge of the qualifications of all prospective candidates and reserves the right to reject any or all submittals without assigning any reason.
All communication should be documented and done in written mode only. The evaluation process for stage 1 is given at section 3.4
3.3.2 Bid Submission for Stage – 2
In stage 2, Bidders must address all information specified as per section 7.0 and the offer shall contain 2 sealed envelopes consisting of a ‘Revised Technical Packet’ and a ‘Financial Packet’ (Annexure - VII) separately, which will be put into single large sealed envelope and should be boldly marked ‘Response to Tender
for FOIS EDW Solution: Stage-2’.
The revised technical proposal packet shall contain updated ‘Proposed Solution and Approach’ as per Annexure-II and Comparison of revised and previous Unpriced Bill of Material.
The evaluation process for stage 2 is given at section 3.5
3.4 Bid Evaluation for Stage 1
The technical evaluation would be done in two steps, as described below. Step I – Screening of Bids (compliance of Annexure –I)
Step II – Technical Bid Evaluation (compliance of Annexure –II, III and IV) The bids that fail to clear any step shall not be evaluated further.
3.4.1 Details of Screening of bids (Step I of Stage 1)
A preliminary examination for screening of bids to determine substantial capabilities of the bidder will be evaluated as per Annexure-I (Bidder Selection Criterion). CRIS will examine the bids to determine whether they are complete, that the documents have been properly signed, and that they are generally in order.
Page 13 of 70
3.4.2 Details of Technical Evaluation (Step-II of Stage 1)
Evaluation at this step shall be done as mentioned below:
1) Proposed Solution and Approach (Annexure-II)
The bidder is expected to give a detailed description of the proposed solution keeping in mind the scope of work, the size of the database system, other source systems which would contribute to the data warehouse and concurrent users (BI and DB) as mentioned in this document. The solution should thus indicate the architecture, design and network details of all H/W and S/W and other relevant information to be used in the proposed solution. An evaluation of the solution based on feedback to Annexure-II shall be done. Bidder needs to submit supporting documents. There is no minimum qualifying marks for any bidder, however bidder are required to complete all the requirement of annexure-II. Further bidder will be given points/relative points proportional to the lower number of racks proposed, lower levels of noise emission and low power consumption. The result of the same will be populated in table 3 given below:-
Table 3 - Marks for Green Solution
Subject Maximum
Marks
1. Number of Racks 1 1 mark for 2 or lower number of racks and 0 for 3 or more number of racks. The marking for power and noise shall be done relatively.
2. Noise in Db (decibel) 2
3. Power in KVA 2
Total 5 No minimum qualifying
marks 2) Feature Compliance Matrix (Annexure-III)
Technical merits and features will be reviewed against the requirements identified in the “Feature Compliance Matrix” sections as indicated in Annexure-III of this document. The grades given by the bidder in the ‘Feature Compliance Matrix’ will be used to populate table 4 given below (method adopted for scaling given grades is explained in Annexure - III), which will be part of the final Technical score. Bids that receive minimum qualifying marks in each sub-heads will only be considered for POC verification.
Table 4 - Marks for Feature Compliance Matrix
Subject Maximum
Marks
Table 21 - General, OLAP and Data
Page 14 of 70
Table 22 - BI features 25 Table 23 - EDW database features 30 Table 24 - ETL & Near Real Time Data Integration/CDC features
20
Total 95
Total Technical Score
The total technical score shall be obtained by adding up the marks as obtained in table 3 & 4 as given above. The bidder is required to achieve a minimum aggregate score of 80% of total technical score, to qualify for POC verification.
3) Proof of Concept (POC Annexure-IV)
The results of the POC use cases shall be submitted as part of the technical bid document in a separate sealed envelope. The instructions and use cases of POC are mentioned in Annexure IV. The POC result verification will be done by the CRIS technical team at the indicated site (in BSC) by the bidder in India as per the process given in “Section 5.1”.
3.4.3 Final Performance Benchmark and Invitation for Stage 2
Based on the performance POC verification results of the technically qualified bidders, a standardized performance benchmark will be established by CRIS. The final standardized performance benchmark will be shared in the clarification meeting with technically qualified bidders of stage 1 and these qualified bidders will be invited for the Stage 2 of the tender process. Against this standardized performance benchmark the bidder will be asked to submit their revised technical proposal, revised bill of material and their financial bid. The bidder has to scale up or scale down the bill of material within the same technology. All versions and releases of hardware and software proposed in the solution must be latest and proof of the same should be enclosed duly signed by OEM and prime bidder.
3.5 Bid Evaluation for Stage 2
1. At this stage the qualified bidder will have to submit:
1) Revised technical proposal (Annexure – II to be submitted afresh)
2) Confirmation by the bidder that the revised technical proposal now conforms to the performance benchmark standards as given by CRIS while inviting bids to stage 2.
3) Comparison of revised and previous Unpriced Bill of Material.
2. Financial bid with respect to revised bill of material should be submitted by the bidder (Annexure – VII). Financial bid will be opened in the presence of authorized representative of concerned bidders who may wish to remain
Page 15 of 70
present. The date and venue of opening of Financial Bid will be conveyed to qualified bidders. Financial bids will be evaluated to determine the lowest financial bid.
Financial bids with any counter conditions or ambiguous remarks are liable to be rejected.
CRIS reserves the right to re-check/evaluate the revised performance results (through POC verification) given by successful bidder in same way as he has demonstrated earlier or ask for any clarification if required. The bidder has to demonstrate the same to the satisfaction of CRIS before issue of Purchase Order.
Thus both the technical and financial offers of each qualified bidder shall be examined at this stage.
3.6 Notification of Award
The contract will be awarded to the Bidder whose bid is found to be technically suitable and having the lowest financial quote.
3.7 References
The Bidder should provide details of at least two customers for reference preferably in India as indicated in Annexure – I item 4. References should preferably be from customers who have implemented data warehouse solutions.
The references should be submitted in following format. Table 5 Customer Reference
Customer Reference Reference 1 Reference 2
Customer Name Country
Line of business
Total raw data stored in the warehouse
Total disk space
No. of concurrent users ETL tool
Logical Data Model Production Database Production Server OLAP Tool
Analytical Applications (if any) Other information
Page 16 of 70
4.0 Scope and Description of Work 4.1 Scope of Work
The development of the data warehouse solution shall be done by CRIS team with the technical support and consultation provided by OEM as mentioned in section 5.0. The bidder shall provide a complete end to end integrated EDW solution (keeping the requirement of FOIS, COA, ICMS and CMS projects) covering the following aspects:-
• A detailed approach and methodology for design and implementation of the entire solution.
• Supply, installation and commissioning of all proposed hardware and software for production & development setup.
• The various components for the above mentioned scope thus should broadly cover the following, but are not limited to these:
EDW database
Data Modelling Tools
ETL
Near Real Time Data Integration/CDC
ODS
Metadata management
All BI layer components
Data Mining Tool
IDE's at each layer for development, testing and deployment
All hosting, development and deployment servers at each layer
Version Control Mechanism
Management Tools
Auditing tools
• OEM training of all the components used to make the solution must be provided, so that end to end development, management and application hosting can be done by CRIS technical team. The details of training requirement is provided at section 4.9
• CRIS will do the development work of warehouse by itself, therefore technical support during the development phase of data warehouse solution shall be provided from respective OEM as per section 5.0
• Bidders may note that scope mentioned in 4.0 (including all sub sections) is for both production and development setup.
4.1.1 Solution provider should keep the following requirement while designing the solution to match the above scope:-
4.1.1.1 Each product (hardware, operating system & other software) proposed in the solution must have clear roadmap for upgrade, update, patches and support for next 5 years from the bid submission date.
Page 17 of 70
4.1.1.2 All components used to build the solution should be configured in active-active and fault tolerant with 24x7 high availability and must provide load balancing at each component level.
4.1.1.3 Bidder has to mention the situations when planned down time of source systems shall be required, during initial configuration of the solution keeping in mind that the maximum outage time of production system for a single day should not exceed 2 hours.
4.1.1.4 All hardware and software must be licensed to CRIS and the System Integrator/OEM must undertake to stand by their recommended products through indemnification.
4.1.1.5 Bidder must provide a standard LDM tool to design the LDM for the solution which should have ability to support the single view of the business lines scalability to extend subject areas.
4.1.1.6 The solution should be capable of catering to all reporting needs like MIS, Operational, Analytical, Ad-hoc, KPI’s on dashboards and canned reports etc.
4.1.1.7 In EDW solution, all current static and dynamic reports will have functionalities like drill (up/down/through), selective printing, sending any report to separate mailbox of any user at scheduled activities with standard predefined values of parameters in pixel perfect format ready for printing on some standard page size like A4/A3/Fanfold, etc.
4.1.1.8 Provision of across mart/schema query must be available in the proposed solution.
4.1.1.9 All the functionalities of BI tool must be provided from the single interface i.e. there should not be any separate view for pixel perfect reports.
4.1.1.10 BI tool should have capability to handle event notifications and alerts (on email and mobile) based on pre-defined business rules in the solution to enhance decision-making.
4.1.1.11 Since all OLTP system under ambit of this proposal are 24x7, proposed data extraction process should be easy to implement and minimize overhead on OLTP system and during extraction, and there should not be any downtime.
4.1.1.12 The EDW solution must be implemented to fulfill the reporting, Dashboard, Ad-hoc query, data integration etc. requirements of FOIS, COA, ICMS, CMS and other associated applications.
4.1.1.13 Impact analysis should be end to end starting from Source System to ETL to BI layer, and should cover impacts at Report level, Report attribute / metric level, Table level, Field / Column level. The solution should support impact analysis and data lineage features. The ETL tool should support bi-directional lineage at table and field level. Bidder should include any tool required to provide the above feature.
4.1.1.14 ETL tool provided by the bidder must have capability to be used as ELT also. Therefore bidders may note that ETL mentioned in this tender document must always be considered as ETL tool with ELT
Page 18 of 70
4.1.1.15 The solution should provide metadata management. It should collect and unify metadata from different tools and sources into a single repository, which provides a better view of metadata relationships across layers.
4.1.1.16 Each EDW components should have web based interface for the monitoring, management, administration, tuning, performance and diagnosis.
4.1.1.17 The response must include escalation matrix for hardware and software support of all components from their respective OEM.
4.1.1.18 The solution should support extendable design for future enhancements in EDW infrastructure, data model, reporting, Dashboard, Ad-hoc query, data integration etc. as and when required for warehouse as well as future requirements.
4.2 Location of Work
Services provided as part of the awarded Bidder’s solution must be performed at CRIS, Chanakyapuri, New Delhi-110021 unless otherwise indicated by CRIS.
4.3 Tentative Project Plan
Table 6 – Tentative Project Plan
Deliverables Expected
Duration
Responsibility
Delivery of all Hardware & software components
Within 8 weeks after issue of PO
Bidder + OEM Verification of Bill of Material (Production
and Development) 1 Week
Bidder + CRIS
Hardware and Software installation and setup of EDW (Prod. & Dev) Solution in CRIS premises.
3 Weeks Bidder + OEM + CRIS
Developer Training as per training plan In parallel after release of PO
Bidder + OEM + CRIS
Design of Logical Data Model (LDM) 4 Weeks CRIS with the help of OEM
Implementing LDM in Physical model 2 Weeks CRIS with the help of OEM
Implementation of ETL processes 3 Weeks CRIS with the help of OEM
Page 19 of 70
4.4 Participation of CRIS Team
The development of the data warehouse solution shall be done by CRIS team with the technical support and consultation provided by OEM as mentioned in section 5.0. OEM will review the development progress done by CRIS team as and when required by CRIS.
4.5 Hardware and Operating System
4.5.1 Bidder must provide the solution in minimum number of racks and should not exceed 4 numbers of racks. Also the rack used should not be more than 42U.
4.5.2 The total of maximum rated power requirement of actual populated hardware installed in of one rack should not exceed 6KVA.
4.5.3 The database component provided should be a standard Enterprise Data Warehouse appliance. All the components within the appliance must be configured in active - active, no active - passive configuration is allowed. 4.5.4 The hardware, other than database appliance must be configured in blade
architecture (where other software will be installed).
4.5.5 Blade chassis and servers must be in redundancy and configured in HA (active-active) across chassis.
4.5.6 Each software (other than database appliance) of EDW solution must be configured in cluster (Active-Active) and across blade chassis. Servers can be electronically partitioned within chassis.
4.5.7 Operating system should preferably be a proprietary operating system of the hardware OEM or any industry leading enterprise class operating system. In both the cases the operating system must
i. be of 64 bit
ii. have core based or perpetual license iii. be easy to manage
iv. be highly secure and on-line serviceability v. have feature of power fail recovery
vi. allow the best balance between data availability and performance vii. support IPV4 and IPV6 protocols
4.5.8 Hardware used to configure each system software component/tool (like ETL, Near Real Time Data Integration/CDC, BI, management tool, audit, Loading of current and archival data in
warehouse
1 week CRIS with the help of OEM
System Admin Level Training as per plan. After successful installation of h/w
Bidder + OEM + CRIS
Development & Implementation of selected reports, Dashboards, Ad-hoc queries and decision-making alerts as desired. (Phase-I)
3 months CRIS with the help of OEM
Page 20 of 70
etc.) of EDW solution, must have operating system and system software in cluster and configured in active-active.
4.5.9 In case of Linux operating system, the L1 & L2 support must be directly provided by the hardware OEM and in case of L3 & L4 support the hardware OEM is solely responsible to communicate with operating system’s technical support to resolve any issue. In both (Proprietary or Linux) cases, the hardware OEM vendor is solely responsible for providing on-site support as and when required by CRIS during the support period. 4.5.10 Whenever operating system support expires the hardware OEM vendor
will be responsible for renewing the operating system support or renewal of Linux subscription.
Note: - Each hardware and software must have support (levels like L1, L2, L3 or L4) from its respective OEM. No free or unlicensed or unsupported software can be used in EDW solution desired by CRIS. A consolidated support and escalation matrix is to be provided with bid document in Stage-1.
4.6 System Performance, Monitoring and Availability
The desired solution should have the following capabilities in addition to the above:
4.6.1 In case of ‘idle situation’ (i.e. no user load) of the solution, the CPU and memory utilization of each hardware component of the entire EDW solution should never cross the 30% threshold value.
4.6.2 In case of ‘user load situation’ (not in failover condition) after go live (i.e. Phase 1 as given in tentative plan as per section 4.3) the CPU and memory utilization of each hardware component of the entire EDW solution should never cross 60% threshold value.
4.6.3 All EDW components should have web based interface for monitoring, management, administration, tuning, performance and diagnosis.
4.6.4 Architecture should be in active-active design for maximum performance & load balancing in addition to availability.
4.6.5 Each component (hardware and software) of complete solution must be configured in High Availability (Active-Active), Fault Tolerance and Load Balancing mode.
4.6.6 Each tool should have capability to send event notifications and alerts (on email and mobile) based on pre-defined rules.
4.6.7 Annual uptime of the EDW solution/setup must be 99.50%
Note: In the solution designed by the bidder, if any of the system crosses the said performance benchmark or any component is found in non-redundant mode or not comply with the said requirement, the bidder has to procure the h/w & s/w (including licenses if required) at its own cost to meet the same. CRIS will not bear any additional cost liability associated with such procurement.
Page 21 of 70
4.7 System Security and Audit
Security:
4.7.1.5 Role based access at various levels have to be implemented across the data repositories, BI and analytics tools.
4.7.1.6 The solution should provide security features at the database, presentation and application layer level.
4.7.1.7 Encryption of the sensitive data is required.
4.7.1.8 Ability to define separate security rules for various environments (production and development)
4.7.1.9 Information travelled between BI and end user must be secure using “SSL”. The same must be provided with the solution.
Audit:
The solution should provide an auditing and logging facility that should contain at least the following features:-
4.7.2.1 Deter unauthorized user behavior at each layer (ETL, BI, Database, etc.)
4.7.2.2 The audit logs/data must be kept separately from the production or development environment.
4.7.2.3 Audit should include a review of access and authorization procedure, physical security control, backup and recovery procedures, security controls and program change controls.
4.7.2.4 Audit tool should generate a report to safe guard against threats and hazards to the confidentiality, integrity and availability of data.
4.8 Backups and Recovery
FOIS has its own Tape Library. The bidder has to build, implement and demonstrate a solution which is capable of taking the backup of the solution into the existing Tape Library. The detail of the SAN switch and Tape Library is as follows:-
Table 7 – SAN Switch & Tape Library Detail
The software used to build the solution by the bidder must have following capabilities:-
4.8.1 The proposed backup setup must have the capability to backup the data of each component (database, application data, application codes, operating system, etc.) and metadata across all the sub systems on to the mentioned device.
4.8.2 The proposed solution should provide mechanism for incremental and full
San Switch Model Port Speed Free Port Quantity
HP Storageworks 4/32B 4Gbps 12 2
Tape Library Model Backup Software Tape Supported
Page 22 of 70 database backups with zero down time.
4.8.3 The proposed solution should provide monthly validation of database backup. Service includes restoration of database from backup and validation that all database components are present and not defective. An electronic report of the results is provided at completion of validation.
4.8.4 The data transfer from all servers and database to backup device must use the FCIP/SAN as mentioned. The load of backup should not come on network.
4.8.5 The backup solution must able to take backup of each machine’s operating system and use the same for restoration (in case of crash).
4.8.6 If the requirement of free port is more than what is mentioned above (in table 8), then bidder has to make a provision for a new appropriate SAN switches and “Trunking” with existing SAN’s to provide connectivity with the backup device.
4.8.7 Each software component used to build the solution must have the capability to take backup of respective software component to the tape library.
4.9 Training Plan
Training as per plan given below, should be provided by OEM (not by any other third party) at training centers located in Delhi/NCR only. Training shall be provided to CRIS technical team on all the software/hardware technologies used in the proposed EDW solution.
The training must be provided for all software and hardware components like EDW, ETL, BI tools, data modeling & optimization, database administration (basic, advance & tuning), system administration, any special tools used in the solution etc... The purpose of the training is primarily to strengthen the CRIS technical team to develop, maintain and deploy the solution. Training shall include both hands-on and classroom activities.
All training should be based on a training needs analysis as given below:- Table 8 – Training Requirement
Component
Team Training (No of persons) Developer's
Training Admin Training
LDM Designing (Only Experts) 14
Data Warehouse Database 23 23
OLAP/Star Schema designing 25 23
ETL 27 23
Near Real Time Data Integration/CDC 17
BI layer 46 23
OS 27
Any other tool Provided by Bidder 27 23
Page 23 of 70
• Each training batch should be of 8 to 10 persons
• Hands-on training via a classroom/PC lab. Each trainee should be provided a separate PC.
• Bidder has to submit the training plan and also submit the details about the training material.
• Hard copy of training material must be provided to each trainee.
4.10 Patches and Updates
4.10.1 There should not be any extra cost during the entire support period for any new version, update, upgrade and patches of operating system, all the software provided within EDW solution, hardware components and firmware.
4.10.2 As and when required by CRIS, the support for any new version, update, upgrade and patches as mentioned above will be provided on-site by respective OEM.
4.10.3 Respective OEM should be responsible for all hardware and software support including proactive services like firmware upgrades, system health check services, and assessment services etc.
4.10.4 Bidder must provide an authorization letter duly signed by signatory authority from OEM for providing the support as mentioned.
4.10.5 Bidder must provide a clear road map for 5 years of all the hardware and software (from their respective OEM) used in the EDW solution duly signed by a signatory authority of OEM.
4.10.6 All the hardware supplied for this tender should not have a declared ‘end of sale’ of the product within 1 year of submission of stage 2 bid, else the next upgraded version of the same product has to delivered by the bidder to meet the scope of work and other tender condition without any financial liability to CRIS.
4.11 Network Design
4.11.1 Bidder has to provide the network architecture for EDW solution connecting their servers and storage along with the connectivity to the source systems. 4.11.2 The SAN and network speed within the solution must be at least of 10Gbps
or above.
4.11.3 To make this setup, all communication switches (L2 or L3) as required must be provided by the bidder. Moreover, two additional 48 port (fully populated) network switches of 10Gbps in redundant mode must be provided with the solution to communicate outside the solution with source system used for ETL, Near Real Time Data Integration/CDC and public network in CRIS. 4.11.4 Speed of SAN and network switches mentioned in bid should be disclosed
and same setup must be provided in CRIS.
4.11.5 All network devices (Network switch and SAN switches/IB switch) and connection to each warehouse component (ETL/DATABASE/BI etc.) server must be in HA (active-active) & failover.
Page 24 of 70
servers which fall in DMZ. Both the network must be segregated in such a way that server falling in different zone will communicate through firewall only and not within switch. Switch module in blade chassis should be used for cluster heart beat or internal communication.
4.11.7 Requirement of FCIP, network port and IP’s for each server kept in MZ and DMZ should be mentioned separately in the proposal.
4.12 Testing tool
The Bidder should provide standard functional and load testing tool for EDW solution.
4.13 Description of the Data Warehouse Workloads and Sizing
The specified size of the database is the total amount of source system extracted data, defined as all data contained in the database, including all data warehouse design-specific structures (such as indexes, cubes/stars schema and summary tables). Source system extracted data is the actual row/byte count of data that is reconfigured and loaded into the warehouse, without regard to optimization techniques implemented to meet the requirements of EDW.
The data warehouse size of FOIS and other projects is estimated to be around 40TB (usable size) in next 4-5 years on production system considering the current growth pattern. Also, data size to implement ODS for decision support can be considered as 1.5TB for production and 500GB for development setup. In addition around 2TB data space is required for development setup. Hence the total minimum required usable space in EDW database is 44TB excluding any overheads like database basic requirement, spool files, dictionary tables, temp space, database logs etc.
Any server other than warehouse DB in production setup should have a usable space of 1TB and configured in RAID1.
It is to be noted that the data warehouse solution would have a maximum of 400 concurrent users at BI layer and 400 active queries at database layer. Also the maximum connected users at BI layer would be around 5000. The proposed solution should cater for the above requirements. Also the rpm of the hard disk used to build solution should be equal or more than 10k.
4.14 Development Setup
Bidder must consider following points while designing the Development Setup for EDW:-
4.14.1 Bidder must provision the hardware of development setup in HA (active-active)
4.14.2 Bidder must provision a database sizing of 2 TB (usable and configured in RAID 1) for storage of development data.
4.14.3 Any server, other than warehouse database should have available usable space of 500GB usable and configured in RAID1.
Page 25 of 70
4.14.4 Data size to implement ODS for decision support can be considered as 500GB for development setup.
4.14.5 Bidder must consider similar software setup as proposed on production for development setup.
4.14.6 Development setup hardware must have enough sizing to handle at least 10% load (40 concurrent users) of production setup.
4.15 Software License
4.15.1 For both production and development setup ETL, Database, BI and other software licenses shall be free of project specific restrictions. The same setup may be used to meet requirements of other projects, as long as additional resources are not required.
4.15.2 The EDW solution may be integrated with applications beyond those mentioned in scope of work (section 4.1) in due course. The offered license terms should not restrict such integration as and when CRIS plans to do the same and there should not be any additional cost liability associated with such integrations.
4.15.3 Bidder has to mention clearly and separately the unit cost of supplied software and hardware including licenses. The bidder has to keep on hold the said unit price for 3 Years for any additional requirement considered necessary by CRIS for future enhancement of the project.
4.15.4 All the software licenses must be perpetual and should not be user based for any tool. No of users mentioned in tender document must only be used for sizing and not for licensing purpose.
Note: For any new version, update and patch management of any software (ETL, Database, BI, Operating System, etc.) within the solution there should not be any extra cost during the support period (The support period could be additional 5 years after initial 3 year warranty period provided, if CRIS agrees to the additional period).
4.16 Acceptance Criteria
Preliminary Acceptance Criteria
• Physical verification of equipment/components as per the Bill of Material (BoM). • Physical inspection of the equipment/components for any physical damage • 72 hours “Power on self test” of hardware.
• Physical verification of software media, licenses and documentation (which shall also include Installation and warranty certificates from OEM) as per tender.
• Delivery, installation & commissioning of hardware & software. No open issues left w.r.t. hardware, software and licences.
• ‘Idle utilization’ of hardware is as per the standards mentioned in this document at section 4.6, else bidder has to make provision to increase the resources to meet the same at his own cost including hardware and software licenses.
Page 26 of 70
The date of issue of Preliminary Acceptance Certificate shall be termed as date of Preliminary Acceptance.
Final Acceptance Criteria
• All the training modules must be completed. Software support services must be started.
• Three month after go live of EDW solution and utilization of hardware is as per the standards mentioned in this document at section 4.6 under ‘user load condition’, else bidder has to provision to increase the resources to meet the same at his own cost including hardware and software licenses.
• Go live will be the date on which CRIS completes its phase-I development. • At this time the version and patches of all software, firmware & OS must be
latest and proof of the same should be submitted by the bidder. • No single point of failure.
• Final acceptance test certificate to be signed jointly by CRIS and the bidder.
4.17 Offer Validity
The offer should remain valid for a period of at least 180 days from the date of the submission of offer.
4.18 Requirement of Near Real Time Data Integration/CDC
Table 9 - Near Real Time Data Integration/CDC Requirement
S/N Application Database Type Near Real Time Data
Integration/CDC
Delay to reflect in EDW
1 FOIS Oracle Database Yes Less than 3 min
4.19 Existing Source Infrastructure and Standards
Table 10 - Configuration of FOIS Source Database & Hardware
Server (Type & Model) Number of Servers Memory in GB No. of Cores Processor Type Operating System Database HP
RX6600 1 (Active) 32 4 Itanium HP Ux 11i V3
Oracle HP
RX6600 1 (Active) 32 4 Itanium HP Ux 11i V3
Oracle
Table 11 - Configuration of ICMS Source Database & Hardware
Server (Type & Model) Number of Servers Memory in GB/Server No. of Cores Processor Type Operating System Database PA-RISC, Model- 9000/800/rp 4410 2 16 (may increase to 32GB/ Server) 4 (may increase to 8 shortly) Itanium HP-UX 11.23i Oracle
Page 27 of 70
Table 12 - Configuration of COA Source Database & Hardware
Server (Type & Model) Number of Servers Memory in GB/Server No. of Cores Processor Type Operating System Database Rack Mountable Server HP Proliant DL385 2 database server per division 4 GB/ server Dual Core AMD Opteron ™ 2.2 GHz Windows server 2003 R2 Oracle
Table 13 - Configuration of CMS Source Database & Hardware
Server (Type & Model) Number of Servers Memory in GB/Server No. of Cores Processor Type Operating System Database
IBM P5 550 1 (Active) 32 GB 4 RISC AIX DB2 IBM P5 550 1 (Passive) 32 GB 4 RISC AIX DB2
4.20 Bank Guarantee
The selected Bidder is required to submit a bank guarantee, which should be 10% of the Total Bid Amount of the tender within 14 days from issue of letter of acceptance. PO will be issued after submission of performance Bank Guarantee from a scheduled bank.
The submitted Bank guarantee will be released by CRIS three months after the end of warranty period (3 Years from the date of issue of PO, therefore the validity of the BG should also comply the same duration).
4.21 Payment Schedule
Table 14 – Payment Schedule
Sr. No.
Schedule Description Terms & Conditions
1. First Installment 80% of contract value (except cost of man days for Solution Development Support)
This installment will be paid on submission of the performance bank guarantee for 10% of tender value and after preliminary acceptance (as per section 4.16). 2 Second
Installment
20% of contract value (except cost of man days for Solution Development Support)
This will be released after final acceptance (as per section 4.16).
Page 28 of 70 3 Solution
Development Support Payment
Quarterly (at quarter end) As per actual consumption of man days as accepted by CRIS.
4.22 Warranty and Support Period
4.22.1 The selected bidder must quote the complete comprehensive warranty cost of each component for 3 years (cost which has been included in the bid value) and yearly warranty cost for next 5 years as given in schedule of rates (option to enter warranty after 3 years shall rest with CRIS, who shall also have the right to negotiate the indicated rates if required).
4.22.2 The support as mentioned above should not be fall in the extended support period for any component.
4.22.3 All support must be directly from OEM. The back to back arrangement agreement for the same must be enclosed and signed by signatory authority of bidder and OEM.
4.22.4 Each participating OEM in the bid must have or create technical staff located in NCR. The proof of the same should be submitted duly signed by signatory.
4.22.5 The hardware warranty, operating system and other software support must start from the date of preliminary acceptance.
4.22.6 Clear road map for at least 5 years of each component of hardware and software must be submitted by the respective OEM duly signed by their signatory authority.
4.22.7 The onsite support of hardware, for each component must be on 6 Hour CTR (call to repair) basis.
4.22.8 The support provided of hardware and software must be for 24 X 7 by their respective OEM.
4.22.9 Proactive support on regular interval for any new version, update, upgrade and patches mentioned above will be provided on-site by respective OEM. 4.22.10 All OEM of hardware and software must have local presence in Delhi/NCR.
The proof of the same must be submitted by the bidder duly signed by the signatory authority of respective OEM.
4.22.11 In case of consortium, prime bidder must furnish the letter of authorization (signed by signatory authority of respective OEM) and clear defined roles and responsibilities for the warranty and support from all respective OEM of the EDW components as stated. Also the prime bidder shall nominate a single point of contact for the project.
4.23 Terms and Conditions for Penalties
4.23.1 If the hardware failure support breaches 6Hrs CTR (call to repair), then a penalty will be charged on hourly basis and the cost of penalty per hour will be 0.02% of the contract value per year against each registered case for each component.
Page 29 of 70
4.23.2 Total annual uptime of the solution (hardware and system software for production setup only) should be more than 99.50% per year, else a penalty of 1% of the contract value per year will be enforced on the bidder. This penalty will be applicable only on hardware and system software after logging the case to the respective OEM. Penalty will not be applicable on the downtime due to the application developed by CRIS.
4.23.3 All penalties will be deducted from the bidder bills. In case the penalty cost raised by CRIS is not paid by bidder in due time than CRIS has the right to deduct it from the bank guarantee amount.
4.23.4 In case the total penalty exceeds 10% of contract value, CRIS reserve the right to terminate the contract and forfeit the Bank Guarantee.
4.23.5 If any of the machine/server crosses the performance benchmark (as mentioned in section 4.6) or any component is found in non-redundant mode, the SI has to procure the h/w & s/w (including licenses if required) to meet the same, else the desired augmentation will be done by CRIS and the cost of the same will be deducted from the bidder bills.
4.23.6 Penalties will be enforced only on unplanned downtimes.
5.0 Solution Development Support and Consultancy
CRIS will develop the EDW solution through collaborative development with OEM support team. To enable the same, selected bidder shall provide the support from respective OEM for following developments:
• LDM Designing • ETL Layer
• Near Real Time Data Integration/CDC implementation • Warehouse database
• OLAP/Star Schemadesigning • BI and Data Mining Layer
Table 15 - Support required in man days for various components
LDM Designing
Data Warehouse ETL
BI layer Man Days Database OLAP/Cubes designing ETL Jobs
Near Real Time Data Integration/CDC
100 130 140 90 30 210 700
All technical support must be provided by their respective OEM as and when required by CRIS. CRIS will reserve the right to ask for support for above developments stages as required. CRIS may call resources in parallel for different support at the same time. One man day will be counted for 8 hours of support irrespective of day or night. CRIS will intimate for any planned activity of man power support 15 days in advance, and for any unplanned activity (emergency support) CRIS has the right to
Page 30 of 70
call support person anytime. As above requirement are indicative, so it is possible that few days less or more is required against each indicated activity. It is expected that bidder will able to adjust these requirements within the total man days which may be deemed to be fixed. Bidder must provide a standard man power cost for each
component. The above man power support will be valid for 3 Years from the
date of issue of purchase order.
The support resource must have minimum 5 years of relevant experience in the area of expertise with relevant qualification and should have worked on 2 EDW projects of at least 20 TB each. The resource should have capability for coding,
design, debugging, optimization and tuning for each respective
component/tool. The experience and qualification of the technical resource should be shared with CRIS before commencement of development support. CRIS reserves the right to request for change of the resource if found unsuitable for a particular development support component. Once the resource is accepted by CRIS, than change in deputed resource will only be allowed after taking permission from GM/FOIS.
Note: The above support will not be part of hardware and software installation and commissioning.
5.0.1 Intellectual Property
It may be noted that the intellectual property right of the data warehouse software solution developed by CRIS as part of this tender will reside with India Railways.
5.1 POC Verification Procedure
5.1.1 Bidder has to be ready for POC verification after submission of the bid. The schedule for the same will be intimated to each bidder at least one week prior to visit by CRIS team.
5.1.2 As POC is a part of technical evaluation, CRIS team will verify the POC results at the premises with in INDIA only as mentioned in Bidder Selection Criteria.
5.1.3 The bidder needs to showcase the POC results on exactly the same stack/hardware of EDW solution proposed by the bidder including the network configuration within the solution.
5.1.4 The hardware setup for demonstration of POC cases can be setup within India or outside India. If the bidder is demonstrating the POC remotely in India using a physical setup outside India then the bidder also has to make arrangements for a site visit within India of a live data warehouse setup. 5.1.5 CRIS team may ask for the verification of hardware configuration as per the
Page 31 of 70
5.1.6 Bidder has to verify the POC result within 5 days.
5.1.7 All use cases are to be performed in sequence as mentioned in tender document.
5.1.8 Query should not be in cache before execution of any use case.
5.1.9 During POC demonstration, the system resource utilization should not cross as mentioned in section 4.6.
5.1.10 The POC results, along with the infrastructure (hardware, software etc.) should be included in the technical proposal.
5.1.11 Basic configurations of system has to be verified to CRIS team at start of each day using a script made by the bidder.
5.1.12 Bidder has to provide minimum three network connection for CRIS team to connect their laptops with internet facility.
5.1.13 Speed of SAN and network switches used while demonstration and mentioned in bid should be disclosed and same SAN setup must be provided in proposed solution.
5.1.14 Detail logs of all the script and command executed during POC verification process must be captured and submitted to the technical team.
5.1.15 All POC results shall be signed by both CRIS and bidders team.
Important: Improvements in the POC results at the time of verification are accepted,
Degradation of result during POC verification beyond specified limits (up-to 20% degradation in case of query performance and up-to 10% degradation in all other case) will be viewed seriously and could lead to even disqualification of the bidder from the bidding process.
Note: Except basic courtesy, no extra hospitality (boarding, lodging etc.) will be accepted by CRIS team during POC verification process.
Page 32 of 70
6.0 Bid Forms Stage - 1
Tender Submission Form – Stage 1
To,
<Contact Person>, CRIS, Chanakya Puri, New Delhi, Pin- 110021 Dear Sir,
SUBJECT: TENDER FOR FOIS ENTERPRISE DATA WAREHOUSE SOLUTION FOR CENTRE OF RAILWAYS INFORMATION SYSTEM (CRIS)
With reference to your subject tender, we confirm having carefully read, studied and understood various conditions/documents supplied with the tender and submit them duly signed and stamped as having accepted the same in entirety. We submit herewith our proposal, duly signed, in sealed envelope as per details given hereunder:
COVER ENVELOP CONTAINING
(A) Power of Attorney for the Authorized Signatory (B) Earnest Money Deposit (EMD)
(C) Technical Bid Packet
(B) Unpriced Bill of Material (BOM)
Thanking You
Yours faithfully
Signature of Bidders Authorized Signatory With Designation and Stamp.
