The Bidder must respond to the following Staff requirements by using the table below. 7.2.2. The Bidder shall identify the Project Manager and all other “Bidder Personnel” roles (e.g. System Architect, Database Administrator, Functional Lead, Test Lead, and Security Expert) that are key to the success of each Phase of the Project. 7.2.3. The Bidder shall provide an explanation of the responsibilities for each role. 7.2.4. The Bidder’s Project Manager shall be required to work onsite for the duration of the project. 7.2.5. All proposed Bidder Personnel shall have performed significant roles in at least one (1) project of similar size and scope in the last two (2) years that migrated enterprise z/OS infrastructure inclusive of applications, toolsets, utilities, and databases to a distributed platform. 7.2.6. The Bidder shall provide a resume for all Bidder Personnel proposed for this project. Resumes shall reflect qualifications and recent experience relevant to the scope of the work indicated in this RFP. Resumes shall include at least three (3) references that can be directly contacted to verify the individual’s qualifications and experience. Resumes shall include the office location of each person. 7.2.7. The Bidder shall commit in writing, in their proposal, that each staff member assigned to this project has the ability to communicate clearly in the English language both verbally and in written form. 7.2.2. 7.2.2. 7.2.3. 7.2.4. 7.2.5. 7.2.6. 7.2.7. Role Name Responsibilities On-Site for Project Duration (required for Project Manager only) 1 Project within 2 of Similar Size/Scope Resume Attached Able to Communicate in English (written and verbally) Project Manager
Categories Description Target Minimum Performance Measurement Interval Bidder Acceptance SYSTEM OPERATIONS Availability (of support application) Intent: To ensure that ACES and ACES.Online are available and operational during designated hours of operation. This SLR is not intended to hold the Bidder accountable for outages or lack of availability resulting from DSHS planned outages or DSHS infrastructure failure. (1) 1 (CICS): 100% 2 (WEB) 100% 1 (CICS): 99% 2 (WEB): 99% Measure Daily, Report Monthly (1) Measurement of CICS Time 1: All CICS Production Regions. Measured by the number of minutes (duration) any production CICS region is either down (not running) or not responding to transaction requests. If one or multiple regions are down or not responding, the duration of the outage starts from the time the earliest region is down or not responding to the time the latest region is back running and/or responding to transaction requests. Measurement of WEB Time 2: ACES.Online Application Servers. Measured by the number of minutes (duration) the ACES.OnLine Application Server is causing client outages or not responding to client requests. The duration of the outage starts from the time that the application is not responding to client requests to the time the servers are back running and/or responding to client requests. Calculation of Minimum Performance:
Minimum performance is measured by dividing the total number of minutes the system was available (calculated by subtracting the above unavailable measurements from the scheduled available time) by the total number of minutes the system is scheduled to be available during the measurement period as shown in the ACES Production Schedule. Categories Description Target Minimum Performance Measurement Interval Bidder Acceptance Response Time of the Application Intent: To ensure that ACES and ACES.Online users receive timely responses to transactions. To ensure the application is designed, coded and operating efficiently. This SLR is not intended to hold the Bidder accountable for response delays resulting from DSHS infrastructure issues. (2) 1 (CICS) 0.15 seconds 2 (WEB) 0.17 seconds WEB CICS transactions associated with printing letters locally are excluded from calculating average response time. 1 (CICS) 0.25 seconds 2 (WEB) 0.3 seconds WEB CICS transactions associated with printing from calculating average response time. Measure during peak daily hours Report Monthly (2) Measurement of CICS Time 1: All internal CICS Production transactions. CICS internal response time is measured by using PERFORMANCE REPORTER software reporting against CICS transaction logs. Batch jobs are run each night to generate hourly, daily and monthly monitoring reports. Calculation of Minimum Performance: Minimum performance is calculated by averaging all Production CICS transactions over the measurement period. Web transaction averages do not include response time for the letter job (WE99). Both Mainframe and Web averages must meet the minimum target or else the service level is considered unmet.