Request for Proposal

Request for Proposal Software Selection For Workload Automation Issue date: 20 th January, 2011 Last date for submission of proposals: 7 th February, 2011

Table of Contents Overview... 4 1 Background... 4 2 Purpose... 4 3 Request for proposal Definitions... 4 Terms of RFP... 6 1 Acknowledgement... 6 2 Proposal Deadlines... 6 3 Format of proposals... 6 4 Further Inquiries and Questions Regarding RFP... 7 5 CHOICe s Obligations... 7 6 Proposal Evaluation... 7 7 RFP Terms and Conditions Applied to Final Contract... 8 8 Terms Binding on... 8 9 Hold Harmless... 8 10 Confidentiality Provision... 9 11 RFP Schedule... 9 12 Sub-Contracting... 9 13 Acceptance of Proposals... 10 14 Evaluation and Selection... 10 15 Liability for Errors... 10 16 Acceptance of Terms... 11 17 Ownership of Proposals... 11 18 Use of Request for Proposal... 11 19 Exception Notice... 11 Proposal Preparation... 12 1 Proposal Format... 12 2 Notification of Changes... 12 3 Changes to Proposed Wording... 12 4 s Expenses... 13 Public Document Page 2 of 43

5 Currency and Taxes... 13 6 Completeness of Proposal... 13 7 Implementation Scope... 13 SUPPLIER QUESTIONNAIRE... 14 1 TECHNICAL QUESTIONNAIRE... 14 1 INSTRUCTIONS... 14 2 Degree of Fit... 14 3 General information of the vendor... 14 4 Technical Functionality... 16 5 Functional Requirement... 16 Annexure A Technical... 17 Customization & Implementation... 17 Product Strategy... 17 Technical Support... 18 Warranty... 19 Technical Architecture... 19 Integration Requirement... 19 Scalability and Performance... 20 DR and BCP... 21 System Administration... 21 Security... 21 Deployment Configuration... 22 System Limitations... 23 Data Control... 23 Annexure B - Functional... 25 Instructions... 25 Business Functionality... 25 Annexure C Commercial Bid Format... 43 Public Document Page 3 of 43

Overview 1 Background Canara HSBC Oriental Bank of Commerce Life Insurance Company Ltd, an Insurance company (hereinafter referred to as CHOICe) has branches and administrative offices spread across the country. As part of its IT initiatives, the company has already deployed various IT applications / products like Core Policy Admin System (PAS), Group Policy Admin System, Websphere Portals, Sales Portal, PeopleSoft, MIS Reporting and other applications systems. To provide workload automation solution for the above mentioned applications as well as the future IT initiatives, CHOICe requests for proposal for Workload Automation solution on Fixed Cost basis. 2 Purpose The purpose of this RFP is to inform the potential bidders of a business opportunity and to solicit proposals for Workload automation solution. Based on the review and evaluation of proposals offered in response to this RFP, CHOICe may at its sole discretion negotiate and enter into contracts with one or more successful bidders. Notwithstanding any other provision herein, bidder participation in this process is voluntary and at bidder s sole discretion. Price will be a consideration but will not be the sole factor in CHOICe s decision to award a contractual relationship. CHOICe reserves the right to reject any or all bids from a specific or multiple bidders for any reason at any time. CHOICe also reserves the right at its sole discretion to select or reject any or all bidder(s) in this process and will not be responsible for any direct or indirect costs incurred by bidders in this process. 3 Request for proposal Definitions Throughout this proposal the following definitions are used: means an individual or company that submits, or intends to submit, a proposal in response to the Request for Proposal Company means the bidder(s) awarded a contract resulting from this RFP; Contract means the agreement formed between CHOICe and the company as evidenced by an Agreement issued to the company; Contract document means the agreement, the company s proposal document, the RFP and such other documents as listed in the agreement, including all amendments or a addenda agreed between parties; Must, Mandatory or Required means an absolute minimum function or capacity, which, if not satisfied in the proposal, may result in disqualification in the final evaluation; Public Document Page 4 of 43

De-identification is the process of removing from data any information from electronic media that identifies a particular individual RFP means this request for proposal including any amendments, attachments, and/or clarifications pertaining to RFP that may be issued prior to the closing date, and Should, may or is desirable means desirable but not mandatory functions or capacities. s who are able to provide these functions or capacities may be evaluated favorably than those who cannot. Public Document Page 5 of 43

Terms of RFP 1 Acknowledgement Please acknowledge the receipt of this document by sending an e-mail to rfp.it@canarahsbclife.in. Please include the contact information for person who will be directly responsible for completing the RFP. 2 Proposal Deadlines CHOICe must receive duly completed and signed proposals not later than Monday, 7 th February, 2011 at 1800 hrs (IST). s are requested to note that they have to submit their response to the RFP in hard as well as electronic (CD) copies before the deadline of the submission date, which is Monday, 7 th February, 2011 at 1800 hrs (IST) and any decision to extend the submission date will be at the sole discretion of CHOICe. Technical & Commercial responses including the printed and signed documents and CDs should be enclosed in separately sealed envelopes and both these envelopes should be enclosed in a master envelope which should be received at the address mentioned below before the due date. Title: RFP for Workload Automation Kind Attn: Surendra Dangi Canara HSBC Oriental Bank of Commerce Life Insurance Company Ltd. 5 TH Floor, Tower-B, Centrum Plaza, Sector 53, Golf Course Road, Gurgaon-12200 Proposals received after the time and date specified above may, at CHOICe s sole discretion, be returned unopened, or destroyed and eliminated from consideration. Please do not send your RFP responses to any other CHOICe employee. s sent to any other location other than the above address and email id will not be considered. 3 Format of proposals Proposals must be submitted in accordance with the instructions contained in the RFP and must include all information and materials requested in the RFP. s are cautioned that proposals that do not follow the form required by, or contain the information requested in, the RFP shall be subject to rejection without review. All pages of any proposal submitted must be typed in the format embedded in this RFP and all responses must follow the numbering of the Sections and Subsections of the RFP. Public Document Page 6 of 43

