Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF JANUARY 25, 2013 FBO #4080
DOCUMENT

R -- USER ACCEPTANCE TESTING (UAT) *LOOKING FOR GSA CONTRACT HOLDERS* - Attachment

Notice Date
1/23/2013
 
Notice Type
Attachment
 
NAICS
541511 — Custom Computer Programming Services
 
Contracting Office
Department of Veterans Affairs;Health Administration Center;3773 Cherry Creek Drive North, Suite 450;Denver CO 80209
 
ZIP Code
80209
 
Solicitation Number
VA74113I0083
 
Response Due
1/31/2013
 
Archive Date
4/1/2013
 
Point of Contact
MAURICE WALKER
 
E-Mail Address
E.WALKER@VA.GOV<br
 
Small Business Set-Aside
N/A
 
Description
STATEMENT OF WORK Veterans Health Administration (VHA), Chief Business Office (CBO) has identified a requirement to retain a highly skilled Contractor to provide an objective and independent assessment of software product implementations. B5.1 PURPOSE The Chief Business Office (CBO), Veterans Health Administration (VHA), Department of Veterans Affairs (VA) is seeking professional services for User Acceptance Testing (UAT) support to provide an objective and independent assessment of software product implementations (and related processes) throughout the project lifecycle. In addition, to facilitate early detection and correction of errors, enhances management insight into risks and mitigates the risks that a project will not meet its goals in terms of project performance, scope, schedule, and budget. B5.2 BACKGROUND B5.2.1 The Department of Veterans Affairs (VA), Veterans Health Administration (VHA) is one of the world's largest health care delivery organizations. As part of an integrated strategy to provide veterans with timely, respectful, and efficient service, the Chief Business Office (CBO), Member Services devotes its attention on the enrollment, eligibility, and contact management elements within the VA's Health Care System. B5.2.2 The VA provides eligibility and enrollment determination and income verification services for veterans through the Income Verification Division and Enrollment Eligibility Division within the Health Eligibility Center. The CBO, Systems Management office provides consultative services to Member Services' initiatives that facilitate the access of care to veteran's benefits and services. Systems Management defines and implements business initiatives and programs, provides business analysis, integration of business practices and information systems, and coordination of business and system processes deployments. B5.2.3 In general, veterans seek health care at VA expense and obtain such care at VA facilities. The Income Verification Division and Enrollment Eligibility Division provide the VA Medical Centers with accurate verification and eligibility decisions in order to collect copayments from veterans for care. A veteran's means test status and priority group are determined based on pension guidelines provided by law. Various VA Policies and Directives have been written to provide additional interpretation. B5.2.4 The VHA Chief Business Office (CBO), Systems Management has developed a comprehensive set of requirements to outline a vision for the future of Member Services. Systems Management is managing multiple programmatic enhancements to Income Verification Matching to provide a stronger integration with the Enrollment System in order to meet both long-term needs as well as interim requirements. These enhancements will not only provide support to the Enrollment and Income Verification process, but components under the Veterans Relationship Management Program, Veterans Transportations Services, Veterans Point of Service (Kiosks), and Legislative changes. B5.3 OBJECTIVES The purpose of User Acceptance Testing (UAT) for Member Services is to give the customer an opportunity to test the application. UAT will simulate a production environment and allow the validation of the requirements outlined in the Business Requirements Document (BRD). UAT is a method to improve the quality and effectiveness of the product by determining if the system is acceptable and capable of delivering accurate, timely information and satisfactory service to VHA users. As part of User Acceptance Plan, the UAT team will validate end-to-end business functionality to assess whether the application performs to a customer defined acceptable level of application functionality and stability. B5.4 SCOPE There will be a total of 3 Releases and two separate UAT's will be performed in the base year and 1 UAT in option year 1. The contractor will be responsible developing the test plan, writing user acceptance test scripts and for assisting the USERS in executing test scenarios, which will exercise the following aspects of the application: Level 1: The integration of components of the required systems; inclusive of testing for defects, coding errors, and usability. Level 2: To assure the complete system has been delivered. In this level of testing, the business owner is looking to guarantee components/interfaces have not been left out and/or the system conforms to the specified use case requirements. Level 3: To assure the system meets the critical business requirements, such as end-to-end business functionality, volume, and stress testing. Users of the system with the support of the contractor will perform tests, which analysts and developers have derived from the requirements gathered from the business as well as test scenarios written by users. The contractor will lead UAT team in the evaluation of the application by conducting user functionality tests, which consists of creating and executing test cases against the application. The test results will be used to determine whether the following items are included in the system: "Required attributes/functionality are present "Test cases in the required system are implemented "Menus, screens, reports, system interfaces are present as specified and behave as documented and expected "Interfaces to external systems work effectively "Specified processing algorithms are implemented correctly "End to end business processes work appropriately "Requirements and rules are appropriate and complete thereby meeting the needs of the business "Roles-based usage works accordingly Approximate total number of UAT test scenarios and test cases/scripts expected to be generated by the contractor: "Approximately 40 use cases that include an average of 4 scenarios each. Would expect more than 1 per scenario per use case "Approximately 36 workflow use cases that include 1 scenario per use case. "Approximately 36 workflow use cases that include an average of 3 scenarios each. "Approximately 25 correspondence use cases. "Approximately 11 different scenarios within RAS where a workflow item may be created. "Approximately 24 different scenarios within Claims Processing where a workflow item may be created. "The numbers above represent an "atomic" approach to testing of requirements and does not consider scripts needed to test system integration. Approximate total number of critical business requirements for the health claims systems against which test scenarios and test cases/scripts will be built and tested "Approximately 300 "features" defined in each BRD. "Approximately 960 requirements to be tested (40 use cases X 4 scenarios X 6 steps). "Approximately 500 rules to be tested. UAT testing will take place at the Health Eligibility Center in Atlanta, Georgia and will be expected to last 20 working days. B5.5 MANDATORY TASKS AND ASSOCIATED DELIVERABLES - BASE PERIOD The contractor shall perform the tasks and complete the associated deliverables as follows by the scheduled dates within the overall period performance or as may be agreed to with the Program Manager. If for any reason, any deliverable cannot be delivered on time according to the below schedule, the contractor shall provide a written explanation three days prior to the due date to the Contracting Officer Technical Representative (COTR). This written transmittal shall include a firm commitment of when the work shall be completed. This transmittal to the COTR shall cite the reasons for the delay, and the impact on the overall project. The COTR will review collaboratively with the program office the facts and issue a response in accordance with the contract terms and conditions. All deliverables shall be provided in electronic media. Specifically, the contractor shall: B5.5.1 Task One: UAT Management: The contractor will develop a UAT Management Plan describing the activities, personnel, schedule, standards, and methodology for conducting the UAT. B5.5.1.1 Deliverable 1.1: Complete UAT PMP (within 15 calendar days of award) B5.5.1.2 Deliverable 1.2: Staff Background Investigations (within 5 calendar days of award) B5.5.1.3 Deliverable 1.3: Evidence of Staff Training (within 5 calendar days after award) B5.5.1.4 Deliverable 1.4: Business Associate Agreement (date of award signature) B5.5.1.5 Deliverable 1.5: Electronic Status Reports (monthly) B5.5.2 Task Two: User Acceptance Testing (UAT): The Contractor shall support the customer in performing User Acceptance Testing. The activities will include UAT planning, designing user acceptance test cases, assist in selecting team to execute UAT test cases, overseeing the execution of test cases and documenting the defects found during UAT. B5.5.2.1 Deliverable 2.1: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria. The plan will include at a minimum: "Test Approach "Assumptions and Constraints "Setup of Test Environment "Approach to Develop Test Cases "Test Period "Process to Document Test Results B5.5.2.2 Deliverable 2.2: User Acceptance Test Cases: The User Acceptance Test Cases will be developed in simple language and outline the precise steps to help the Test Execution Team test the application thoroughly. They will be developed to ensure that the UAT provides sufficient coverage of all the scenarios and will be mapped to the Requirements Traceability Matrix. B5.5.2.3 Deliverable 2.3: User Acceptance Results Document: The User Acceptance test results will be documented in a mutually agreed upon format. It will document any issues found, such as bugs, crashes, or missing functionality. B5.5.3 SCHEDULE FOR DELIVERABLES - Base Period DeliverableDeliverable Description (Performance Period)Due Date Task 1 Deliverable 5.5.1.1: Present complete PMP in Microsoft Project and briefing in Microsoft PowerPoint to CBO at CBO Central Office, 1722 Eye Street, Washington, DCWithin 15 calendar days after contract award Task 1 Deliverable 5.5.1.2: Provide a full and complete list of names, Social Security Numbers, and home addresses of contractor personnel for the Background Investigation requirement within 5 calendar days from date of award. Provide a Staff Roster within five business days from date of award.Within 5 calendar days of award. Task 1 Deliverable 5.5.1.3: Provide evidence of contractor's staff training for VA's annual mandatory training required with 30 calendar days from date of award. If contract performance crosses the anniversary date for VA's recurring annual training requirements, such training must be completed within 30 calendar days of the anniversary date. Training completed by contractor staff under separate VA contracts will be accepted and evidence of such training, i.e., training certificates is submitted. Within 5 calendar days after contract award Task 1 Deliverable 5.5.1.4: Provide the Business Associate Agreement within five days from date of award. The Contracting Officer will countersign and send to the contractor within one day of receipt. Date of award signature Task 1 Deliverable 5.5.1.5: Provide monthly electronic contract status reports on the fifth day of each month. Monthly status reports will outline the progress of each task, identify contractor's accomplishments, contractor's project issues/concerns, and contractor's next month proposed activitiesOn the fifth day of each month Task 2 Deliverable 5.5.2.1: User Acceptance Test Plan: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria90 calendar days prior to the scheduled start of UAT Task 2 Deliverable 5.5.2.2: User Acceptance Test Cases: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria.30 calendar days prior to the scheduled start of UAT Task 2 Deliverable 5.5.2.3: User Acceptance Results Document: The User Acceptance test results will be documented in a mutually agreed upon format. It will document any issues found, such as bugs, crashes, or missing functionality.5 calendar days post UAT B5.6 MANDATORY TASKS AND ASSOCIATED DELIVERABLES - Option Period The contractor shall perform the tasks and complete the associated deliverables as follows by the scheduled dates within the overall period performance or as may be agreed to with the Program Manager. If for any reason, any deliverable cannot be delivered on time according to the below schedule, the contractor shall provide a written explanation three days prior to the due date to the Contracting Officer Technical Representative (COTR). This written transmittal shall include a firm commitment of when the work shall be completed. This transmittal to the COTR shall cite the reasons for the delay, and the impact on the overall project. The COTR will review collaboratively with the program office the facts and issue a response in accordance with the contract terms and conditions. All deliverables shall be provided in electronic media. Specifically, the contractor shall: B5.6.1 Task One: UAT Management: The contractor will develop a UAT Management Plan describing the activities, personnel, schedule, standards, and methodology for conducting the UAT. B5.6.1.1 Deliverable 1.1: Complete UAT PMP (Within 15 days from date of award) B5.6.1.2 Deliverable 1.2: Staff Background Investigations (within 5 calendar days of award) B5.6.1.3 Deliverable 1.3: Evidence of Staff Training (within 5 calendar days after award) B5.6.1.4 Deliverable 1.4: Electronic Status Reports (monthly) B5.6.2 Task Two: User Acceptance Testing (UAT): The Contractor shall support the customer in performing User Acceptance Testing. The activities will include UAT planning, designing user acceptance test cases, assist in selecting the team to execute UAT test cases, overseeing the execution of test cases and documenting the defects found during UAT. B5.6.2.1 Deliverable 2.1: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria. The plan will include at minimum: "Test Approach "Assumptions and Constraints "Setup of Test Environment "Approach to Develop Test Cases "Test Period "Process to Document Test Results B5.6.2.2 Deliverable 2.2: User Acceptance Test Cases: The User Acceptance Test Cases will be developed in simple language and outline the precise steps to help the Test Execution Team test the application thoroughly. They will be developed to ensure that the UAT provides sufficient coverage of all the scenarios and will be mapped to the Requirements Traceability Matrix. B5.6.2.3 Deliverable 2.3: User Acceptance Results Document: The User Acceptance test result will be documented in a mutually agreed upon format. It will document any issues found such as bugs, crashes or missing functionality. B5.6.3 SCHEDULE FOR DELIVERABLES - Option Period Reference Deliverable Due Date Task 1 Deliverable 5.6.1.1: Present complete PMP in Microsoft Project and briefing in Microsoft PowerPoint to CBO at CBO Central Office, 1722 Eye Street, Washington, DCWithin 15 calendar days after option year is exercised Task 1 Deliverable 5.6.1.2: Provide a full and complete list of names, Social Security Numbers, and home addresses of contractor personnel for the Background Investigation requirement within 5 calendar days from date of award. Provide a Staff Roster within five business days from date of award.Within 5 calendar days of award. Task 1 Deliverable 5.6.1.3: Provide evidence of contractor's staff training for VA's annual mandatory training required with 5 calendar days after option year is exercised. If contract performance crosses the anniversary date for VA's recurring annual training requirements, such training must be completed within 5 calendar days of the anniversary date. Training completed by contractor's staff under separate VA contracts will be accepted and evidence of such training, i.e., training certificates is submitted. Within 5 calendar days after option year is exercised Task 1 Deliverable 5.6.1.4: Provide monthly electronic contract status reports on the fifth day of each month. Monthly status reports will outline the progress of each task, identify contractor's accomplishments, contractor's project issues/concerns, and contractor's next month proposed activitiesOn the fifth day of each month Task 2 Deliverable 5.6.2.1: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria90 calendar days prior to the scheduled start of UAT Task 2 Deliverable 5.6.2.2: User Acceptance Test Cases: User Acceptance Test Plan: The Plan will outline the User Acceptance Testing Strategy to include the key focus areas, entry and exit criteria.30 calendar days prior to the scheduled start of UAT Task 2 Deliverable 5.6.2.3: User Acceptance Results Document: The User Acceptance test result will be documented in a mutually agreed upon format. It will document any issues found, such as bugs, crashes, or missing functionality.5 calendar days post UAT B5.7 PERIOD OF PERFORMANCE Services shall be required for 1 year and 2 option years. Work at a government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer. There is ten (10) Federal holidays set by law (U.S.C. Title 5 Section 6103): Under current definitions, four are set by date: New Year's DayJanuary 1 Independence DayJuly 4 Veteran's DayNovember 11 Christmas DayDecember 25 If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday. The other six are set by a day of the week and month: Martin Luther King DayThird Monday in January Washington's BirthdayThird Monday in February Memorial DayLast Monday in May Labor DayFirst Monday in September Columbus DaySecond Monday in October ThanksgivingForth Thursday in November NOTE: Work shall not commence during a Federal building closure (whether, building issues, Presidents death, etc ¦) B5.8 PLACE OF PERFORMANCE B5.8.1 The Contractor shall support this effort at the Department of Veterans Affairs, 1722 I Street, NW Washington, DC 20006, or at approved Contractor facilities as directed by the COTR and mutually agreed to by the Contractor. If the work is performed at the Department of Veterans Affairs, the COTR will provide adequate on-site workspace and ADP equipment for Contractor personnel. B5.8.2 All work shall be performed at the contractor's site within the Continental United States (CONUS). B5.8.3 Provision of Facilities - The Contractor shall provide all facilities required to support staff assigned to this contract including network connectivity, office space, furniture, personnel support accommodations, etc. The Contractor shall provide contract staff with end user computing equipment including common desktop computing software and hardware to perform the required services. The VA shall provide VA specific software such as VistA and Virtual Private Network access. The Contractor shall utilize VA provided software development and test accounts, document and requirements repositories, etc. as required for the development, storage, maintenance and delivery of products within the scope of this contract. The Contractor shall not transmit, store or otherwise maintain sensitive data or products in systems or media other than VA provided systems within the VA firewall. B5.8.4 Hours of service - contractor shall provide service during normal business hours from 8:00 A.M. to 4:30 P.M. Eastern Time (ET), Monday through Friday. B5.9 KEY PERSONNEL B5.9.1 Certain skilled experienced professional and/or technical personnel are essential for accomplishing the work to be performed. These individuals are defined as "Key Personnel" and are those persons whose resumes were submitted and marked by the vendor as "Key Personnel". Substitutions shall only be accepted if in compliance with "Substitution of Key Personnel" provision identified below. B5.9.2 The Contracting Officer may notify the Contractor and request immediate removal of any personnel assigned to the task order by the Contractor that are deemed to have a conflict of interest with the government or if the performance is deemed to be unsatisfactory. The reason for removal shall be documented and replacement personnel shall be identified within three business days of the notification. Employment and staffing difficulties shall not be justification for failure to meet established schedules. B5.10 SUBSTITUTION OF KEY PERSONNEL AND OTHER PERSONNEL CONSIDERATIONS B5.10.1 Personnel assigned by the Contractor to the performance of work on this order shall be acceptable to VA in terms of personal and professional conduct and technical knowledge. Should the assignment to this order of any person by the Contractor be deemed to conflict with the interests of VA, or in the event performance is deemed to be unsatisfactory at any time during the life of the task order, the Contracting Officer may notify the Contractor and request the person be immediately removed from the assignment. The reason for removal shall be documented and a request to receive personnel replacement within three (3) business days of the notification shall be made. Replacement personnel qualifications shall be equal to or greater than those of the personnel being replaced. Employment and staffing difficulties shall not be justification for failure to meet established schedules. B5.10.2 All Contractor requests for approval of substitutions hereunder shall be submitted in writing to the COTR and the Contracting Officer at least thirty calendar days in advance of the effective date, whenever possible, and shall provide a detailed explanation of the circumstances necessitating the proposed substitution, a complete resume for the proposed substitute, and any other information requested by the Contracting Officer necessary to approve or disapprove the proposed substitution. The COTR and the Contracting Officer will evaluate such requests and promptly notify the Contractor of approval or disapproval in writing. B5.10.3 The Contractor shall submit a resume of qualifications and the Contractor Personnel Change Control form to the PM and COTR and all other direct employees proposed for the project. The PM and COTR will approve all Contractor employees prior to bringing on duty via Contractor Personnel Change Request Form (Attachment D2). If, at any time from date of award to the end of the contract, Contractor personnel are no longer available, the VHA will approve the qualifications of proposed replacement personnel and shall reject individuals who do not meet the qualifications set forth herein. All Contractor employees are subject to immediate removal from performance of this contract when they are involved in a violation of the law, VA security, confidentiality requirements, and/or other disciplinary reasons. New personnel shall not commence work until all necessary security requirements, have been fulfilled and resumes provided and accepted B5.10.4 The VHA will not be liable for further payment of any Contractor employee that VHA requires the Contractor to remove from the performance of this contract. VHA's payment liability, for unsuitable Contractor employees, ends five working days after Contractor's receipt of "removal request."
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/VA/VAHAC741/VAHAC741/VA74113I0083/listing.html)
 
Document(s)
Attachment
 
File Name: VA741-13-I-0083 VA741-13-I-0083_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=593079&FileName=VA741-13-I-0083-000.docx)
Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=593079&FileName=VA741-13-I-0083-000.docx

 
Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 
Record
SN02970315-W 20130125/130123234048-ca65c503e393ff59206b3f75e3756001 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.