Request. For. Information (RFI) Enterprise Process Scheduling. Date: September 26, Washington Metropolitan Area Transit Authority

Transcription

1 Request For Washington Metropolitan Area Transit Authority Information (RFI) Enterprise Process Scheduling Date: September 26, 2011

2 INTRODUCTORY INFORMATION RFI Enterprise Process Scheduling APPROVED FOR RELEASE END OF SECTION

3 Background/Introduction Introduction This project involves procurement and implementation of an enterprise-level job/process scheduling solution (also known as IT Workload Automation Broker (ITWAB)) which can provide a unified mechanism for managing and monitoring critical applications/os across the organization. This RFI is issued by WMATA on behalf of Data Center and Infrastructure (DCI) Department, hereinafter referred to as Authorized POC. The objective of the project described in this RFI is hereafter referred to as Solution. The terms vendor and supplier will be used synonymously to refer to the entity responsible for providing services to WMATA. Background WMATA s IT business systems involve routine execution of critical background support jobs, with varying frequencies, to perform tasks such as background data transfers within systems, cleanup and relocation of systems logs, systems health checks, nightly systems memory clean up/reboots. Currently, these jobs are either manually executed or automatically scheduled on per-system basis. There is a need for an enterprise-level unified approach for scheduling, ensuring the execution and alerting the subject matter experts. WMATA s IT infrastructure uses heterogeneous operating systems environment which is comprised of AIX, Windows, Solaris and Linux and other flavors of UNIX. Some of the key application platforms included but not limited to PeopleSoft, Maximo, WebSphere, WebLogic, BizTalk, Oracle App Servers, MS-SQL Server Scheduler. The scheduled jobs are exists at multiple tiers to include but not limited to, application servers, Operating System and custom developed application code executed at scheduled intervals. The scheduled jobs functionality spans a broad range to include but not limited to crossapplications data transfers, backups, applications housekeeping functions, internal systems housekeeping functions, and automated systems/application processes restarts. WMATA is using CA Spectrum Suite for Enterprise Monitoring. The backup environment consists of TSM. The backend database platforms supported are Oracle and Microsoft SQL Server (preferred). Systems operate in Microsoft Active Directory and Microsoft Exchange environments. This business initiative is focused towards implementation of a centrally managed Enterprise-level job/process scheduling solution which will minimize chances of human error, proactively ensure critical jobs are attended within timely manner. WMATA intends to implement an enterprise-level job/process scheduling solution in The specific schedule, deliverables and roles and responsibilities are yet to be determined. Vendors are encouraged to provide a best practice solution. Purpose and Objectives WMATA is seeking a geo-redundant job/process scheduling solution based on commercially available well known software product. The proposed software product must carry perpetual licenses and include 3- year maintenance support.

4 The solution must incorporate disaster recovery and high availability as part of design and implementation. The JGB will serve as the primary site for job scheduler with CTF as the secondary site. The proposed solution must have none to minimal interruption to the existing automation processes, during and after the implementation of the solution. The software product proposed in the solution must support WMATA s current environment as indicated in the previous section. The vendor must incorporate post implementation support hours for providing remote/onsite assistance during the first year of the solution rollout. Contract Products and Services to Support the Requirements a. Technical Specification It is WMATA s preference to use Virtual Servers Technology. The current virtual servers environment is based on VMware vsphere 4x infrastructure. WMATA will provision Microsoft Widows Server Operating System. WMATA will also provide physical server hardware, should the accepted solution requires the physical servers. If during analysis, vendor requires physical servers which WMATA needs to procure; vendor must allow 4 to 5 weeks for the hardware procurement, when developing implementation plans. If the proposed solution requires special purpose software and/or non-server hardware, the vendor must provide cost of the software/hardware as a separate line item in the response. It is WMATA s preference to use a single software product to provide job scheduling capabilities. Some of the required key features (which is not an all inclusive list): Ability to schedule jobs across multiple platforms, Workflow-based job executions Ability to trigger existing jobs in the native environment of target system (for cases where WMATA decides to keep certain jobs on the original system). Provide full visibility into execution history of the jobs Ability to detect success/failures of the jobs, ability Event-drive Processing Security and Auditing Queue Management and Job Prioritization Dependencies Management Workload Management Calendaring Role-based Access Control Graphical Reporting Administrator Alerts/Notifications Job-owner Alerts/Notifications Customizable Execution Status Summaries and Reports transmissions to Job-owners Integration with WMATA s Enterprise Monitoring Solution Self-Recovering High Availability Disaster Recovery Scalability SQL Server and Oracle DBMS Support