s may include any additional information and material they wish; however, such material (e.g. alternative services and/or features) shall be identified in a separate attachment ("Attachment"). Any such attachment shall identify the applicable RFP Section or Subsection to which it is responsive and shall be incorporated into and be made a part of the proposal. If a believes that it can offer Contract conditions that may be more favorable to CANARA HSBC Life than those set forth in the RFP, shall include such conditions in a labeled addendum to their response as an Attachment to the proposal. However, must still complete all specifications as set out in the RFP. An authorized officer of the or other person authorized to bind in this matter must sign the returned proposals. 4 Further Inquiries and Questions Regarding RFP All inquiries that arise regarding the RFP must be submitted in writing (via email) by close of business on Friday, 28 th January, 201 Inquiries must be made only via e-mail and only to rfp.it@canarahsbclife.in. s to such inquiries will be made via e-mail and shared with all participants in the bid. No confidential information will be shared. agrees to designate one point of contact for all RFP and/or proposal communications. This point of contact should be clearly defined in the RFP response, as the single point for questions and clarifications on the RFP response. 5 CHOICe s Obligations The submission and receipt of proposals does not obligate CHOICe in any way. CHOICe shall not be liable for any costs incurred by s in the preparation, presentation or any other aspect of the proposals received by reason of this request, nor is CHOICe obligated to negotiate separately with any sources whatsoever in any manner necessary to serve 's best interests. CHOICe makes no representation, implied or express, that it will accept and approve any proposal submitted. Any and all Contracts which result from this RFP shall be non-exclusive, as-ordered agreements. 6 Proposal Evaluation Proposals submitted may be reviewed and evaluated by any person at the discretion of CHOICe s internal evaluation team, including non-allied and independent consultants retained by CHOICe now or in the future for the sole purpose of obtaining evaluations to proposals. s may be asked to further explain or clarify areas of their proposal in writing during the evaluation process. s are expected to submit their best bid in response to the RFP. Public Document Page 7 of 43

CHOICe s internal evaluation team will notify s, following completion of the evaluation process, whether or not s have been awarded a Contract. The only information regarding status of the evaluation of proposals that the team will give to any inquiring shall be whether or not that has been awarded a Contract. CHOICe may, at its sole discretion, inform any inquiring of the reason(s) why it was not awarded the bid. The bidders should submit their technical bid as well as the commercial bid separately in a sealed envelope. CHOICe will first open the technical bid and on evaluation of the technical bid, the commercial bid will be opened only for the vendors who qualified in the technical bid. Kindly refer Annexure A & B for technical bid format and Annexure C for commercial bid format. 7 RFP Terms and Conditions Applied to Final Contract The terms and conditions of the RFP, including the specifications and the completed proposal, will become, at CHOICe's sole discretion, part of the final Contract (the "Contract") between CHOICe and the selected. In the event that responses to the terms and conditions will materially impair a 's ability to respond to the RFP, should notify CHOICe in writing of the impairment. If fails to object to any condition incorporated herein, it shall mean that agrees with, and will comply with the conditions set forth herein. Any exceptions to the terms and conditions or any additions, which may wish to include in the RFP, should be made in writing and included in the form of an attachment to the applicable Section in the RFP. 8 Terms Binding on Following the date for submission of proposals, and prior to Contract award, the RFP shall be binding upon in all respects for a period of 180 days. 9 Hold Harmless In submitting a proposal, understands that CHOICe will determine at its sole discretion which proposal, if any, is accepted. waives any right to claim damages of any nature whatsoever based on the selection process, final selection, and any communications associated with the selection. CHOICe reserves the right to award the Contract to the (s) whose proposal is deemed to be the most advantageous in meeting the specifications of the RFP. In addition, CHOICe reserves the right to add or waive any requirements contained in this RFP at its sole discretion with regard to proposals submitted. CHOICe s decision on award of Contract shall be final and binding on all the s. Public Document Page 8 of 43

