RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
TENDER DOCUMENT
OFFICE OF THE Sr. EDPM, M.I.S. CENTRE, RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560064.
TENDER NOTICE NO. RWF/MIS/SD(IIMS LAN)/556 Dated: 29.12.2018
Name of work :- “Software Development for RWF’s Intranet Business Application (IIMS LAN)– Upgradation”
Page 1 of 54
GOVT OF INDIA RAIL WHEEL FACTORY Office of the Sr. EDP Manager Yelahanka, Bangalore – 560 064 Web site: www.rwf.indianrailways.gov.in
On behalf of the President of India, sealed Tenders are invited by the Sr. EDP Manager, M.I.S. Centre, Rail Wheel Factory (RWF), Bangalore - 560 064, for ”Software Development for RWF’s Intranet Business Application (IIMS LAN) - Upgradation” from Professionals in Dot Net and Visual Basic.
Sr. EDP Manager Rail Wheel Factory for and on behalf of President of India
Page 2 of 54
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064 CONTENTS OF TENDER DOCUMENT
Chapter Index Page No. No(s) 1. Top Sheet 4 2. Check Sheet 5 3. Brief of RWF’s Business Application 7-25 4. Brief of RWF’s IT Infrastructure 26-28 5. Technical Evaluation Criteria 29-30 6. Scope of Work (In Brief) 31 7. Detailed Scope of Work – Technical Specifications & Deployment Architecture for Software Development/Conversion/Upgradation 32-36 of IIMS LAN – Part I 8. Detailed Scope of Work – Technical Specifications of Software Development/Conversion/Upgradation of IIMS LAN – Part II 37 9. Detailed Scope of Work – Workflow & Estimated Timelines for Software Development/Conversion/Upgradation of IIMS LAN – 38 Part III 10. Special Conditions of Tender 39-40 11. Security Deposit and Performance Guarantee 41-43 12. Prices & Payment 52-53 13. Annexures --- Declaration of Compliance, Annexure-A 44 Declaration of Familiarization, Annexure-B 45 Schedule of Rates-A 51 Deviation Statement, Annexure-C 46 Agreement for Works, Annexure-D 47-48 Proforma for Performance Bank Guarantee, Annexure-E 49 Electronic Fund Transfer (EFT), Annexure-F 54 END OF THE TENDER DOCUMENT. ---
Page 3 of 54
CHAPTER-01
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
TOP SHEET
Office of the Senior EDPM, M.I.S. Centre, Yelahanka, Bangalore – 560 064.
Tender for Software Development for RWF’s Intranet Business Application (IIMS LAN) - Upgradation
Tender No. RWF/MIS/SD(IIMS LAN)/556 Dated.29.12.2018
Place of Dropping Tender. Sr. EDPM’s Office, M.I.S. Centre, Rail Wheel Factory, Doddabalapur Main Road, Yelahanka, Bangalore – 560064.
Type of Offer. Open Tender.
Date from which Tender Document will be available. 02.01.2018 :from 09.00 hrs to 16:00 hrs.
Last Date for Submission of “Proof 01.02.2019. from 09.00 hrs to 15:00 of Concept.” hrs.
Last Date and Time of Submission 01.02.2019. at 15:00 Hours. of Tender.
Date and Time of Opening of 01.02.2019. at 15:30 Hours. Tender (Bids). Earnest Money Deposit. Rs. 70,460/-.
Cost of Tender Document. Rs. 2,625/- (inclusive of GST @ 5%).
Estimated Cost of Work. Rs. 35.23 Lakhs (inclusive of GST).
Details are also available at http://www.rwf.indianrailways.gov.in
Page 4 of 54
CHAPTER-02
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064 CHECK SHEET TO BE COMPLIED ALONG WITH TENDER DOCUMENT Sl. No. Item Complied Yes No
1. Earnest Money Deposit submitted along with Technical Bid
2. Submission of Soft & Hard copy of “Proof of Concept (POC) along with “Technical Bid” 3. Signature & Seal affixed on all pages of Tender Document
4. Schedule of Rates – Component wise Break-up; Total - In Numericals and in Words furnished, vide Rate Schedule-A & Sum Total along with “Financial Bid”
5. Deviation(s), if any, furnished, Annexure-C along with Technical Bid 6. Declaration of Compliance, Annexure-A along with Technical Bid 7. Declaration of Familiarisation of work, Annexure-B along with Technical Bid Note that Except “Rate Schedule A ”, everything should be submitted along with “Technical Bid”.
Contd. On Next Page
Page 5 of 54
TECHNICAL BID CHAPTER-03
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
1.BACKGROUND:
Rail Wheel Factory, situated in Yelahanka, Bangalore is in the business of manufacturing world class railway Wheel, Axles and Wheel Sets. The products are primarily meant for the consumption of the Indian Railways. They are also sold to indigenous private wagon builders. An export market also exists.
Rail Wheel Factory or RWF in short works directly under the Ministry of Railways, Government of India.
The Web based Business Application which caters to every aspect of the organization is a highly customized and home-grown product. It is known as Integrated Information Management System and works on an Intranet LAN. Hence, its variable nomenclature is IIMS LAN. In its initial days, it was written in COBOL and run on a Main Frame Computer. A transition was made to FoxPro, from which it was brought on to Microsoft Windows platform. Since, the move from FoxPro to Windows was made in the very early days of Microsoft network and server operating system, some of the tell-tale marks of its historical legacy has been carried over. Nonetheless, the Business Application is a very robust, comprehensive and tightly integrated system, measuring up to any modern ERP in its scope, versatility and user-friendliness.
The Business Application, IIMS LAN, comprises of discrete and tightly integrated modules.
RWF is making a serious bid to shed off the Business Applications’ legacy status and migrate to a modern platform, through work accomplished by means of this tender. 2. Mode of Tendering: Open Tender is invited with TWO PACKET SYSTEM namely, “Technical Bid” and “Financial Bid”. The tenderer shall submit both the Packets at a time but separately and clearly indicating which of the Packets is “Technical Bid” & “Financial Bid”. First the Technical Bid shall be opened and evaluatied and if found Technically Qualified then only their Financial Bid shall be Opened for evaluation. Those tenderers, who do not Qualify in “Technical Bid” are summarily rejected and their Financial Bid shall not be Opened and their EMD shall be refunded. Those tenderers who qualify in the “Technical Bid”, their “Financial Bid” would be opened on specified date. This date will be informed to all the tenderers who qualify in the “Technical Bid”.
2.1 Eligibility Criteria: Details are mentioned in Chapter-V
Contd. On Next Page
Page 6 of 54
3. BRIEF OF BUSINESS APPLICATION MODULES AT A GLANCE:
3.1. MANUFACTURING MANAGEMENT SYSTEM (MMS) Manufacturing Management system (MMS) covers Production Planning activities, Wheel shop, Axle shop. The whole system is on-line and vital manufacturing process information and information related to quality of product is captured at the point of data generation. The queries and reports are generated by users themselves.
3.1.1. Production Planning activities comprises of: Annual production plan entry, Customer details, Sale order entry, WTA demand entry, Product master, Route definition, Bill of material, Work order generation, Raw material requisition, generation and print, Despatch schedule and despatch monitoring.
3.1.1.(A) Wheel Shop consists of Melting Shop, Moulding Shop, Finishing Shop, and Mould Repair Shop.
i) Melt Shop module comprises of:
Furnace, roof and ladle re-lining information, Scrap bin details, Metal charge preparation, Scrap receipt, Heat activity and entry of data pertaining to each heat, Chemistry of molten metal, Consumables usage viz; Electricity used, Liquid oxygen used, High value consumable usage and Breakdown of machinery.
ii) Mould Shop module comprises of:
Wheel cast out of molten metal information, Status of each cast wheel, Usage of molds, tubes, Baking sand, Sand inspection details by MLAB, Mould spray, Sprue wash and hub cutting, Cold process of wheel, Mould transactions, On line mould position, High value consumable usage and Breakdown of machinery.
iii) Wheel Final Process Shop module comprises of:
Inspection of wheel at UT, MPT by Lab staff, Inspection of wheel by final inspection, Yard and quality control inspection, Rework wheels inspection, Wheel machining, Wheel sent to outside agencies for rework, Closure test of wheels by MLAB, Despatch of loose wheels, Daily shop activity details, High value consumable usage and Breakdown of machinery.
iv) Mould Repair Shop module comprises of:
Mould history update, Mould machining, assembly, Introduction of new moulds, Condemnation "of old moulds, Ingate assembly, Mould transfer, Daily shop activity details, High value consumable usage and Breakdown of machinery.
Page 7 of 54
3.1.1.(B) Axle Shop consists of Axle Forge, Axle Machine and Axle Assembly Shop. i) Forge Shop module comprises of:
Bloom supplier, Cast master, Billet cutting and heating Axle forging, Normalising and tempering details, Axle transfer to machine shop, Sample cutting and sending for LAB test, Cast test details from MLAB, Forge hammer details, Daily shop activity details, Axle Rejection details, Wagon details for loading axles, Fuel used in furnace details, High value consumable usage and Breakdown Of machinery.
ii) Axle machine shop module comprises of:
Axle UT testing, Axle MPT testing, Daily shop activity details, Axle rejection details, UT/MPT inspection certificate for loose axles, Loose axle despatch details, High value consumable usage, Breakdown of machinery and, Wagon details for loading axles.
iii) Axle assembly shop module comprises of:
Wheel set details, Wheelset inspection details, Rework of wheelset, Demount of rejected set, Inspection certificates, Dispatch of sets, Daily shop activity details, Breakdown of machinery and Wagon details for loading axles.
Contd. On Next Page
Page 8 of 54
3.2. MAINTENANCE AND SUPPORT SYSTEM (MSS)
This comprises of: 1. Preventive Maintenance of Machinery 2. Metallurgical Test results 3. Vehicle Usage of Road Transport Shop (RTS) 4. Utility shop.
3.2.1. Preventive Maintenance of Machinery module comprises of:
. Generation of preventive maintenance work orders. . Breakdown maintenance, Unschedules maintenance.
3.2.2. Metallurgical test results comprises of:
Sample testing of materials received by stores and other testings and analysis.
3.2.3. Vehicle usage of road transport comprises of:
Vehicle insurance, fitness certificate Fuel usage.
3.2.4. Utility Shop module comprises of:
Water, compressed air, liquid oxygen, HSD received and used details are captured.
Contd. On Next Page
Page 9 of 54
3.3. & 3.4. MATERIALS MANAGEMENT SYSTEM
The Material Management System developed in RWF covers all activities relating to the material management function starting from the generation of indents upto the final accounting of materials. The system provides an interface with the finance system for bill passing and costing.
The software is functionally developed as two applications viz.,
Purchase Management System (PMS) Depot Management System (DMS)
3.3. PURCHASE MANAGEMENT SYSTEM (PMS)
It covers: . Generation of purchase related documents which will reduce the manual work load. . Monitoring of cash liability and foreign exchange commitments. . Extensive query and reporting facilities to cover MIS and statutory requirements. . Current status of demands, tenders and purchase orders. . Information for review of budget proposals.
3.3.1. PRE-ORDER MODULE
This module starts with the receipt of indents (prepared and approved by the indenter) after they have been vetted by finance where the vetting is required and have been certified by the depot, in case of non-stock indents. At the time of registration of demand, based on the demand value and other parameters, the tender type is arrived at;, the likely supplier list is compiled by referring to the trade groups, likely suppliers and purchase order databases. Based on these, the purchase note is prepared. Generating enquiries to suppliers and the preparation of the tabulation statement of the quotations received is the next operation of the pre-order module. '
Based on the tabulation statement provided by the pre-order module, the successful tenderer is decided manually. This decision is passed on to the order module for generating the purchase order.
3.3.2. PURCHASE ORDER RELEASE AND MONITORING MODULE
The purchase order is generated based on the decision on quotations for an enquiry. The data is picked up from the offers and demand databases. The purchase order is printed.
This module will take the enquiry ,and quotation details along with terms and conditions of the order to prepare the purchase order. It provides for PO amendments, extensions, cancellations and reinstatement.
A comprehensive vendor directory is maintained as a part of the purchase system. Apart from the routine data, the details of trade group for which the vendor is registered, the agencies with which registered and the monetary limit etc., are also maintained. This database is used for vendor analysis. Page 10 of 54
3.3.3. PURCHASE MODULE
The module covers indent generation indent registration, quotation entry, Local purchase Day Book Register, Issue register, and Imprest Recoupment.
3.4 DEPOT MANAGEMENT SYSTEM (DMS)
It covers the-
. Generation of SRMs for timely and, sufficient recoupment of stock items. . Information for monitoring the progress of purchase orders. . Generation of receipt related documents for prompt accountal of materials. . Connecting the documents to consignments received. . Information to monitor rejections and recovery from suppliers for rejected materials. . Maintain and monitor purchase and sales suspense accounts. . Accountal of scrap generated and reused. . Extensive query and reporting facilities to cover MIS and statutory requirements.
3.4.1. RECEIPT ACCOUNTAL
It captures despatch advices and railway receipts to track material in transit. It caters to- Monitor the wagon movement in and out of RWF resulting in information about:- The availability of wagons inside RWF. Demurrages payable. Capture details of goods received. This facilitates the monitoring of under tally issues. Prepare inspection demand notes and capture the results of inspection. Generate the rejection advice and monitoring lifting of rejected material. Generate receipt note, taking the receipt details from DBR and the rate details from purchase order.
The following types of receipt transactions are catered to for the transaction ledger:-
Stock Verification. Stock sheet. Receipt against a purchase order. Book Transfer. Returned store. Adjustment to receipts.
3.4.2. ISSUE ACCOUNTAL
This module will provide for accountal of all issue transactions.
3.4.3. SCRAP DISPOSAL
The activities involved are forming of lots, preparing catalogue, entering Page 11 of 54 the auction details and subsequently preparing the documents, such as sale advice, sale order and sale issue note.
3.4.4. INVENTORY CONTROL
This module generates stock recoupment memos and generates reports for aiding in inventory control function. The stock recoupment memos are prepared based on the recoupment calendar, the estimated requirement, covered and uncovered dues. Periodical stock reviews can be done and supplementary SRM's generated if necessary. Contd. On Next Page
Page 12 of 54
1 3.5. FINANCIAL MANAGEMENT SYSTEM (FMS)
The financial Management System caters for the following activities:
1. Bill passing. 2. Printing cheques. 3. Maintenance of Books and suspense Registers 4. Costing and Workshop accounting 5. Budget 6. All other modules
These items of work has been divided into various modules in FMS viz. Bills, Cash and Bank, J.V. and T.C., General Ledger, Suspense Register, Budget; Works Register, Finance and costing and Work shop accounting.
3.5.1. Bills : a) Supplier Bills b) Employee Bills - From PPMS c) P.P. advance/Withdrawals d) Import Purchase Bills (L.C) bills e) Contractors' bills f) Miscellaneous Bills : 1. Vehicle Maintenance bills 2. Typewriter maintenance Bills 3. Petty contract Bills 4. Other Misc. Bills 5. Imprest Bills 6. Telephone Bills 7. Electricity Bills 8. Water bills 9. Advertisement Bills 10.Air travel Bills
The bills entry and passing is synchronised with the PMS and DMS systems as far as Supplier Bills are concerned wherein validations in regard to terms and conditions in purchase order is made while passing the bills. After bills are entered into the respective files, they are posted to the co6 register and then to co7 registers from where later the cheque is printed. In case of payroll bills these records are transferred from PPMS to FMS after the payroll bills are printed.
3.5.2. Books and Bank module:
Once the CO7s are printed by respective sections, the data then accumulated for printing the cheques, for each bill. The cheques are printed for each bank in the respective pre-printed cheque stationery at the same time the Cheques and Bills register is also posted. The books and bank module deals with the following:
a) Daily cash book b) Printing of cheques Page 13 of 54 c) Maintenance of Cheques and Bills register d) Posting of Daily cash receipts by Divisional Cashier and the remittance of cash/cheques received by him into bank. e) Posting of unpaid wages by the cashier f) Printing of cashier's MCR ledger; Challans for Bank remittances, and the PMR register.
3.5.3. General Ledger Module:
The ledger module deals with the compilation of various ledgers maintained in the Books section. This consists of : a) General Ledger b) Approximate Account Current c) Monthly account current d) PCDO e) and other various registers/statements printed at the end of the month and at the end of the year etc.
3.5.4. J.V. and T.C. Module
J.V are prepared in two ways, one is generated from system viz. JVs for transfer transactions are generated from T.Cs and stores suspense J.V. is generated from the DMS transactions for receipts and issues. .
T.Cs (Transfer Challans) from other railways and TCs to others railways from RWF are posted to system to maintain the TC register both in Books section and Stores Accounting section.
The J.Vs are finally merged with the FMS transactions for bills etc. for generating monthly/annual Reports viz. Account current, approximate account current etc.
3.5.5. General Leger Module
The general Ledger is a batch mode processing module where the month end reports are generated by the books section. This process updates various registers, which are required to be maintained in books section viz. General Ledger, MCR Ledger etc.
3.5.6. Suspense Register:
This module has the following: a) Purchase suspense, b) import Suspense, c) Railway Suspense d) Sale Suspense, e) DGS & D suspense, f) Deposit – X, g) Deposit stores, h) Employees Suspense – Unpaid wages, Security Deposits, with-held amount from DCRGs etc.
3.5.7. Costing and workshop Accounting Module.
The costing and workshoping module has been maintained as a sub-system to FMS in a separate directory as WAS in vall: of FA server. This is also basically
Page 14 of 54 a batch mode processing system and takes the data from FMS, DMS and MMS for processing at the closure work orders every month end. It generate various Ledger viz. Labour subledger, Misc Subledger, Cost sheet and other supporting statements.
3.5.8. Budget:
The budget module deals with the posting of production programme, and other parameters required to generate the general budget for WMS and Stores. Other departments are posted through separate screens by books section. Contd. On Next Page
Page 15 of 54
3.6. PERSONNEL AND PAYROLL MANAGEMENT SYSTEM (PPMS)
The Personnel and Payroll Management system is designed to cater for the requirement of online process of personnel information, payment of wages and other emoluments due to the personnel working in Rail Wheel Factory and to maintain necessary records regarding personnel info and payment details. The Personnel Management System is divided into the following 4 sub modules.
1. Personnel Management System 2. Payment (Compensation) Management System 3. Provident Fund 4. Attendance Recording Management System (ARMS)
3.6.1. Personnel Management System
A. Career Events: All the career events pertaining to an employee like Promotions, Demotions, Pay Fixations, Transfers within RWF, etc, are done in this module. The system takes care of events from the noting stage to the office order generation stage. The noting number and office order numbers are auto generated by the module, which is used as the ref. in all further transactions. This module is handled by ACCOUNTS Department for their own staff and staff of MIS Centre. For all other departments the Personnel department does it. The Taken Charge Date for events like promotions, transfers etc., are done by the respective departments. The effect of these events into payroll is confirmed by CEBS section in a separate option under Payment (Compensation) Management System.
B. Leave Accounting: This module takes care of accounting all types of leave for which an employee is eligible. The module does leave crediting half yearly for LAP & LHAP and annually for CL. Annual Statements are generated for the purpose of S.R. Book & individual copy. The Qualifying service for person is also determined. This module also serves the purpose of attendance for Payroll for non-punching staff. This module is distributed to all the departments. This module has interface with Payment(Compensation) Mgt. System.
Each individual employee is given access to generate Leave application online and sanction/updation is done online by the departments concerned. This process updates the leave balances automatically.
C. Quarters: This module caters to allotment, occupation, vacation details and other fixed charges maintenance. Priority registers are maintained pool wise. This module is distributed to all the departments. The civil dept. maintains the occupation & vacation details and other fixed charges. This module has interface with Elec. Energy module and Payroll Processing module.
All the employees are having provision to apply for quarters online.
D. Loans Sanctions: All loans/advances (except P .F.) for an employee is processed in this module. Priority registers are maintained for loans of vehicle &house building. The Sanction order is generated by the system. This module is
Page 16 of 54 handled by AlCs & Personnel dept. The CEBS section generates the necessary bills for all loans/advances. Normally the Festival advance is paid through Payroll. This module has interface with Payment (Compensation) Mgt. System & FMS System.
All loans and advances forms are available online for entry and print by individual employees and to submit the same for sanction.
E.Awards: The Noting for approval & memorandum for the awards (like Rly. week awards, Spot awards) are generated by this module. The memorandum is meant for service register & individual copy. The necessary bills are also generated by the system for payment. The details of the awards are kept permanently for future queries. .
F. Book of Sanctions: The various sanctions of posts dept. wise to RWF is maintained in this module. The module generates periodically Scale Check & Cadre Check reports with the posts operated.
G.Personnel Data: Separate modules are available for Family particulars, Address (Permanent & Temporary), Educational Qualifications, and Medical Tests. All the data pertaining to each employee is collected in this module which includes Bank Details, Aadhar Number, Mobile Number, Children Education details and study certificate details. Family particulars captured here is having interface with pass module for issue of scholar pass.
H. Training: All the training particulars of employees are captured in this module. This module is distributed to both Personnel & Accounts depts.
I. Statement 40: Every year compiled annual statements on Pay, DA, TA, OT', Bonus, and Advances etc. with Group-wise & dept. wise with various combinations are to be sent to Railway Board. This module produces the relevant consolidated data for generation of these ST40 reports.
J. Grievance Monitoring: This module captures online the grievances of staff under different classifications. The reprisal measures done by the welfare section will also be captured online for query by the complainant. .
K. Group 'A' Office Orders: In this module all posting orders related to Group 'A' officers of IR are captured in a concise form and is given as a online Query. The details will be kept online for about a month.
L. Pass and PTO: This module consists of data capturing pertaining to All Previlege Passes and PTOs, annual credits, and printing. Contd. On Next Page
Page 17 of 54
3.6.2. Payment (Compensation) Management System
A. O.T. Module:This module caters to the requirements of factory overtime for artisans and supervisory staff. This module has interface with ARMS System and Incentive module for punching staff and Payroll processing module. This module is distributed to Time Office for Punching staff and all other departments for non- punching staff.
B. Incentive: This module determines the incentive rates for Wheel and Axle Shops depending on the monthly production figures, idle hours, G.A. hours and O.T. hours. This module has interface with Arms System, Overtime and Payroll processing modules. PCO and Costing section of Accounts department handle this module.
C. Elec. Energy:This module caters to the needs of electrical dept. for energy consumption requirements of RWF quarters. This module has interface with Quarters module and Payroll processing module. This module is distributed to Electrical department.
D. Miscellaneous Earnings and Recoveries: This module caters to the various types of earnings like T.A., Honorarium, Educational Assistance, Hazardous allowance etc. and recoveries like Telephone Charges, Tools Charges, Vehicle hire charges etc. of employees. The module generates the memorandum. The ef1ect of these into payroll is confirmed by CEBS section of accts. in a separate option. The module is distributed to all departments.
E. HOER OT/NDA module: This module facilitates capture of HOER OT of drivers and NDA of non-punching staff The module generates the memorandum. The effect of these into payroll is confirmed by CEBS section of accounts in a separate option. The module is distributed to all departments.
F. Annual increments module: This module facilitates drawl of annual increments. Every month a table of employees due for increment is generated. Personnel, Accounts and RPF do review. All increments approved are taken into effect during payroll processing and relevant tables are updated.
G. Payroll processing module: All the payroll processing program modules are handled in this module. The programs are grouped according to the category of staff being processed viz. Officers, Supervisory and Ministerial (incl. Gr. 'D'), Artisans and RPF. The processing is done module by module with the sequence of operations controlled by a driving control file. The module is distributed to CEBS section of Accts and RPF.
H. Leave regularization arrears (supplementary payroll): The module calculates arrears for previous 1 month, payable/recoverable, due to leave regularization done after payroll processing. The module is distributed to CEBS section of Accts and is made a part of payroll processing module. .
I. Supplementary Bills module: This module caters to the supplementary payments like awards, pay arrears, subsistence allowance, T.A. and Pay Page 18 of 54 advance, Audit and RDSO staff' payments etc. C07 is generated by the system. This module has interface with Awards, Misc. Earnings and Recoveries, HOER/NDA and Loan modules. This module also has interface with FMS system..
J. Loans and Advances monitoring module: This module monitors the recoveries of loans and advances given by Railways. This module reconciles all the recoveries effected thro' salary, supplementary bill, cash and recoveries from employees on deputation. Monthly ledgers are printed as a statutory requirement of Accounts Code.
K. Income Tax module: This module calculates the ,income tax payable for each employee based on the earnings already paid and future expected earnings for the remaining period of financial year and the declared savings. A separate calculation sheet is prepared for each employee for verification and declaration of savings by each employee. The module also generates form 16 for Income Tax returns filing. Form 24 data is generated quarterly and uploaded to income tax website. This module is distributed to CEBS section of Accts. and RPF.
L. D.A. arrears module: This module facilitates calculation of DA arrears, which is a half-yearly feature. Options to enter pay particulars of transferred employees have been provided. Provision is made for payment thro' supplementary bill or salary depending on requirements. This module is distributed to CEBS section or Accounts and RPF.
M. Productivity Linked Bonus (PLB) module: This module facilitates calculation of Productivity Linked Bonus, which is an annual feature. Options to enter pay particulars of transferred employees have been provided. Provision is made for payment through supplementary bill. There is also an option for employees to credit partial or full amount to VPF. This module is distributed to CEBS section ofAccts.
3.6.3. Provident Fund:
This module caters to the requirement of Provident Fund account maintenance of employees. Every month the PF master is updated with transactions after the monthly ledger is generated and is tallied with the cashbook. This module along with the annual ledger also calculates the annual interest. Every year PF slip' containing the PF account, with all the PF transactions along with the interest, is generated for distribution to employees. . This module has interface with FMS system for PF advance bill passing, Supplementary bills and Payroll processing modules for transactions capturing. This module is distributed to PF section.
Different types of provident fund drawl applications are provided to individual employees to enter the same online and track the progress of their applications.
3.6.4. Attendance Recording Management System (ARMS) This module, which has been developed in-house, determines the attendance of all the punching staff directly from the punches made and based on their shift bookings. This module also determines the G.A. hours for the purpose of incentive calculation. This module has interface with over time, Incentive and
Page 19 of 54
Payroll. . Time Office handles this module.
The module fulfils the requirements of Mechanical Code. The details of the system are explained below.
A. Shift Attendance:
As per the provisions (Mech. Code 226), for every shift, within 1 hour of the commencement of shift, the shift attendance is being processed. This serves the purpose of informing the Shop In charge, who all have punched for duty and who are absent for the shift. In case somebody has punched and not reported for duty the shop in charge will have to take necessary action. .
B. Daily Attendance:
Everyday the attendance for the previous day is generated after all the four shifts are over after 06.30 a.m. The full day attendance is determined by considering all the valid four punches (Viz. shift in, Lunch out, Lunch in and Shift out).
C. Weekly Attendance, Periodical attendance reports:
Every week, the weekly attendance is generated combining the information of attendance in the ARMS module and leave postings in the Leave module. These are circulated for incorporating corrections regarding CR, OD etc.
Fortnightly and monthly attendance statements are, also generated, for similar purpose. Monthly Statement is kept as a permanent record.
D. Shift Roster generation:
The system maintains the shift bookings of all the punching staff. The system generates the shift roster for the subsequent week. The shift roster for all the shops for subsequent week is printed and circulated for carrying out changes in the bookings of any employee.
E. Monthly processes.
The monthly attendance/absence statement for punching staff is generated depending on the schedule of payroll process. This statement is to be printed and submitted to the Personnel/ Accounts Branch in time. The monthly incentive processed after this process. Contd. On Next Page
Page 20 of 54
3.7. Payroll Process Applications
Payroll is processed by the following programmes, which are essentially executables. Web-based application posed many problems in the initial stages of development and were therefore, abandoned. Visual Basic 7 and 6 have been used for coding. The database remains the same as for all other IIMS Applications.
The process is done sequentially in the same order as shown in the table below. There are three occasions when the programme is executed. Employees are divided into pay categories, viz., 1, 2, 3 &, 5. A supplementary process is also run which is marked S, in the table below. Different allowances may either be commonly applicable to all categories or otherwise.
VB 7 processes: Payroll Process of all Categories - Officers, Ministerial Staff, Railway Protection Force, Technical Staff Sl. Sequ- Name of Categories Description of Process No. ence Process applicable ID 1. 01 PPSTART 1/2/3/5 PROCESS START UP 2. 02 PPSYS01 1/2/3/5 UPDATE WAGE PERIOD (SYS FILE) 3. 03 PPCRUP1 1/2/3/5 UPDATE INCREMENTS TO CAREER EVENTS* 4. 04 PPCRUP2 1/2/3/5 UPDATE CAREER EVENTS 5. 05 CO7UPD1 2/3/5 UPDATE CO7 BOOK DATE 6. 06 SPLVUP S SUPPLEMENTARY LEAVE UPDATION 7. 07 SPROC05 S SUPPLEMENTARY ATTENDANCE SUMMARY CREATION 8. 08 LVREGPRO S EMPLOYEES LEAVE REGULARIZATION; ARREARS INDICATION 9. 09 SPAYWAP S SUPPLEMENTARY NETT PAY CREATION 10. 10 PPRTM 1/2/3/5 STOP PF RECOVERY BEFORE RETIREMENT 11. 11 MUSTCREA 1/2/3/5 MUSTER ROLL CREATION 12. 12 PROC2 2/5 GATE ATTENDANCE HOURS UPDATION 13. 13 GATEPASS S PERSONAL GATE PASS HOURS UPDATION 14. 14 PPLVUP 1/2/3/5 LEAVE UPDATION 15. 15 ATDCORR 1/2/5 ABSENCE UPDATION FROM ARMS/18th 16. 16 PPLV011 1/2/5 ABSENCE FROM PUNCHING/18th TO LEAVE 17. 20 PPEL06 1 ELECTRICITY UPDATE 18. 21 PROC14 1/2/3/5 ADD PENDING RECOVERIES OF LAST MONTH 19. 22 HSERENT 1/2/3/5 HOUSE RENT UPDATION 20. 23 PROC04 2/5 PREVIOUS MONTH’S NDA 21. 24 FINLVUP 2/5 LEAVE UPDATION – FINAL 22. 25 PPSUPINC 2 SSE/SE’S INCENTIVE CREATION 23. 26 PPMED S DELETE EARNINGS DEDUCTIONS LEAVE_REG FROM PPMED 24. 27 PROC05 1/2/3/5 ATTENDANCE SUMMARY CREATION 25. 28 GRPUNIT 1/2/3/5 GROUP UNITS UPDATION TO ATTENANCE
Page 21 of 54
26. 29 INCEREPL 2/5 INCENTIVE UPDATION 27. 30 PAYPWAPN 1/2/3/5 NET PAY CREATION 28. 32 PROC11N 1/2/3/5 CARRY FORWARD RECOVERIES 29. 34 MODRATE 1/2/3/5 MEMORANDUM OF DIFFERENCE – BASIC PAY 30. 35 MODDIFF 1/2/3/5 MEMORANDUM OF DIFFERENCE – PERCENT 31. 36 PROC132N 1/2/3/5 CO7 CREATION 32. 37 PPOT 5 OT FILE UPDATION 33. 38 PPALLOWP 5 NDA/OT/TA UPDATION – PAYROLL 34. 39 PPALLOWS 5 NDA/OT/TA UPDATION – SUPPLEMENTARY 35. 40 PPCLOS 5 MONTHLY CLOSE UP PROCEDURES 36. 41 PROC12 1/2/3/5 UPDATE LOANS RECOVERED 37. 42 PPPF02 1/2/3/5 UPDATE PF TRANSACTION – PAYROLL 38. 43 PPPFtsup 5 UPDATE PF TRANSACTION – SUPPLEMENTARY 39. 44 PPIT01 1/2/3/5 INCOME TAX FILE UPDATION – PAYROLL 40. 45 PPITSUP 5 INCOME TAX FILE UPDATION – SUPPLEMENTARY 41. 46 RBEXPUP2 5 R.B.EXPENSE FILE UPDATION – PAYROLL 42. 47 RBEXPUP3 5 R.B.EXPENSE FILE UPDATION – SUPPLEMENTARY 43. 48 PPTCPAY 5 UPDATE TRANSFER CREDITS FILE FROM PAYROLL 44. 49 PPTCSUP 5 UPDATE TRANSFER CREDITS FILE FROM SUPPLEMENTARY 45. 50 PPSAL01 5 UPDATE SALARY REGISTER – PAYROLL 46. 51 PPSAL02 5 UPDATE SALARY REGISTER – SUPPLEMENTARY 47. 52 PPSTMN 5 MONTHLY STATISTICAL FILE GENERATION 48. 53 PPSTSUP 5 STATISTICAL FILE UPDATION FROM SUPPLEMENTARY 49. 54 PPIN01 S CREATE AUTO INCREMENT FILE** 50. 60 CO7UPD S UPDATE CO7 BOOK DATE *Done twice a year, January & July **Not being executed presently
Contd. On Next Page
Page 22 of 54
VB 6 processes: Payroll related Process of all Categories - Officers, Ministerial Staff, Railway Protection Force, Technical Staff Sl. Name of Categories Description of Process No. Process applicable 1. PAYSLIP 1/2/3/5 Output is a text file; process is run every GENERATION month for every pay bill category. 2. PAYBILL 1/2/3/5 Output is a text file; process is run every PRINTING month for every pay bill category. 3. PF STATEMENT 1/2/3/5 Output is a text file; process is run annually. PRINTING 4. SQLDBF 1/2/3/5 Out is exported in Microsoft Excel format; process is run every month for every pay bill category. 5. TIME OFFICE 5 Gate Attendance Punching is downloaded ATTENDANCE into tables and processed further for inclusion in pay bill.
Contd. On Next Page
Page 23 of 54
3.8. Hospital Management Information System
3.8.1. Existing Architecture: Hospital Management Information System (HMIS) was developed long after the previously described Business Application modules were in use at RWF. Therefore, it has different architectural features.
HMIS is also a Web based system. The system allows precompiled sites to be updated. It uses fixed naming and single page assemblies. The single page assemblies create individual page Dynamic Link Libraries for optimal use of memory and enhanced performance speed. HMIS can be hosted on a Windows based site with IIS 6 or 7 with Dot Net framework 2.0.
Dynamic creation of Menu system is a feature of the system wherein an administrator can create any page and link it to the system by creating a menu for that page. User roles for each page can also be created online. When such changes are made, the entire site need not be copied to the site folder but only the concerned page(s) along with its library needs to be copied.
One point to be noted is that whenever a site update is done, the web config file should not be modified as it contains the system setup information. If the web config file is replaced the site information will be lost and the system may not show up pages for browsing.
HMIS is currently hosted on Microsoft Windows 2003 Server Operating System. It uses Microsoft Visual Studio 2005 and has its own Microsoft SQL 2005 Database.
The system shares other than HMIS database, tables from HR tables, Purchase Management System tables for integration of employee-patient linking, patient-family linking and purchase and indent linking (for Read only).
Reports are Visual Studio Data reports and are printed using XML data source DataSet1.xsd where individual table adapters are defined with identical name as the report name. Reports are printed as PDF reports.
Summary of Hospital Management Information System:
Database Server : Server RWFDBCLUSTER Database Name : HMIS Application Host name : ServerH Front End : Microsoft Visual Studio .Net 2005 Programming Language : Microsoft Visual Basic and Java Script - client side Back End : Microsoft SQL Server 2005
i. HMIS sub modules: Outpatient Inpatient Operation Theatre Lab
Page 24 of 54
Medical Stores Pharmacy Billing Reference to Other Hospitals Occupational Health Emergency Family Health Queries Reports System Management
b. Minor Applications: CARE, Quest, CMS, PMESS, REPS
------Contd. On Next Page
Page 25 of 54
CHAPTER-04
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
BRIEF OF RWF’s IT INFRASTRUCTURE
4. Existing Architecture
4.1. Hardware& Network: 4.1.1. Network: RWF’s in-house Data Centre is the nodal point from which two separate networks fan out to the campus. The campus includes the Administrative Block, Factory, Ancillary Offices and Colonies. One is the Intranet which is the network on which the Business Application runs. The other is the Railnet network, interconnecting pan-India Railways which is also connected to the Internet. These two networks are isolated from each other. 4.1.2. Forest, Domain & Active Directory Services: Each of these networks, have their respective Windows Domain Controllers running Microsoft Windows 2012 Server. Windows Active Directory Services are enabled for User and Computer Authorization, Authentication and On-boarding. The Intranet Domain is called RWFNET.COM and the Railnet/Internet Domain is called WAP1.COM. Computer and User Access Level Control is implemented using Group Policies. 4.1.3. Security:Appliance based Firewall and Gateway is implemented on the Railnet network. Each network has its own Antivirus Server. Server- Client based Symantec End Point Protection has been deployed. Floppy drives, CD/DVD drives and Mass Storage devices have been disabled on all computers in the Intranet domain. 4.1.4. Intranet Serversetup: IIMS/Business Applications are hosted on a Nutanix Hyper Converged Infrastructure. The Nutanix platform consists of 4 Nodes in a 2U rack mounted box. Each Node consists of 10 Core x 2 CPUs, with 1024GB RAM, and 960 GB SSD. 16 x 2 TB SAS Hard Disks are pooled by Nutanix OS across the 4 Nodes which gives, 31TB usable storage. Communication between Nodes is established through redundant Top of Rack Switches. Tape Backup is on Power Vault TL2000 Tape Library aided by a dedicated Backup Server. Primary Domain Controller and Antivirus Servers are hosted on separate rack servers. 4.1.5. Intranet Client Computers: All client computers are joined to the RWFNET.COM domain. Users login with a User Name and Password, which does not have Administrator rights.
Page 26 of 54
4.2. Software Stack: 4.2.1. Intranet Server setup: Nutanix Hyper Converged Infrastructure is setup with Nutanix Operating System which establishes Nutanix Cluster. Upto one Node failure, fault can be tolerated without any deterioration in performance. Connectivity is through 2 x 10 GbE network. 4.2.2. Virtualization: Virtualization of the Nutanix HCI is achieved by use of VM Ware Hypervisor, ESX 5. The main reason for not going with Nutanix’ own hypervisor, Acropolis or any other, is because VMs hosting the Business Application works only with legacy Windows Operating Systems, viz., Microsoft Windows 2K for Applications and Microsoft Windows 2K3 for Database. 4.2.3. HCI Management: Management of the Hyper Converged Infrastructure is achieved using either Nutanix’ Management tool, Prism or with VM Ware VRealize Operations Manager. 4.2.4. Production Support/Subscriptions: Onsite and Remote, OEM support is available for the entire stack with subscription licenses. 4.2.5. Storage Container: Storage Contained is comprised of two VMFS Datastores. These contain all required ISO images, installed on VMs. 4.2.6. Virtual Machines: Currently about 30 Virtual Machines are hosted on the Nutanix Hyper Converged Infrastructure.
4.3. Business Application - Integrated Information Management System: 4.3.1. Major Components: Rail Wheel Factory’s web based, home grown and highly customized Business Application or Integrated Information Management System as its otherwise known, consists of three parts, viz., domain application modules, reports and database. 4.3.2. Major Application Modules: There are 7 major application modules, viz., Manufacturing Management System (MMS), Maintenance and Support System (MSS), Personnel and Payroll Management System (PPMS), Financial Management System (FMS); Material Management System is divided into Purchase Management System (PMS); Depot Management System (DMS) and Hospital Management Information System(HMIS). 4.3.3. Minor Application Modules: The above apart, there are few other smaller application modules viz., CARE, Quest, CMS, File Movement, REPS, PMESS etc.
4.4. Architecture of Major and Minor Application Modules: 4.4.1. Application - Operating System: The Applications mentioned above in paras 4.3.2. and 4.3.3. except HMIS are hosted on Microsoft Windows 2000 Advanced Server Operating System. HMIS is hosted on Microsoft Windows 2003 Server. Due to intrinsic limitations, the Applications are not compatible with any other Operating System. 4.4.2. Application - Browser Compatibility: At present, the Applications can only be accessed by Internet Explorer with the highest version being Page 27 of 54
6.x. Higher versions of Internet Explorer are being switched to compatibility mode. No other browsers are compatible. 4.4.3. Application - Framework: The only compatible framework at present is Microsoft Dot Net Framework 1.x for all applications except HMIS which is on Microsoft Dot Net Framework 2.x. 4.4.4. Application - Development Suite: The development suite at present is Microsoft Visual Studio 2002. The development suite for HMIS is Microsoft Visual Studio 2005. The application code used is Visual Basic. 4.4.5. Application - Maintenance Suite: The maintenance suite used at present is Microsoft Visual Studio 2002.
4.5. Reports Tool: All Applications use Crystal Report 8.0 as the Reporting Tool, while only PMS and DMS use Crystal Report 8.5. Reports are called through Application screens. Stored Procedure and Sub-report methodologies are also used.
4.6. Database: Database is Microsoft SQL 2005 which is hosted on Microsoft Windows 2003 R2 Server.
4.7. Security: Agent based Trend Micro is used as the Antivirus agent for each of the VMs running Microsoft Windows 2000 Advanced Server and Windows 2003 R2 Server on which the Applications and Data Base are hosted.
Contd. On Next Page
Page 28 of 54
CHAPTER-05
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
Technical Evaluation Criteria 5.1 The tenderer should submit the Proof of Concept (POC) in the form of a DVD. The details of POC is mentioned in Para 5.2 below.
5.2 Details of POC:-
1. Bidder should be a Professional or a System Integrator with proven skills and experience in Dot Net and Visual Basic. 2. Tenderers are required to submit a Proof of Concept (POC) in the form of a DVD. 3. POC steps are as follows: a) Tenderers are expected to pay site visits and familiarize themselves with RWF’s IT environment . b) Tenderers shall be provided a soft copy in DVD of sample Business Application code of select ASPX pages, Reports and Data Base as part of the Tender Document together with enhanced workflow approval management system. c) Tenderers are required to demonstrate the domain knowledge and skill by Developing/Converting/Upgrading the sample Business Application codes to work on respective upgraded platforms as specified in the Tender Document. d) Implementation of digital signing should be included as part of POC, as an event trigger using WSS technologies so as to remove dependency on Java compatibility with modern existing browsers e) POC to be completed within a month from the date of commencement f) Screen designs of the POC to be shared with RWF, including the Home Page g) Soft copy of so Developed/Converted/Upgraded code and database shall be produced on a DVD and submitted along with the Technical Bid. This is the first part of POC. h) The second part of the POC shall contain a detailed write up in hard copy, of the major steps of software development proposed to be adopted by the Tenderer, in converting/upgrading the existing (a) Customized, Home-grown Dot Net Business Application, (b) Crystal Reports, (c) Data Base, (d) Operating Systems, (e) Testing, (f) Production Roll-out, (g) Roll-back to existing version if required, (h) Final Production Roll-out, (i) System cleanup and (j) Training to M.I.S. Centre officials. i) The third part of the POC shall contain, a brief write up in hard copy, on best practices, precautionary measures etc., which the Tenderer proposes to make use of, during the course of work related to this tender.
Page 29 of 54
4. POC shall fully cover the sample provided. Incomplete POC shall not be considered. 5. Look and feel of the Business Applications shall be retained to the maximum possible extent, in the upgraded version. 6. No changes shall be permitted to the POC, soft and hard copies after submission.
Contd. On Next Page
Page 30 of 54
CHAPTER-06
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
SCOPE OF WORK (IN BRIEF)
6.1. Works:
(i) “Proof of Concept” of developed/converted/upgraded screens of prescribed sample aspx pages, Crystal Reports and sample Database in Softcopy format is to be produced on a DVD. In this regard, Para-5.2 “Details of POC” should be followed. (ii) Hard copy of methodology proposed to be used for Software Development/Conversion/Upgradation of Application, Reports code and Database. (iii) Hard copy of best practices, precautionary measures proposed to be used. (iv) Conversion of VB 7.x and VB 6.x codes to higher version of VB, compatible with all Windows OS versions. (v) Creation of necessary number of VMs. (vi) The requisite licensed version Software will be provided by RWF for upgradation of the entire Business Applications and Data Base. (vii) Software development, conversion, upgrade of all Application modules. (viii) Uploading and building of IIMS Application modules. (ix) Conversion of Database and hosting on VM. (x) Configuring server permissions and connections. (xi) Testing. (xii) Troubleshooting and rectifying issues. (xiii) Certifying each module for full and faultless operation together with the internal IT team. (xiv) Preliminary Roll out of upgraded Applications for production. (xv) Roll back to existing version of Business Application, in case required, prior to final successful roll out of upgraded Applications for production. (xvi) Final Roll out of upgraded Applications for production. (xvii) Establishing secure data sharing with outside world. (xviii) Full service support for 3 months and three years as warranty periods after successful migration, (xix) Training in Conversion/Upgradation intricacies and Maintenance of Applications/Database to all Officers, SEs and JEs of MIS Centre. (xx) Warranty of 3 years to be furnished by the contractor for Software Applications developed. Contd. On Next Page
Page 31 of 54
CHAPTER-07
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
DETAILED SCOPE OF WORK - TECHNICAL SPECIFICATIONS & DEPLOYMENT ARCHITECTURE FOR SOFTWARE DEVELOPMENT/CONVERSION/UPGRADATION OF IIMS LAN – Part I
7. Upgraded Architecture of Intranet 7.1 Hardware & Network: 7.1.1 Network:The Network topology, switching, distribution and isolated structure will remain as is. 7.1.2 Forest, Domain & Active Directory Services: The Intranet Domain, RWFNET.COM will remain as is. 7.1.3 Security:The Intranet Domain RWFNET.COM is to be made ready for exchange of data with outside world, through secure means and utilization of existing Firewall in consultation and co-operation with the firm, who are providing support service for RWF’s Data Centre setup. 7.1.4 Intranet Server setup: Microsoft’s extant license policy for Windows 2016 Server Standard OS is 8 Cores x 2, per license. Totally 80 physical cores are available on Nutanix HCI. Out of this, licenses for 32 Cores are available with RWF already. For the remaining 48 Cores, 3 licenses of Microsoft Windows 2016 Server Standard OS will be procured and provided by RWF. With the help of RWF’s internal IT team, successful tenderer will be required to create space as needed on the Nutanix HCI, for the purpose of hosting new VMs with Windows 2016 Server Standard on which the upgraded IIMS Application and Database are to be hosted. 7.1.5 Intranet Client Computers: No changes are required and the current setup will remain as is.
7.2 Software Stack: 7.2.1 Intranet Server setup: Nutanix Operating System, Cluster and Network will remain as is. 7.2.2 Virtualization: Virtualization of the Nutanix HCI by use of VM Ware Hypervisor, ESX 5 will remain as is. 7.2.3 HCI Management: Management of the Hyper Converged Infrastructure using either Nutanix’ Management tool, Prism or with VM Ware VRealize Operations Manager will remain as is. 7.2.4 Production Support/Subscriptions: Onsite and Remote, OEM support as is available for the entire stack with subscription licenses, will remain with the firm providing services already. Successful bidder, working in co-operation with the firm providing support service, shall provide full support for their portion of Upgraded IIMS LAN deployment, to RWF’s IT team, for 3 months from the date of successful production roll out of the upgraded solution. 7.2.5 Storage Container: With the help of the firm providing support, the successful bidder shall carve out required storage from existing VMFS Datastores.
Page 32 of 54
7.2.6 Virtual Machines:New VMs are to be created, configured and used for hosting upgraded Application and Database Servers. The currently running 30 Virtual Machines will be suspended during trial and final roll out of the upgraded solution and will be retired and removed, by the successful bidder between the 25th and 30th day of their post production support time.
7.3 Business Application - Integrated Information Management System: 7.3.1 Major Components: The upgraded solution, when deployed for use will have the same look and feel as the currently used web based, home grown and highly customized Business Application. The page scheme, style, colour, layout, radio buttons, dropdown lists, menus, sub-menus etc., shall be retained as is for all aspx pages and reports. Only the code behind, Database and its OS stack need to be upgraded. However, jQuery, Ajax or client side scripts/validations may be introduced in event handling to improve performance and reduce load on the server. 7.3.2 Major Application Modules: The current scheme of 6 major Applications, viz., MMS, MSS, PPMS, FMS, PMS & DMS shall remain as is. 7.3.3 Minor Application Modules: The current scheme of minor applications like CARE, Quest, CMS, File Movement etc., shall also remain as is. 7.3.4 Hospital Management Information System: HMIS shall continue to run independently with its own Database. 7.3.5 Pay Roll Process Application: Pay Roll Process and related applications which are not Web based and currently in VB.Net 7.x and some which are in VB.Net 6.x are compatible only with Windows 2000 OS. These are to be upgraded to a higher version of VB.Net and made compatible with all higher versions of Windows Operating Systems.
7.4 Architecture of Major and Minor Application Modules: 7.4.1 Application - Operating System: The upgraded Applications mentioned above in paras 7.3.2. and 7.3.3. are to be hosted on Microsoft Windows 2016 Server Standard Operating System. Thus, the current intrinsic limitations of not being able to scale with upgrades of OS releases will be overcome. 7.4.2 Application - Browser Compatibility: The present limitation of accessing Business Application only with Internet Explorer version 6.x needs to done away with and the developed/upgraded Application should ideally be made browser independent and be made compatible with all popular browsers, like Internet Explorer 11.x or above, Edge, Chrome, Firefox, Safari, Opera etc. 7.4.3 Application - Framework: The highest Microsoft Dot Net Framework version is the ideal and the minimum shall be Dot Net Framework 4.x. 7.4.4 Application - Development Suite: The development suite needs to be upgraded to Microsoft Visual Studio 2017 Pro Sub MSDN Edition. The application code used in the upgraded version will be the intrinsically built in version of Visual Basic. 7.4.5 Application - Maintenance Suite: The maintenance suite needs to be upgraded to Microsoft Visual Studio 2017 Community Edition.
Page 33 of 54
7.4.6 Reports Tool: Reports shall be upgraded to Crystal Reports Version 13.0.2000.0. All reports shall retain the same layout as in current deployment. Stored Procedure and Sub-report methodologies currently used need to be carried on and implemented successfully in the new solution. Certain reports are generated as text reports. The code behind needs to be upgraded to the technically highest feasible version and the same output with the same layout needs to be adhered to.
7.4.7 Database: The Database will have to successfully ported to Microsoft SQL 2017 Enterprise and hosted on Microsoft Windows 2016 Server Standard.
7.4.8 Security: Agent based Trend Micro Deep Security is to be dispensed with and the newly deployed VMs shall use Symantec End Point Protection as Client machines.
7.5 Hospital Management Information System: 7.5.1 Application - Operating System: The upgraded HMIS Application is to be hosted on Microsoft Windows 2016 Server Standard Operating System. Thus, the current intrinsic limitations of not being able to scale with upgrades of OS releases will be overcome. 7.5.2 Application - Browser Compatibility: The present access of the Business Application only by Internet Explorer version 6.x needs to done away with and the Application should be compatible with all popular browsers, like Internet Explorer 11.x or above, Edge, Chrome, Firefox, Safari, Opera etc. 7.5.3 Application - Framework: The highest Microsoft Dot Net Framework version is the ideal and the minimum shall be Dot Net Framework 4.x. 7.5.4 Application - Development Suite: The development suite needs to be upgraded to Microsoft Visual Studio 2017 Pro Sub MSDN Edition. 7.5.5 Application - Maintenance Suite: The maintenance suite needs to be upgraded to Microsoft Visual Studio 2017 Community Edition. 7.5.6 Reports Tool: Reports in Hospital Management Information System using RDLC shall be converted to highest compatible version. Reports are called through Application screens. Stored Procedure and Sub-report methods will have to be made to work in the new upgraded environment, if & where required.
7.6 Database: The Database will have to successfully ported to Microsoft SQL 2017 and hosted on Microsoft Windows 2019 Server Standard.
7.7 Security: Newly deployed VMs shall use Symantec End Point Protection as Client machines.
7.8 Payroll Process Application: Entire code in VB7 and VB6 needs to be converted to a higher version and be made compatible to work in any Windows OS environment.
Page 34 of 54
Snapshot of Major & Minor Application System Sl. Existing Existing version Version to be No. Infrastructure Upgraded to Component
1. Operating System Microsoft Windows Microsoft Windows 2000 Server 2019 Server Standard or higher 2. Dot Net Framework 1.x 4.x 3. Development Tool Visual Studio 2002 Visual Studio 2017 or higher 4. Programming Language Visual Basic Visual Basic, highest version technically feasible 5. Application Management Visual Studio 2005 Visual Studio 2017 Tool 6. Reporting Tool Crystal Reports 8.0 Crystal Reports & 8.5 13.0.2000.0 or higher 7. Database Server OS Microsoft Windows Microsoft Windows 2003 Server 2019 Server Standard Enterprise or higher 8. Database Microsoft SQL 2005 Microsoft SQL 2017 or higher 9. Executables VB 7 & VB 6 Technically highest feasible versions of VB
Snapshot of Hospital Management Information System Sl. Existing Existing version Version to be No. Infrastructure Upgraded to Component
1. Operating System Microsoft Windows Microsoft Windows 2003 Server 2019 Server Standard or higher 2. Database Microsoft SQL 2005 Microsoft SQL 2017 or higher
3. Front End Microsoft Visual Microsoft Visual Studio .Net 2005 Studio .Net 2017 4. Dot Net Framework Version 2.x Version 4.x 5. Reports Visual Studio RDLC To be converted to (Report Definition highest compatible Language Client version Side)
Page 35 of 54
Estimated sizing of the work under Part-I Sl. Business Estimated Sizing No. Application Module with Reports No. of No. of Call- ascx Java DLL ASPX Reports able script screens func- tions 1.a MMS Application 330 3 67 13 304 1 1.b MMS Queries 91 146 62 5 - 9 2. MSS Application 371 230 70 1 110 - 3. PPMS Application 689 547 63 - 164 - 4. FMS Application 733 647 38 5 162 7 5. PMS Application 264 420 5 1 - 5 6. DMS Application 503 9 6 3 280 - 7. HMIS Application 164 46 3 - - 8 8. All Minor 50 30 - - 35 3 Applications 9. Pay Roll Process Convert VB7 code working on Windows 2000 Application Server to VB code, compatible with all Windows versions 10. Database Move from Microsoft SQL 2005/Windows 2003 to Conversion Microsoft SQL 2017/Windows 2019 Server
Sign and Seal of Tenderer
Contd. On Next Page
Page 36 of 54
CHAPTER-08
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
DETAILED SCOPE OF WORK - TECHNICAL SPECIFICATIONS OF SOFTWARE DEVELOPMENT/CONVERSION/UPGRADATION OF IIMS LAN – Part II
1. Vulnerability Assessment & Penetration Testing (VAPT) - Vulnerability Assessment & Penetration Testing (VAPT) security services need to be performed by the bidder on identifying vulnerabilities in the network, server and system infrastructure. 2. Database roles need to be enhanced with security features 3. OS ticketing to be introduced 4. Database tuning/optimization for performance enhancements 5. Secured SSL support 6. Enhanced Exception handling with monitoring feasibilities 7. Client side validations (wherever necessary) to support enhanced user experience while migrating to latest version 8. 6 Windows/console applications which are developed in (VB 7) also need to be included in the migration process 9. Data storage security 10. Payroll menu restructuring for enhanced user visualization 11. Inline statements to be identified and eliminated in order to avoid SQL Injections. 12. SSO – Single Sign On – for all existing applications 13. Form 16 – Signing to be digitalized 14. HSM (hardware security module) to be introduced to store digital Certificates 15. API development for mobile application 16. For Proof of Concept, necessary source code and DB structure will be shared to Bidder/s. Post approval of POC and successful bid, migration/development activities should be carried out at RWF premises. 17. Post migration together with above mentioned activities, QA activities has to be done jointly (RWF/Bidder) and User Acceptance Testing & Parallel Run to be taken up by RWF 18. Implementation of digital signing should be included, as an event trigger using WSS technologies so as to remove dependency on Java compatibility with modern existing browsers
Contd. On Next Page
Page 37 of 54
CHAPTER-09
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
DETAILED SCOPE OF WORK – WORK FLOW AND ESTIMATED TIME LINES FOR SOFTWARE DEVELOPMENT/CONVERSION/UPGRADATION OF IIMS LAN – Part III
9.1. Works that need to be executed in parallel Sl. Business Estimated Number of weeks for Number of No. Application Time in Assessment of weeks for Module with weeks Outcome by concerned Finalization Reports SE(IT)/RWF and Test after check by Users Testing 1. MMS Application 30 5 2 2. MSS Application 10 3 2 3. PPMS Application 42 4 4 4. FMS Application 42 6 4 5. PMS Application 30 6 5 6. DMS Application 42 5 5 7. HMIS Application 42 4 3 8. Pay Roll Process 10 5 15 Application 9. All Minor 40 4 4 Applications
9.2. Works/Supplies to be done without dependencies on other works Sl. Module No. 1. Creation of required space and VMs on Nutanix HCI 2. Installation of OS, configuring of VMs 3. Self testing of Developed/ Converted/Upgraded Applications and Reports 4. Data Base Conversion 5. Training of RWF’s IT team
Sl. 9.3 Name of Work shall be fully tested, finalized & ready for No. production deployment 1. Development/Conversion/Upgrade of all Business Application modules 2. Development/Conversion/Upgrade of all Crystal Reports 3. Conversion of Data Base 4. VMs with Operating System 5. Build of Applications on host VMs 6. Testing of Integrated New Environment 7. Initial Production Roll-out 8. Final Production Roll-out
Contd. On Next Page
Page 38 of 54
CHAPTER-10
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
SPECIAL CONDITIONS OF TENDER
10.1. SPECIAL CONDITIONS 1. Consortium bidding is not allowed. 2. The currency of the contract shall be for 12 months from the date of issue of Letter of Acceptance. 3. The latest version of General Conditions of Contract (GCC) along with all latest amendments, if any can be downloaded from the site http://www.indianrailways.gov.in and the same are applicable in this tender. 4. A one time extension upto 3 months can be granted, if need be, for completion of the project, upon request by the successful bidder, duly furnishing reasons for the delay. 5. Performance Bank Guarantee and Security Deposit shall be forfeited for reasons of below par performance of quality, quantity or time. The same shall be determined by Sr. EDPM, M.I.S. Centre, Rail Wheel Factory, Yelahanka, Bangalore – 560064.
10.2. SHORT CLOSURE: RWF administration at its discretion reserves the right to short close part or full work of the schedule forming part of the tender without any financial obligations.
10.3 COMPLETION PERIOD:- The successful bidder should complete the work within 12 months. Extension can be granted to complete the work for a further period of 3 months subject to the concrete reason ascertained jointly by the nominated team of MIS Centre and the Contractor. 10.4 WARRANTY:- Software infrastructure - upgraded and rolled out for production, shall have a 3 year warranty furnished and executed by the Contractor.
10.5 Penalty:- Penalty Clause as per GCC is applicable.
10.6. Responsibility of successful Tenderer: 1. As far as possible, carry out the work as per estimated time under Detailed Scope of Work – Part III. 2. Contractor and authorized personnel of contractor have to mandatorily work in the designated premises in RWF and on PCs made available to the contractor by the administration. 3. Copying of source code on any media is strictly prohibited. 4. Submit a report every fortnight to the concerned authorities on the progress of work. 5. Actively seek any technical clarifications and meet on a regular basis for technical discussion with the internal IT team of RWF.
Page 39 of 54
6. Provide infection free soft copy of developed work, whether for testing or deployment. 7. Work closely with the internal IT team of RWF at all stages of development/conversion/upgrade work and for installation of OEM software. 8. Maintain cleanliness of the workspace allotted and PCs provided by RWF. 9. Maintain the PCs’ integrity by not tampering with its components and configuration. 10.Return PCs provided after completion of the work in the same working condition as given initially. 11.The contractor shall be responsible for any breakdowns/disturbance in the normal working of the existing Business Application during the time of creation of space, creation/installation of VMs, build of upgraded applications etc., and work together with the internal IT team of RWF and the firms providing support, to restore normal working in the least possible time.
12.Levy of Conservancy Charges: 13.The Conservancy charges will be levied as applicable from time to time on the Contractor and the present rates are given below:
Type of Average No. of Laborers/ Conservancy CESS tender Workman employed per day, charges to be recovered in RWF premises per month (Rs) Works 1 to 5 145.00 Tender 6 to 10 285.00 11 to 25 717.00 26 to 50 1044.00 51 to 100 1402.00 101 to 200 1760.00 201 to 300 2118.00 301 to 750 2445.00 751 to 1500 4918.00 1501 to 3000 9839.00 3001 & above 19653.00
14.Please Note: Changes in the conservancy charges if any, as revised by the Railways at the time of the execution of the contract shall be applicable.
10.7. RESPONSIBILITIES OF RWF:
1. Monitor the works carried out by the contractor. 2. Make available a conducive atmosphere and infrastructure for smooth and quick operations by the contractor. 3. Provide alternate PCs, switches etc., in case of breakdown of equipment provided.
Page 40 of 54
CHAPTER-11
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
SECURITY DEPOSIT AND PERFORMANCE GUARANTEE
11.1. SECURITY DEPOSIT:
11.1.1. The Earnest Money deposited by the successful bidder with his tender will be retained by the Railways as part of security for the due and faithful fulfillment of the contract by the contractor. The balance to make up the full security deposit being 5% of the contract value shall be deposited by the Contractor in cash or DD in favour of PFA. Provided also that in case of defaulting contractors the Railway may retain any amount due for payment to the contractor on the pending “on accounts bill” so that the amounts so retained may not exceed 10% of the total value of the contract. The security deposit rate of recovery/mode of recovery shall be :- • Security Deposit for each work should be 5% of the contract value. • Security Deposits will be recovered only from the running bills of the contract and mode of collecting SD such as SD in the form of instruments like BG, FD etc., shall be accepted towards security deposit.
11.1.2. Security Deposit shall be returned to the contractor after the successful completion of the Warranty period of 3 years as certified by the competent authority. The competent authority shall normally be the authority who is competent to sign the contract. The Certificate, inter alia, should mention that the work has been completed Certificate for in all respects and that all the contractual obligations have been fulfilled by the contractors and that there is no due from the contractor to Railways against the contract concerned. The contractor along with requisition shall furnish an unconditional and unequivocal No Claim refund of Security Deposit after completion of work and maintenance period. No interest will be payable upon the Earnest Money and Security Deposit or amounts payable to the Contractor under the contract, but Government Securities as prescribed and acceptable towards the above will be payable with interest accrued thereon.
11.2. PERFORMANCE GUARANTEE:
11.2.1. The successful bidder shall have to submit a Performance Guarantee (PG) within 30(thirty) days from the date of issue of Letter of Acceptance (LOA). Extension of time for submission of PG beyond 30 (thirty) days and up-to 60 days from the date of issue of LOA shall be given by the competent authority. However, a penal interest of 15 % per annum shall be charged for the delay beyond 30 (thirty) days i.e. from 31st day after the date of issue of LOA. In case the contractor fails to submit the requisite PG even after 60 days from the date of issue of LOA, the contract shall be terminated duly forfeiting EMD and other dues, if any payable against the contract. The failed contractor shall be debarred from participating in re-tender for that work.
Page 41 of 54
11.2.2. The successful bidder may submit the Performance Guarantee (PG) in any of the following forms amounting to 5% of the contract value:- A deposit of Cash. Irrevocable Bank Guarantee. Government Securities including State Loan Bonds at 5 Percent below the market value. Deposit Receipts, Pay Orders, Demand Drafts and Bank Guarantee Bonds. These forms of Performance Guarantee could be either of the State Bank of India or any of the Nationalized Banks. Guarantee Bonds executed or Deposits Receipts tendered by all Scheduled Banks. A Deposit in the Post Office Saving Bank. A Deposit in the National Savings Certificates. Twelve years National Defense Certificates. Ten years Defense Deposits. National Defense Bonds. Unit Trust Certificates at 5 percent below market value or at the face value whichever is less. Also FDR in favour of PFA/RWF (free from any encumbrance) may be accepted.
11.2.3. A Performance Guarantee shall be submitted by successful bidder after the letter of acceptance has been issued, but before signing of the agreement. This PG shall be initially valid up-to the stipulated date of completion plus 3 months beyond that. In case, the time of completion of work gets extended, the contractor shall get the validity of Performance Guarantee extended to cover such extended time for completion of work plus 90 days. 11.2.4. The value of PG, which will be 5% of the contract value to be submitted by the contractor will not change for variation upto 25% (either increase or decrease). 11.2.5. The Performance Guarantee (PG) shall be released after the physical completion of work based on the “Completion Certificate” issued by the competent authority stating that the contractor has completed the work in all respects satisfactorily. The security deposit shall, however, be released only after expiry of the warranty period and after passing the final bill based on “No Claim Certificate” from the contractor. 11.2.6. Wherever the contract is rescinded, the security deposit shall be forfeited and the performance guarantee shall be encashed. The balance work shall be got done independently without risk and cost of the failed contractor. The failed contractor shall be debarred from participating in the tender for executing the balance work. If the failed contractor is a JV or a partnership firm, then every member/partner of such firm shall be debarred from participating in the tender for the balance work in his/her individual capacity or as a partner of any other JV/partnership firm. 11.2.7. The Competent Authority shall not make a claim under the performance guarantee except for amounts to which the President of India is entitled under the contract (Notwithstanding and/or without prejudice to any other provisions in the contract agreement) in the event of:
Page 42 of 54
i) Failure by the contractor to extend the validity of performance guarantee as described herein above, in which event the Competent Authority may claim the full amount of the Performance Guarantee. ii) Failure by the contractor to pay President of India any amount due, either as agreed by the contractor or determined under any of the clauses/conditions of the agreement, within 30 days of the service of notice to this effect by the Competent Authority. iii) The contractor being determined or rescinded under provision of the GCC, the Performance Guarantee shall be forfeited in full and shall be absolutely at the disposal of the President of India
11.2.8. Bank Guarantees to be submitted by the contractors should be sent directly to the concerned authorities by the issuing bank under Regd. Post Ack. Due.
Contd. On Next Page
Page 43 of 54
DECLARATION OF COMPLIANCE ANNEXURE - A
I/we hereby declare that I/we have fully complied with the pre-requisites and all other conditions of the tender. I/we have submitted Proof of Concept as required in three parts. I/we have obtained the Certificate of Proof of Concept issued by RWF’s administration and have enclosed the same herewith.
.
Sign and Seal of Tenderer
Page 44 of 54
DECLARATION OF FAMILIARIZATION ANNEXURE - B
I/We, ………………………………………………… (Name of tenderer) hereby declare that we have sufficiently associated myself/ourselves with RWF’s IT environment so as to familiarize myself/ourselves with the works specified in this tender.
I/we further declare that I/we possess sufficient domain knowledge so as to accomplish the work of development/conversion/upgradation of RWF’s Business Application without changing the process flow and business logic.
I/we also declare that working in cooperation with RWF’s internal IT team, that we will not hamper the daily working of Business Application during development and testing stage nor cause any undue delays during the time of final production rollout of the upgraded version.
Sign and Seal of Tenderer
Page 45 of 54
DEVIATION STATEMENT ANNEXURE – C
DEVIATION STATEMENT
Proforma of Statement for deviation from Technical Specifications.
Clause No. Deviation Remarks with justification for Deviation
Signature & seal of Contractor
Note: Where there is no deviation, the statement should be submitted duly signed with an endorsement indicating “NO Deviation.” Railways reserves the right to accept/reject the offers with deviations without assigning any reasons thereof.
Sign and Seal of Tenderer
Page 46 of 54
AGREEMENT FOR WORKS ANNEXURE – D
AGREEMENT FOR WORKS
CONTRACT AGREEMENT NO: Date:------
I. ARTICLES OF AGREEMENT made this ___ Day of ______2016, between the “President of India” acting through the Sr. EDP Manager, Rail Wheel Factory, Bangalore herein after called the “Railway” of the One Part and M/s ------herein after called the “Contractor” of the Other Part. II. WHEREAS the Contractor has agreed with the Railway for the performance of the work of “______” set forth in the Schedule here to annexed and in conformity with Specifications and Terms and Conditions hereto annexed and General Conditions of Contract all known as “Contract Documents” AND WHEREAS the performance of the said works is an act in which the public are interested. III. AND WHEREAS the contractor has submitted: a) Bank Guarantee towards Performance guarantee of Rs: /- vide ------Dt. ------issued by ------valid till ------and, b) Security Deposit of Rs………………………. IV. The PG Bond and Security Deposit furnished by the contractor with the tender will be retained by the railways as part of the security deposit for due and faithful fulfillment of the contract by the contractor. V. Bank Guarantee for Performance for the work shall be 5% of the contract value, i.e. Rs.------(Rupees ------only). VI. Security Deposit which shall be deducted from the account bills submitted by the Contractor for the work shall be 5% of the contract value, i.e. Rs.------(Rupees ------only). VII. NOW THIS INDENTURE WITNESSETH that is consideration of the payments to be made by the Railways, the Contractor will duly perform the said works set forth in the said schedules and shall execute the same with great promptness, care and accuracy in a workman like manner to the satisfaction of the Railways and shall complete the same in accordance with the said specifications and said drawings and said conditions of contract and this office subsequent letters all known as contract documents with in the ------period from the date of issue of LOA i.e. on or before ------and will maintain the said works for a period of ------months from the date of commissioning and proving out of “Software Development for RWF’s Intranet Business Application(IIMS LAN) - Upgradation” Solution and will observe, fulfill and keep all the conditions therein mentioned (which shall be deemed and taken to be part of this Contract as if the same has been fully set forth herein). VIII. AND The Railway do hereby agree that if the Contractor shall duly perform the said works in the manner aforesaid and observe and keep the said terms and conditions, the Railway will pay or cause to be paid to the Contractor for the said works on the final completion thereof, the amount due in respect thereof at the rates set forth in the Schedule of Rates & Quantities annexed hereto amounting to a total value of Rs.------/-
Page 47 of 54
(Rupees ------only) as per the details of payment terms in Annexure to SCHEDULE OF RATES & QUANTITIES of the Agreement. IX. It is hereby agreed and declared that all the said specifications and conditions of contract which have been carefully read and understood by the Contractor shall be as binding upon the Contractor and upon the Railway as if the same has been repeated herein and shall be read as part of these presents. X. The cost of Stamp Duty on the Agreement shall be borne by the Railway Administration.
Signature of the Contractor Signature of Sr. EDP Manager, Address: Rail Wheel Factory, For & On Behalf of the President of India Address:
Date: Date:
Witnesses
1. Signature Address
2. Signature Address Sign and Seal of Tenderer
Page 48 of 54
PROFORMA FOR PERFORMANCE BANK GUARANTEE ANNEXURE – E
(To be typed on Rs.200.00 Non-judicial stamp paper)
PROFORMA FOR PERFORMANCE BANK GUARANTEE
Sr. EDP Manager, Rail Wheel Factory. Yelahanka, Bangalore – 560 064.
In consideration of the President of India acting through Sr. EDP Manager, Rail Wheel Factory, Yelahanka, Bangalore – 560 064 hereinafter called “The Railway” having agreed under the terms and conditions of Letter of Acceptance No.______dated ______(hereinafter called the Letter of Acceptance) made between Sr. EDP Manager, Rail Wheel Factory, Yelahanka, Bangalore – 560064 and M/s.______(hereinafter called the said contractor(s) to accept from M/s.______in the form of Guarantee Bond for the due and faithful fulfillment of the Performance Guarantee obligations contained in Para ______of the said Letter of Acceptance for Rs.______(Rupees only). We, ______(hereinafter called the Bank) do hereby undertake to pay to the Railway an amount not exceeding Rs.______(Rupees______only) against any loss or damage caused to or suffered or would be caused to or suffered by the Railway by reason of any breach by the said contractor (s) of the said Letter of Acceptance.
We, ______do hereby undertake to pay the amounts due and payable under this Guarantee without any demur, merely on a demand from the Government stating that the amount claimed is due by way of loss or damage caused to, or would be caused to, or suffered by the Government by reason of any breach by the said contractor(s) of any of the terms or conditions contained in para______of the said Letter of Acceptance of his failure to fulfill the extended Performance Guarantee of the work covered by the Letter of Acceptance for a period of------from ______. Any such demand made on the bank shall be conclusive as regards the amount due and payable by the Bank under this Guarantee. However, our liability under this Guarantee shall be restricted to an amount not exceeding Rs.______(Rupees______only).
We, ______further agree that the Guarantee herein contained will remain in full force and effect during the period that would be taken for the performance of the said Letter of Acceptance, for due and faithful fulfillment of Performance Guarantee obligations and that it shall continue to be enforceable till the Sr. EDP Manager, Rail Wheel Factory, Yelahanka, Bangalore – 560 064, India certifies that the extended Page 49 of 54
Performance Guarantee under the said Letter of Acceptance have been fully and properly carried out by the said Contractor (s) and accordingly, discharges the Guarantee made on us in writing on or before ______, we shall be discharged from all liability under this Guarantee thereafter.
We undertake to pay to the Government any money so demanded notwithstanding any dispute or disputes raised by the Contractor(s) in any suit or proceeding pending before any Court or Tribunal relating thereto our liability under this present being absolute and unequivocal.
The payment so made by us under this Bond shall be a valid discharge of our liability for payment there under the Contractor(s)/supplier(s) shall have no claim against us for making such payment.
We,______(indicate the name of Bank), further agree with, the Government that the Government shall have the fullest liberty without our consent and without affecting in any manner our obligations hereunder to vary any of the terms and conditions of the said Agreement or to extent time of performance by the said Contractor (s) from time-to-time or to postpone for any time or from time-to-time any of the powers exercisable by the Government against the said contractor(s) and to forbear or enforce any of terms and conditions relating to the said Agreement and we shall not be relieved from our liability by reason of any such variation or extension being granted to the said contractor(s) or for any forbearance, act or omission on the part of the Government or any indulgence by the Government to the said contractor(s) or by any such matter or thing whatsoever which under the law relating to sureties would but for this provision have effect of so relieving us.
This Guarantee will not be discharged due to change in the constitution of the Bank or the contractor(s)/supplier(s).
We,______, lastly undertake not to revoke this guarantee during its currency except with the previous consent of the Government in writing.
Dated the ______day of______20
For______(indicate the name of bank)
Note: To be executed on Rs. 200/- non-judicial stamp paper of India.
Sign and Seal of Tenderer
Page 50 of 54
CHAPTER-12
RAIL WHEEL FACTORY, YELAHANKA, BANGALORE – 560 064
FINANCIAL BID
RATE SCHEDULES
Schedule-A Upgradation work Rs 35,23,067/-
Total Par Value of the Contract Rs 35,23,067/-
Schedule–A
Sl. Business Application Module with All inclusive price No. Reports
1. MMS Application 2. MSS Application 3. PPMS Application 4. FMS Application 5. PMS Application 6. DMS Application 7. HMIS Application 8. All Minor Applications 9. Pay Roll Process Application 10. Database Conversion 11. Final Installation, Testing and Production rollout 12. Maintenance for 90 days, post production rollout 13. Paid software supplies (if any), proposed by Tenderer Total Par value Rs 35,23,067/- Tenderer’s % on Par value Total Rupees ------Sign and Seal of Tenderer
Page 51 of 54
PRICES AND PAYMENT
The terms and conditions of prices & payment for the various items of work to be executed under the contract shall be as follows:
12.1 Prices
i. The rate quoted shall be firm and inclusive of all taxes, duties, levies etc. during the currency of the contract and any further extension thereof. ii. The Contractor shall submit the tender schedule of Works under Schedule- “A” with separate rate for Software Development/Conversion/Upgradation of IIMS LAN including and upto the stage of Production roll-out and maintenance period of 3 months. iii. The Contractor shall submit the grand total of Works under Schedule-“A”, which shall determine the final all inclusive bid value. iv. The Contractor shall submit the above said bills to Sr. EDPM/M.I.S. Centre/RWF for the work completed in a month, bi-monthly, half yearly and yearly with the statement indicating the works completed for verifying and forwarding for payment. v. The Sr.Engineer(IT) in charge shall also certify compliance of safety norms/ statutory requirement by the Contractor on the bill, failing which the bill cannot be passed for payment. vi. As the Payment will be made in Electronic Fund Transfer (EFT) mode only. You are required to furnish the EFT particulars as per prescribed format, available in the M.I.S. Centre, if not already done. vii. The Final payment will be made only on submission of No Due Certificate issued by the concerned Sr.Engineer(IT)-in-charge and submission of No Claim Certificate by the Contractor (as per Format).
12.2 Payments: Payment will be made in two (02) stages as follows:
12.2.1 50% payment of the total contract value will be released only after successful development, installation, upgradation, commissioning and completion of the entire work of the contract.
12.2.2 Balance 50% of the total contract value will be released only after successful running of the system for a period of 03 months, after successful completion of the entire development, up-gradation of software as per scope of the contract.
12.2.3 The stage payments will be made only after the issue of Completion certificate of each stage by the nominated Engineer for this purpose.
12.2.4 All the payments will be made against GST invoice only
12.3. Income Tax:
Under Section 194-C of Income tax Act 1961,deduction of 2% or as applicable from time to time will be made from the sums payable under the contract. The Page 52 of 54
Contractor should invariably indicate PAN No. allotted by Income Tax Department, on the bill. By claiming otherwise, claim will not be entertained.
12.4. Goods / Service Tax (GST)
i) Contractors will examine the various provisions of the Central Goods and Service Tax Act, 2017(CGST)/Integrated Goods and Service Tax Act, 2017(IGST)/Union Territory Goods and Services Tax Act, 2017(UTGST)/respective State's Goods and Service Tax Act (SGST) also, as notified by Central/State Government and as amended from time to time and applicable taxes before bidding. Contractors will ensure that full benefit of Input Tax Credit (ITC) likely to be availed by them is duly considered while quoting rates.
ii) The Contractor who is liable to be registered under CGST/IGST/UTGST/SGST Act shall submit GSTIN along with other details under CGST/IGST/UTGST/SGST Act to Railway immediately after the award of contract, without which no payment shall be released to the contractor. The contractor shall be responsible for deposition of applicable GST to the concerned authority. iii) In case the Contractor is not liable to be registered under CGST/IGST/UTGST/SGST Act, the Railway shall deduct the applicable GST from his/their bills under reverse charge mechanism (RCM) and deposit the same to the concerned authority. iv) The Contractor shall submit the bill along with the invoice No. and all other details required under GST Act. v) The payment made by Railways is inclusive of GST.
Page 53 of 54
ELECTRONIC FUND TRANSFER ANNEXURE – F
ELECTRONIC FUND TRANSFER (E.F.T.)
We ______are expressing our consentfor getting our payment directly credited to our Bank Account towards supply of Stores to RAILWHEEL FACTORY( Ministry of Railways), Yelahanka, Bangalore 560 064.
Company’s seal & Authorized Signatory Vendor/Signature’s Code : Name of the Company : Postal Address : Name of the Bank & Branch : Address (with telephone No.) 9 Digits MICR code of the Bank : Account number : Type of Account : Income Tax Pan No. : Signature of Authorized Signature & Date The above account number has been verified and found correct. Bank Seal & Signature
Page 54 of 54