5 The proposed software product must carry perpetual licenses and include 3-year maintenance support for software/hardware provided by the vendor. The software product proposed in the solution must support WMATA s current environment as indicated in the previous section. The vendor must adhere to the industry best practices for implementation. The vendor must comply with the WMATA IT infrastructure standards and policies. b. Training and Knowledge Transfer It is WMATA s requirement to become self-sufficient in operating or maintaining the solution at its completion. The vendor must determine the type of technical knowledge transfer necessary or such user self-sufficiency. The designated authorized POCs will shadow the vendor throughout the project. The vendor will be responsible for the knowledge transfer of the solution. Vendor must provide formal training of WMATA s support staff for day to day management and administration of the system. c. Support The vendor must incorporate post implementation support hours for providing remote/onsite assistance during the first year of the solution rollout. RFI Response Instructions Interested vendors should review and respond to the RFI. RFI key dates are as follows, 2:00 pm ET: Sept 26, 2011 Sept 30, 2011 October 13, 2011 TBA 2011 RFI made available to the respondents Deadline for submitting questions Deadline to receiving response + supporting documents Decision to launch an RFP / Solicitation All questions related to this RFI should be directed in writing ( ) to: Celena Cochrane Contract Administrator ccochrane@wmata.com Vendors must ensure that your response is delivered to the following address on or before October 13, 2011, 2:00 pm EST with an electronic copy to ccochrane@wmata.com: WASHINGTON METROPOLITAN AREA TRANSIT AUTHORITY th Street, NW Washington, DC Room 3C-01 Attn: Celena Cochrane Disclaimer

6 WMATA does not intend to award a contract on the basis of this RFI or otherwise pay for the information solicited. This RFI does not constitute a solicitation for proposals for WMATA to enter into negotiations to award a contract. This RFI is for planning purposes only and shall not be considered as a request for proposal or as an obligation on the part of WMATA to acquire any products or services. No entitlement to payment of direct or indirect costs or charges by WMATA will arise as a result of contractor submission of responses to this RFI or WMATA s use of such information. Responses to this RFI will not be returned. Whatever information is provided in response to this RFI may be used to access tradeoffs and alternatives available for determining how to proceed with the acquisition. Any proprietary information that is submitted may be used in establishing requirements but specific contractor submitted information will be safeguarded as proprietary. The information, responses received in response to this RFI may be shared with other local and federal agencies at the discretion of WMATA. Evaluation Criteria WMATA will select the best value solution for the agency. The following key factors will be used for evaluating the vendor solutions. WMATA may reject disqualify proposals which do not fully and clearly address the requirements of the evaluation criteria. a. Technical Solution - Industry Reputation of the Proposed Software Product - Flexibility and support capabilities of the Software Product (see Contract Products and Services to Support the Requirements) - Simplicity of the Solution - Strength of Technical Implementation Approach to address requirements of this RFI b. Vendor s Past Performance Vendor must be able to demonstrate extensive experience with Job/Enterprise Scheduling Systems Implementation - Vendor has supported at least 3 large implementations with Enterprise Scheduling Implementations for separate customers. Vendor must cite references to the projects, customers, date and duration for the work, description of the technical work performed in direct relation to this project. - Enterprise Scheduling implementation is one of the core competencies of the vendor c. Vendor s Bench Strength The vendor must clearly show its ability to quickly and seamlessly provision an equivalent or better technical resources should such as need arise. - Provide bench strength, for enterprise job scheduling resources, maintained over the past 12 months - Clearly indicate the maximum number of days it will take for the vendor to replace the onsite resource should such a need arise Submittal Requirements Vendor must provide the following as part of the RFP: a. A detailed technical solution - The vendor must specifically address how it will achieve the services availability objectives asked for in this RFI - The vendor must specially address Disaster Recovery of the solution b. Past performance related to the scope of this RFI.

7 - Provide core competency of your business - Provide number of years for which the vendor has been in business - Provide number of years performing the work similar to this RFI - Provide at least 3 separate customers references which WMATA may call - Provide the type of support contract providing similar servers as required in this RFI, duration of the contact, date of award of the contract - Provide the sizes of the organizations supported thru the contracts submitted as an evidence of the past performance - Provide size and type of the RFI-scope-specific environment supported on each of contracts submitted as evidence of the past performance - Clearly indicate if the past contracts completed their period of performance. If the period of performance was not completed, an explanation must be provided. c. Personnel resumes which reflect potential technical resources which may work on the project. The vendor should clearly indicate if the proposed technical personnel will actually be assigned to the project or if the resumes are provided only as a sample only.