10 Confidentiality Provision The terms of this RFP, the information provided by CHOICe herein and all other information provided by in connection with the services offered to be provided by the pursuant to this RFP, are to be treated by as strictly confidential and proprietary. Such materials are to be used solely for the purpose of responding to this request. Access shall not be granted to third parties except upon prior consent of CHOICe and upon the written agreement of the intended recipient to treat the same as confidential. CHOICe may request at any time that any of CHOICe's material be returned or destroyed. Should choose not to respond to this RFP, please return all materials and any duplicates thereof at: Title: RFP for Workload Automation Kind Attn: Surendra Dangi Canara HSBC Oriental Bank of Commerce Life Insurance Company Ltd. 5 TH Floor, Tower-B, Centrum Plaza, Sector 53, Golf Course Road, Gurgaon-12200 11 RFP Schedule Listed below are the key steps and dates for this RFP process: CHOICe uploads the RFP on its website www.canarahsbclife.com All inquiries regarding RFP due by close of business s deadline for submitting responses to RFP 20 th January, 2011 28 th January, 2011 07 th February, 2011 12 Sub-Contracting The services offered to be undertaken in response to this RFP shall be undertaken to be provided by the directly employing their employees, and there shall not be any sub-contracting, franchisee, contract to hire, consultant etc. arrangement done by the. The deputed person should be only on bidder rolls. The services offered to be undertaken in response to the RFP shall only be from the parent company. However, the may draw resources from its own pool of group companies/ subsidiaries, provided that the shall remain responsible for all the obligations and shall indemnify the Company against any act or omission done by such resources. It may be noted that this contract Public Document Page 9 of 43

CANNOT be sublet/ sub-contracted to any third party and the resources if any hired from its group companies/subsidiaries shall also be on full time rolls of the respective company. 13 Acceptance of Proposals CHOICe reserves the right to modify the terms of the RFP at any time at its sole discretion and the same will be uploaded on the website http://canarahsbclife.abcprocure.com. The bidders have to remain updated about the same from the website and CHOICe will not be responsible for such information not being downloaded by the bidder. Subsequent to the submission of proposals, interviews and negotiations may be conducted with one or more s, but there will be no obligation to receive further information, whether written or oral, from any not to disclose the nature of any proposal received. This RFP should not be construed as an agreement to purchase products or services. CHOICe is not bound to accept the lowest price or any proposal of those submitted. Proposals will be assessed in accordance with the evaluation criteria. 14 Evaluation and Selection A committee will evaluate proposals against the mandatory criteria as detailed herein. Proposals meeting all the mandatory criteria will then be assessed and scored against the evaluation criteria. Subject to the result of technical evaluation being satisfactory, CHOICE intends to call the technically qualified bidders for a presentation (may include demo) of the system. Based on the presentation of the product and subsequent commercial evaluation, CHOICe will select bidder(s) and enter into contracts with them. CHOICe s decision on evaluation shall be final and binding on all the bidders. 15 Liability for Errors While CHOICe has used considerable efforts to ensure an accurate representation of information in this RFP as per its current understanding of the requirements, the information contained in this RFP is supplied as a guideline for s. The information is not guaranteed or warranted accurate by CHOICe, nor is it necessarily comprehensive or exhaustive. Nothing in this RFP is intended to relieve s from forming their own opinions and conclusions with respect to the matters addressed in this RFP. In the event CHOICe finds that the objectives of the intended system is better achieved by processes/procedures other than those mentioned in this document, CHOICe shall have the right irrespective of the fact whether it has already received proposals from intending bidders or not, to effect such changes and enter into negotiations with one or more s at its sole discretion for such changed/modified processes. Public Document Page 10 of 43

16 Acceptance of Terms All the terms and conditions of this RFP shall be deemed to be accepted by the and incorporated in its proposal unless specifically notified otherwise. 17 Ownership of Proposals All documentation, including proposals, submitted to CHOICe will become the property of CHOICe. 18 Use of Request for Proposal This document or any portion thereof, is the property of CHOICe and may not be used or copied for any purpose other than the submission of the s proposal. 19 Exception Notice If the believes that either the process or evaluating officer is biased or partial (either for or against) then is to provide Notice of this exception (in writing) to evaluating officer s supervisor (krishnamurthi.v@canarahsbclife.in) for analysis and action. Public Document Page 11 of 43

Proposal Preparation This section defines the proposal preparation and submission procedures, which are to be followed by all s. s are cautioned to carefully read and follow the procedures required by this RFP. Please note that deviations may be cause for rejection of your proposal. 1 Proposal Format Evaluation of proposals is made easier when s respond in a similar manner. The following format and sequence should be followed in order to provide consistency in response and ensure each proposal receives full consideration. s name and address, closing date and time, s telephone number, email address and a contact person. One page letter of introduction identifying the and signed by the person or persons authorized to sign and bind the to statements made in the proposal. The returned RFP will be referenced as an attachment if/when a contractual agreement is executed. This document has to be uploaded and mapped with this corresponding schedule. Please follow the format of this RFP, placing answers in the text box immediately after sections requiring responses. Please do not enter any information into any part of this document other than the boxes provided. The boxes will expand to accommodate responses of any length. Any additional information, brochures, etc., can be provided at the discretion of the and should be clearly labeled and uploaded. 2 Notification of Changes All recipients of this RFP will be notified of any changes if any made to this document prior to the due date of submission of proposals. 3 Changes to Proposed Wording The will not be permitted to change the wording of its proposal after submission to CHOICe. No words or comments will be added to the general conditions or detailed specifications unless requested by CHOICe for the purposes of clarification. Public Document Page 12 of 43

