# Page Question Type Question Response 1 40 Process As mentioned in the RFP "Offeror's must fully describe how they will be fully operational by July 1, 2015." We assume that the vendor will be provided a 3 months’ time period to complete the transition phase. (i.e. starting from award start date of 03/31/2015 to 01/07/2015). Please confirm. The vendor will be provided the period of time from contract award start date through June 30, 2015 to complete the transition phase. It is anticipated that this will be three months. 2 40 Scope As mentioned in the RFP " How it will confirm it has transitioned all assets and materials needed to continue systems operations." Considering the above Statement, does the State expects the vendor to perform any mandatory activity like: Operational readiness testing (ORT) to ensure Operation Readiness & Business Continuity? The State will perform a readiness assessment with the vendor near June 1, 2015 in order to validate Operational preparedness. 3 General Other We assume that the vendor will be provided with the existing test artifacts (Manual/automation test scripts, test results, etc.) will help to bring in reusability during the M&O and enhancement testing phase. Please confirm. The vendor will have available all existing test artifacts.
31 126 - Point # 47 Process What are all the used for (Other than Clearquest & JIRA) 1. Requirement gathering 2. Data Models 3. Design 4. Unit Testing 5. System & Integration Testing 6. Source code management The RFP procurement library includes a list of all tools. The following are used currently for items listed: 1. Requirements gathering - Word requirements documents, Excel, ClearQuest and JIRA 2. Data Models - Word, Excel, ErWin, Visio 3. Design - Word, Excel, Visio 4. Unit Testing - Clover (YES NM) 5. System & Integration Testing - QTP, ClearCase, and Atlassian tools 6. Source code management - ClearCase, Subversion 32 133 - Pint # 106 Scope Please share past 12 months ticket count by priority, request type (incidents/Service Requests/etc.), function, etc. A slide deck for November 2014 information has been added to the Procurement Library. 33 135 - Point # 127 Technical What is current release management process and release planning? How many releases are happening in a month for 1? Enhancement 2. Incidents 3. Break fixes Current release management process includes weekly meetings with vendor, IT and business to determine what Work Requests (Incidents and Break Fixes) will go into next major and immediate releases if needed. This is planned for 2-3 releases in the future. Each month has one major release and 1-3 immediate releases if needed. Enhancements are determined with monthly Steering Committee meeting of all Divisions and are scheduled into releases based on priority and hours required to complete the change request. These are determined 2-3 releases out as well. In additional daily data fixes are submitted by vendor for approval and run as required. 34 137 - Point # 140 Technical What tools are used for batch scheduling and batch monitoring? OpCon tools are used for batch scheduling and batch monitoring currently. 35 138 - # 142 Technical Please provide details of OpCon environment Please refer to OpCon Integration documentation in the Procurement Library in the Technical Architecture folder (Deliverable A4_Technical Architecture Plan-Appendix L Opcon Integration)