Notice ID: 36C10B25Q0009

The Contractor shall perform maintenance activities and implement maintenance upgrades to the QAWeb system including testing, deployment, production, and configuration management support.

The Contractor shall:

  1. Attend QAWeb Integrated Project Team (IPT) and Change Control Board (CCB) meetings by Teams Meeting or phone conversation. Typically, the IPT meetings are weekly and may include demonstration for any new functionalities to the QAWeb. Typically Change Control Board meetings are monthly and may coincide with the weekly IPT meetings. The Contractor shall provide technical insight into the complexity and sizing of alternative solutions associated with all user change requests. The Contractor shall provide technical recommendations on a quarterly basis to QAWeb IPT and CCB, in the form of email or ad hoc reports.
  2. The Contractor shall support QAWeb Application Software Releases that contain cumulative Change Control Board approved maintenance modifications to the QAWeb application, to include ongoing code maintenance and functional defect corrective work that is required to keep the application accurate; software releases computations valid; software releases operations in conformance with Congressional, Court-directed, Section 508, and CRISP security requirements; and generally to reflect in the QAWeb Application the VR&E Service’s business requirements for assuring quality in the administration of the Chapter 31 Benefit. The Contractor shall ensure that the software release code conforms to VA standards, and that errors are addressed and resolved in a timeframe to comply with the Systems Implementation Office (SIO) release schedule or urgent out-of-cycle release process as may be required. Test and implement VA generated IT security alerts, mandated security patches, emergency Congressional, Court, or White House mandates as well as maintain existing VA developed QAWeb application code. The Contractor shall provide QAWeb Application Software Release Packages and are due at least one week prior to the scheduled SIO Coordination Install dates. Historically over a 12-month period, QAWeb has averaged four scheduled releases, and up to three emergency code changes resulting in releases …

The Period of Performance (PoP) shall be 12 months from date of award with two 12-month option periods, and one optional task for transition support.  The total PoP shall not exceed 37 months.

Read more here.

Ad



Not Yet a Premium Partner/Sponsor? Learn more about the OS AI Premium Corporate and Individual Plans here. Plans start at $250 annually.

How useful was this post?

Click on a star to rate it!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Leave a Reply