4 s Expenses s are solely responsible for their own expenses in preparing a proposal and for subsequent negotiations with CANARA HSBC Life, if any. 5 Currency and Taxes Prices quoted are to be: In Indian rupees; Exclusive of all taxes 6 Completeness of Proposal By submission of a proposal, the warrants that all components required to manage the program have been identified in the proposal or will be provided by the Company at no charge. 7 Implementation Scope Implementation of workload automation solution will include automation of about 300 jobs of which majority belong to following application systems Ingenium - Individual Policy Administration System Group Asia - Group Policy Administration System MIS Reports in Cognos Communication letter printing Portal Applications Database scripts in DB2 and Oracle Alerts ETL tasks in DB2 and Oracle AIX shell scripts Data File/Reports transfers from Public Document Page 13 of 43

SUPPLIER QUESTIONNAIRE 1 TECHNICAL QUESTIONNAIRE 1 INSTRUCTIONS Please fill out the enclosed table containing both the business and technical requirements checklist to help us further understand the functional footprint of your product. Respond to the requirements checklist by indicating both the degree of fit as per the key mentioned below and provide a detailed explanation of the functionality offered in the comments column in the table. Also mention any specific client references for the functionality offered. 2 Degree of Fit Against each requirement, enter one of the following: Y Requirement currently exists in your package. P Requirement does not exist in the package but can be met by a partner product. G Gap that can be resolved (Explain how your package handles this functionality) N Gap cannot be resolved Alongside the response code, please fill out the descriptive comment field to give additional information as needed. 3 General information of the vendor General Information Provide information regarding your company background, products, and solutions that address the stated CHOICe requirements. This could include marketing material, brochures, presentations, case studies and product documentation, such as: Key Partnerships (including the services/products they provide) Acquisitions and Mergers (Current / Planned, Motive) Financial results for last 3 years should provide information on their competency in Workload automation. Information should include Workload automation strength of bidder Public Document Page 14 of 43

Product support Roadmap of the Workload Automation product Ideally these additional materials should be provided in electronic formats. Customer Reference Please provide a list of customers that have completed integration or are in the process of integrating the product(s) you are offering to CHOICe. You may include previous retail products, but please make sure they are differentiated from the product(s) you are offering. Customer Name Customer revenue Contact Information Date of first installation (pilot): Name of Product / Module Version of product / Module Availability for Site visits (Y/N) No. of Automated Jobs 1 2 3 4 5 Types of Automated Jobs Note: If you have more references to list please add a separate list in the above-mentioned format. Public Document Page 15 of 43

Partner Reference Please provide a list of organizations with which you have a partnership, either for sales (dealer), support, development, technology, hardware, integration, installation, 3 rd party partners. Partner Contact Information Type of partner Nature of partnership Date partnership started/planned 4 Technical Functionality For various technical functionality questionnaires kindly refer Annexure A Technical. Please answer all questions and the answers should be as advised in section Apart from the above questionnaires, also answer the following questionnaires in a descriptive manner and the relevant documentation to support the same. Describe the technical architecture of each module of the solution offered in details. Here include The platform details, (identify the server operating system and database combinations that are available) Technology used The deployment details Note: In the deployment details mention where different components are deployed (web server / App server / DB server) and the preferred distribution of the servers (Web server / App server / DB server in the same machine or different machines). Please provide diagrams describing the logical view and the distribution view of the application. 5 Functional Requirement For various functional requirement questionnaires, kindly refer Annexure B Functional. Answer all questions in the fashion as mentioned above. Public Document Page 16 of 43

Annexure A Technical S No Functionality s Customization & Implementation Are the different customization options listed below available and what are the tools used in each of these options? 1 Table and Parameter based customization 2 Scripting and Rule based customization 3 Source code modification 2 Can customizations based on source code modifications be merged on to the newer releases and upgrades? How? 3 Do we get free upgrades on each release 4 Whether the new version will be compatible to existing version with customization? 5 Provide timelines for the entire project from the date of award of contract to till final implementation of Workload automation solution Product Strategy 6 Please elaborate the product roadmap over the next 5 years 7 Do you participate in standard bodies in the Retail and Technology areas? If yes, please provide list of memberships and the nature of memberships. 8 If the solution offered has third party tools and partner products bundled on to it, are these tools/products supported? Are your supports staff trained in partner products and bundled third party tools? Public Document Page 17 of 43

9 Can the solution be bought in modules separately? If yes, give a list of functional modules of the offered solution 10 What is the development language used? 11 How many versions of the software are currently in the market by your customers? 12 If the future vision of the product is architecturally (target platform, technology, major design optimizations etc.) drastically different from the current one Will both the flavors of the product co-exist (Both flavors supported and improved)? How will the migration/up gradation be managed? What would be the support plan for the current version? Technical Support 13 Key locations where company has offices with technical staff. Please elaborate how many technical staff members at each location. 14 Is source code provided with the purchase? Is there an additional cost for this? If not, will you submit the source code to escrow? Will you pick the cost of the escrow account? 15 Do you have the concept of remote support? (Technical support personnel from Vendor locations, remotely accessing the production system for support purposes). Do you currently do this with other clients? If yes, how many? If yes, with whom? In addition to the above mentioned support mechanism what other support options do you provide? Public Document Page 18 of 43

16 Is your company providing different types and levels of production support? If yes, please provide us the details of the same 17 Number of Certified/Trained resources in bidder s organization in India on the proposed product. 18 Number of Certified/Trained resources in India on the proposed product including other implementation partners. Warranty 19 Do you have a policy regarding response time warranty? State in detail your policy regarding response time warranty ( time warranty indicates the guaranteed performance/response time of the deployed product). Specify warranted performance for the proposed system. 20 Do you incorporate software furnished by another vendor in your product bundle? If so, how is it warranted and supported? Technical Architecture 20 Is the solution offered supported on multiple Platforms? If yes, then please mention the Preferred/Recommended Platform. (Please support this by factors like Stability, Customer base, Performance optimizations done specific to the Platform etc.) 21 Is there any tools used for version controls? If yes, What are all tools used for version controls? Please elaborate in all scenarios like production release and development environment Integration Requirement 22 Provide details of the Hardware Platform Preferred ---------------------------------------- Public Document Page 19 of 43

Also supported ----------------------------- 23 Provide details of database Preferred -------------------------- Also supported ---------------------------------- 24 Provide details about the application 1 Is the application is browser based? If yes, Preferred App Server --------------------------- Also supported app server ------------------------ Preferred web server ------------------------- Supported web server ---------------------------- Is the application is client server technology? If yes, what technology / language are used? Scalability and Performance 25 Is scalability dependent on Hardware Software 26 No. of users supported per CPU Windows Unix 27 Has the system been tested for load? If yes, please provide the following as annexure Bench marking volume Performance testing include number of users, bandwidth, volume of transactions Stress test details Incremental and reliability test details Public Document Page 20 of 43

Regression test details 28 Does your product support multiple CPUs? Please mention any limitations. DR and BCP 29 Whether DR and BCP plans are available? If yes provide details of DR and BCP Plans 30 If the answer for above question is Yes, whether the DR requires separate licenses besides production. System Administration 31 Describe the methods available and recommended to backup and restore the system and its data. 32 Are there audit trails for all transactions? Security 33 Whether the authentication and access controls are available in the system? If so, how is authentication and access control for the system provided? 34 Please elaborate whether the following standard user management procedures are supported? Change password on first login Forced change of password every 30 days Disable access after 3 unsuccessful logins Disable login after inactivity of 30 days 35 Please elaborate the following are parameterized Change of password on first login Forced change of password every 30 days Disable access after 3 unsuccessful logins Public Document Page 21 of 43

Disable login after inactivity of 30 days. 36 Whether the system has the controls and monitoring methods in built? If so, provide controls and monitoring methods available in the product 37 Will the system integrate with an external security directory for authentication information specifically Microsoft s Active Directory? 38 Whether security audit and event information are available? If so, What security audit and event information is provided by the system? Deployment Configuration 39 Is there any software development tool required to build and maintain the system which requires a license? If so, Give a list of software development tools used to build and maintain the system. 40 Please explain whether login information / profile are stored in database or any other form. Is the login / profile information stored in encrypted form? 41 If the client components be upgraded independently of the server components? If so, How version sensitive are the various components of the system? 42 Do you have a data dictionary for the product? 43 What report generator does the software support (if any) 44 Does the development team support any development / IDE tools for development? If yes, please elaborate tools used 45 Please provide data model for reference and /or review 46 Preferred Hardware configuration for server. Public Document Page 22 of 43

Preferred software configuration for desktop. System Limitations 47 Are there any limitations on the number of work stations or terminal? If so, what factors (if any) will limit the number of workstations or terminals that can be supported by the system? 48 Are there any other limitations, which we should be aware of? Data Control 49 Does the system perform checks on data entry to ensure integrity (e.g.: range checks, validity checks)? Please describe the features available and whether or not the checks performed are configurable 50 Are transaction failures rolled back to leave the database in a consistent state? 51 Is the software sold on per user license basis or CPU basis? If any other method used, please elaborate. Documentation 52 Are user manuals are provided both hard copy and soft copy? 53 Are all documentation pertains to Installation, Deployment, Job Configuration provided? 54 Are there any training manuals available for training purpose? If Yes, provide the same both in Hardcopy and soft copy 55 Is there any documentation on backup, recovery and replication procedure? If so, provide the same both hardcopy and softcopy. 56 Is there any training calendar available after the installation? If Yes, share the same. Provide the Public Document Page 23 of 43

exhaustive training calendar which should include both technical and functional training. Miscellaneous 57 Has the proposed product ever been implemented in HSBC group organization worldwide? If yes, please mention the details 58 Has the proposed product ever implemented in any other life insurance company across the world? If yes, please mention the details. Public Document Page 24 of 43

Annexure B - Functional Instructions Please fill out the enclosed table containing both the functional and technical requirements checklist to help us further understand the functional footprint of your product. Respond to the requirements checklist by indicating both the degree of fit as per the key mentioned below and provide a detailed explanation of the functionality offered in the comments column in the table. Degree of Fit Against each requirement, enter one of the following: Y Requirement currently exists in your package. P Requirement does not exist in the package but can be met by a partner product. G Gap that can be resolved (Explain how your package handles this functionality) N Gap cannot be resolved Alongside the response code, please fill out the descriptive comment field to give additional information as needed. The shortlisted vendors may have to give a product demo after the first round of short listing process is completed. Business Functionality Scheduling Available via Graphical User Interface Define a basic job definition Define scheduling criteria with reference to an existing calendar Define scheduling criteria without calendar dependency Scheduling solution must have the ability to define conditional dependencies for example, Job_B is dependent on Job_A only if Job_A runs on that day. Public Document Page 25 of 43

5. Scheduling solution must have ability to prevent mutually exclusive jobs from running at the same time. 6. Define pre-requisite conditions, submit times, logical resource requirements for job execution Scheduling solution must have the ability to trigger jobs to run based on the following 7. 8. - Ad-hoc - Date and time - Time window - Predecessor job - Resource availability - External event - File watch (creation, deletion, modification) - Condition code or exit code of a job - Event based Ability to control which exit codes, return code or condition codes are considered a failure. 9. Ability to define which messages in the system output determine job failure. 10. Ability to control which exit codes, return code or condition codes are considered a success. 1 Ability to define which messages in the system output determine job success. 1 Ability to define a job once but run it multiple times according to a pre-defined pattern such as every 30 minutes as a cyclic job. 1 Ability to group jobs into a collection such that only a single set of scheduling criteria is required for all jobs and all jobs must complete successfully before successor jobs can execute. 1 Scheduling solution must have the ability to centrally view log files or job output files from client machine without logging on to target machine to retrieve the information. 15. Scheduling solution should have the ability to schedule to run after specific minutes or hours after the successful completion of another job. Public Document Page 26 of 43

16. Scheduling solution should allow passing of parameters to jobs during execution of jobs. 17. Scheduling solution should have calendar based processing capability. 18. Scheduling solution should have the ability to restart a failed job and specify number of retries. 19. Scheduling solution should provide a robust out of the box utility that supports mass update of jobs, which would help in easier migration of schedules across dev and production environments. 20. Schedule verification, capacity planning for batch workload modifications 2 Project SLA compliance via comprehensive forecasting facilities. 2 Ability to simulate the future job flows and suggests on improvements to the batch jobs. 2 Add what if scenarios to existing schedules to forecast the impact on batch jobs. Administration and Maintenance Installation should be simple and should not require expertise knowledge on the tool or the system level to carry out the installation, upgrades and maintenance. Installation to be express and deployment time should be short and simple. Scheduling solution should be scalable. Specify if there are any limitations on managing the batch jobs from a single enterprise scheduling server. Provides a single admin console to manage all the components connected to the enterprise scheduling solution. Public Document Page 27 of 43

5. Ability to manage the application nodes where the jobs are to be run from a single console. 6. Ability to disable the jobs from running on a node when required without having to manually find the jobs and hold them from being submitted to that node. 7. Ability to set / modify the system parameters from the single administration console. 8. Ability to create user / groups and limit the privileges at user or group level to be able to schedule / monitor the jobs. The user management should be out of the box and should not require installation of any additional component. 9. Ability to restrict the users to use only the allowed accounts as the job owners. 10. Ability to control the number of concurrent jobs that can be run on a server or for a specific application. 1 Ability to raise alerts when any of the components is not available. 1 Ability to recycle the components from the Admin GUI console and also from the command prompt at the component installed location or server. 1 Ability to limit the users from accessing the Admin GUI console. 1 Support cloud platforms to run the jobs. Job Management Available via Graphical User Interface Manually call a job in to execute within a schedule already loaded into Active Job File (AJF). Hold a job prior to execution. View the details of a job on the Active Job File (AJF). Public Document Page 28 of 43

View the jobs sysout files. 5. Rerun a failed job and change status. 6. View the log for a particular job. The scheduling solution log must be granular and assist the operator to diagnose the cause of error or failure. 7. View the reason why a batch process has not started executing. 8. Update Job Dependencies 9. Update Resource Use 10. Amend Return Code checking 1 Change Source Script library name 1 Change Late Alerts 1 Update Auto recovery actions 1 Update Rerun actions 15. Create and remove dependencies that will not affect the definitions in the database 16. Job status 17. File arrival triggers 18. All operational and monitoring functions for all supported platforms and applications available from a single focal point of control. 19. Business-integrated workload management that shows the relevance of batch workload to business services. 20. Drill down into each schedule individually to avoid cluttered view. 2 Ability to determine the predecessor/successor jobs for a batch job. 2 View cross-platform dependencies from a single screen 2 Able to dynamically add jobs based on user requests, system and business events. Public Document Page 29 of 43

2 Manage an unlimited number of instances of the same job on a single schedule to support event-driven scheduling. 25. Alert facilities for notification to operating system consoles, email, pager, enterprise management consoles. 26. Ability to Bypass a job in the Active Environment without making any changes to the flow. Job status requirements Scheduling solution must have reporting capabilities to report on status of jobs. Correct status of job indicated after successful rerun. View can be filtered for particular status jobs only View outstanding predecessor job pre-requisites 5. View outstanding file arrival pre-requisites 6. View outstanding time pre-requisites 7. View outstanding resource pre-requisites 8. View resource status and availability 5. Workload Management Public Document Page 30 of 43

Effectively balance the utilization of resources between different applications at different times and days. Avoid resource overload. Increase the usage of higher-capacity servers. Dynamic routing of workloads Based on the business. 5. Dynamic routing of workloads for Managing downtime for maintenance windows. 6. Dynamic routing of workloads during High availability and disaster recovery. 7. Easy to Define and change the workload management rules and definitions 6. PeopleSoft Jobs Execution of PeopleSoft job is successful. Execution of PeopleSoft BW job is successful. Execution of PeopleSoft EBP job is successful. Execution of PeopleSoft SEM job is successful. 5. Execution of PeopleSoft BDC (SM35) job is successful. 6. Ability to have multiple environments running the same batch stream independently. 7. Reporting available for number of jobs executed and number of jobs failed. 8. Ability to execute a schedule based upon complex offset criteria. 9. Ability to track and action against static named spawned processes under managed batch jobs. Public Document Page 31 of 43

10. Ability to track and action against dynamic named spawned processes under managed batch jobs. 7. Variable Substitution in Job Processing Definitions The product must be able to use default and customizable parameters in the job definitions for: 8. Global variables 9. Date 10. Time 1 Workstation Name 1 Command line 1 Ability to read a remote text file for parameter values and pass the same to a batch file for execution. 8. File Transfers File Transfer to be out of box feature of the solution Integrate File transfers into the batch jobs. File Transfers over secure connection. Ability to restart the transfers from point of failure, thereby reducing the bandwidth consumption. 5. Provides compression, encryption and decryption for safe and secure transfers. Public Document Page 32 of 43

6. Allows pre or post command option to rename / move / delete the files at source or destination as per the requirement. 7. Raises alert for transfer failures. 8. Allows treating of network issues as acceptable and can reinitiate the transfers after set interval of time. 9. Supports file transfers across systems irrespective of platforms. 10. Provides GUI screen to click and select the directory / files to be transferred. 1 Shows graphical progress for file transfers. 1 Scheduling solution should have file watch ability to watch for presence or creation of file. 9. Return Code Checking The tool must be able to manage and initiate different actions based upon the following return code / exit code scenarios. Treat any code as acceptable and mark that job as successful. Treat exit code=56 as acceptable and mark that job as successful. Trigger other jobs based upon a return/exit code= Execute other jobs based upon a return/exit code= 5. Rescheduled to run 4 times based upon particular return/exit codes. 6. Reschedule to run 4 times based upon particular message in sysout files. Public Document Page 33 of 43

10. Job submission control from the GUI Suspend a particular schedule in the active environment Suspend jobs for a particular application Suspend all jobs within the active environment Kill jobs running on a particular server 1 Event Triggered Scheduling Ability to trigger the job based upon the creation, modification or deletion of a file at a specified location. Ability to monitor the file for a specific size before triggering the job. Ability to rename, delete or move the file before triggering the job. Support wild cards while looking for the file at a location. 5. Ability to raise alert upon file size not being of the minimum size specified. 6. Ability to raise alert upon file not being created or modified within the set time at the location. 1 Job/Schedule Status Customizable Alerting Scheduling solution must have reporting capabilities to report on status of jobs. Public Document Page 34 of 43

Where a job/schedule has a status of error and is rerun, the scheduler shows the jobs current status. Alerting for specific jobs/schedules can be turned off. Job/schedule status can be viewed from a single point within the tool. 5. Scheduling solution should allow customization of notification like email based on situation. 6. Scheduling solution should have ability to send notification via customized email, SMS, SNMP traps, logged in event logs. 1 Ability to schedule across periods greater than 24 hours Retain integrity of dependencies of local jobs after New Day process (24 hour window) without manual intervention. Retain integrity of dependencies of cross-platform jobs after New Day process (24 hour window) without manual intervention. Start job of a schedule dependent upon the end job of the previous days schedule. Jobs will retain their original characteristics when remaining in the active environment for longer than 24 hours. 1 Change Management and Version Control Scheduling solution must have version control facility out of the box to track the changes to existing schedules Should facilitate restoration to previous versions easily. Public Document Page 35 of 43

Version control facility should also cater to the jobs that were deleted from the schedule. Should allow restoration of deleted jobs. Export scheduling solutions to XML / Text files. 5. Export calendar definitions to a XML / Text files. 6. Import scheduling solutions to XML / Text files. 7. Import calendar definitions to a XML / Text files. 15. Calendars Create a calendar that contains region-specific standard business week. Create a calendar that contains public holiday s exclusive to a region. Ability of product to refer to a secondary calendar to determine if scheduled day is a processing day. Shift the jobs execution day to the previous day should it fall on a public holiday. 5. Shift the jobs execution day to the next day should it fall on a public holiday. 6. Support regular and periodic calendars across the enterprise. 16. Late and long running alerting Detect if jobs run longer or shorter than expected. Public Document Page 36 of 43

Notify if jobs are late in starting or late in ending. Jobs alert criteria can be modified whilst in the active environment. Alert integrity is maintained within and beyond a 24 hour window. 5. Ability to analyze the business impact as a result to a job failure easily. 6. Ability to prioritize the alerts based upon the impact the job failure will have on the business. 7. A job can be located in the active environment using the alert. 8. Scheduling solution must have the ability to dynamically anticipate end time of a schedule that is running late. 9. Scheduling solution must have the ability to manage batch related workload based on its impact to the business and key business services that the workload aligns with. 10. Any delay or impact on the critical path to critical batch jobs must be notified immediately. 1 Scheduling solution must have the ability to define the critical paths by indicating critical jobs in batch processing flow. 17. Security Allow a non-operations user to submit jobs, but not alter the postsubmitted status of that job. Allow a user access to perform function in the active environment, but have no access to the job definitions in the live database. Allow users read only access to the current plan, but not perform alterations of any kind. Public Document Page 37 of 43

Allow developers to copy production schedules to the development environment, with browse only access to the production environment. 5. External processes triggering events are restricted to particular prefix triggers. 6. External events forcing/ordering batch jobs are restricted to defined scheduling tables. 7. Communication between all product components on separate servers can be encrypted. 8. The use of the root account on Unix systems can be prohibited. 9. The product can communicate to remote components over specified ports to allow firewall customization. 10. Flexible security model that supports the definition of permissions for users and groups to allow granular control of which data can be seen and which actions can be taken by users and/or groups. 18. Job History Graphical review of past scheduling activity to support problem analysis and schedule optimization. The schedules for previous days can be accessed for analysis the next working day. Scheduling solution must have configurable parameters to determine period to retain job history within scheduling database. Ability to view historical run statistics Ability to view the job logs 5. Ability to view log files 6. Ability to view the job status and flow diagram from previous runs from the console. Public Document Page 38 of 43

19. Point of Entry Desktop Client Desktop Client via Citrix environment Remote Access Ability to monitor the jobs by logging onto the server and not having to login to the GUI. 5. Command Line Interface (CLI) should allow all operations that are available in the GUI. 20. Integration & API s Scheduling solution must have integration to ERP packages like SAP, PeopleSoft etc. to provide tighter scheduling capability. Create alerts in Event Management tools, using SNMP interface. Initiate an e-mail for failed batch job. Initiate an SMS message for a failed batch job. 5. External job to trigger the execution of an existing batch job. 6. External job to trigger the execution of a job not currently in the active environment. 7. Ability to integrate and run the stored procedures, SSIS packages, open queries on the leading databases MSSQL, Oracle and DB 8. Support for virtually all operating systems used on commercial platforms. Specifically confirm on AIX, Windows, OS-400, Linux. 9. Seamless support for major business applications such as SAP, PeopleSoft, Databases and Oracle for ebusiness Applications. Public Document Page 39 of 43

10. Seamless support for standard and secure file transfer protocols and to be part of the solution 1 Seamless support for Web Services. 1 Seamless support for both Open Messaging technology such as Java Messaging Services (JMS) or proprietary such as IBM Websphere MQ. 1 Seamless support for Java and J2EE Applications, including EJBs, on all compliant Application Servers such as Websphere, Weblogic, JBOSS, Oracle Application Server and others.. 2 Backup & Failover Ability to run the backup of the centralized GUI server and the scheduling server from the command prompt. A job can still be executed when the Server that normally schedules it is unavailable. A job definition that has been inadvertently updated can be restored from a backup. The availability of the Enterprise Manager does not impact the scheduling of batch processes. 5. The product components are compatible with a clustered Unix / Windows environment. 6. The supplied database backup and restore utilities work as documented. 7. Ability to initiate failover, mirroring and restore from the scheduling server. 2 Audit : Public Document Page 40 of 43

Comprehensive auditing of administration activities across the enterprise. Should be able to track changes to the system parameters for auditing. Scheduling solution must have auditing function to track on actions issued by operation team for accountability and audit purpose. Ability to prompt the user to enter annotations for the changes they perform. Audit report to include the Annotations entered by user for that specific change. 5. When changes were made to job? 6. Who made the changes to the job? 7. What fields were changed to the job? 8. When changes were made to the job definition in the scheduling tables? 9. Who made the changes to the job definition in the scheduling table? 10. What fields were changed in the job definition in the scheduling table? 1 When changes were made to the calendar definition? 1 Who made the changes to the calendar definition? 1 What changes were made to the calendar definition? 2 Reporting : Display Active jobs Job schedule criteria Public Document Page 41 of 43

Job runtime criteria Job name criteria 5. Resource definitions criteria 6. Cross-reference dependencies 7. Hostname jobname reports 8. Execution flowcharts in universal file format e.g. html 9. Forecast reporting text with various what-if scenarios 10. Forecast reporting graphical with various what-if scenarios 1 Generate a report based upon particular common attributes of jobs in the Active Environment. 1 Generate a report based upon particular common attributes of jobs in the scheduling tables. 1 The reporting facility should allow generation of reports in the following options - Online - Batch processing 2 Solution : Uses industry-standard relation DBMS such as Oracle, DB2, supplied with the product Options for quick installation in simple configurations yet flexible enough for distributed and heterogeneous environments Support for silent installation. Support for High Availability using industry-standard solutions such as clustering, Mirroring. 5. Manage authentication via Active Directory. Public Document Page 42 of 43

6. Flexible, scalable architecture capable of supporting very modest configurations as well as global deployments of Global 2000 organizations. 7. Strong network security via industry-standard SSL protocol 8. Scheduling solution must have agentless technology where no installation of scheduling agent is required on target machine where jobs are executed. Annexure C Commercial Bid Format Sl No Item Quantity Required A Server Software License 1 Operating System license ((if any) 2 Database license (if any) B Workload Automation Package 1 Minimum users license cost 2 Additional Users (per user license cost) 3 Per license cost 4 Per workstation cost 5 Source code cost (if available) C TOTAL LICENSE COST First Year Implementation Cost with 3 month onsite support 1 Project Manager - Per day cost in INR 2 Senior Application Consultant - Per day cost in INR 3 Developer - Per day cost in INR D TOTAL IMPLEMENTATION COST Post Implementation Support (from 2 nd Year onwards) 1 Annual Technical Support 1 Year Option 2 Annual Technical Support 3 Year Option Total Cost Rate per unit Total Price Public Document Page 43 of 43