7_27_22 Amendment 0002 Questions and Answers.pdf

PDF 169 KB Posted

Attached to
WAPA RMR/DSW GAP Analysis and Software Development
Solicitation number
89503122RWA000042
Issued by

About this file

This document provides an amendment to a request for proposal for a GAP analysis and software development opportunity with the Western Area Power Administration. The amendment includes responses to questions from interested offerors clarifying that the Rocky Mountain and Colorado River Storage Project entities share the same merchant function operated by CRSP, and that RMR provides BAA services for both regions. It also specifies that WAPA seeks detailed requirements and solution architectures from offerors in order to engage software vendors for contracts to join the SPP RTO market. The amendment maintains the original proposal due date of July 14, 2022. Interested parties can find the full solicitation on SAM.gov referencing number 89503122RWA000042. Questions should be directed to the contact listed via email only.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

(x)

89503122RWA000042

x x

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR

OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

LOVELAND CO 80539-8986

RMR

5555 E. CROSSROADS BLVD

ROCKY MOUNTAIN REGIONAL OFFICE

US DOE/WESTERN AREA POWER

WAPA (RMR)

PHOENIX AZ 85005-6457

DSW

PO BOX 6457

DESERT SOUTHWEST REGIONAL OFFICE

US DOE/WESTERN AREA POWER

WAPA (DSW)

07/27/20220002

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

07/01/2022

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

See Continuation Page(s).

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

Gregory K. Cagle

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

07/27/2022

Solicitation - 89503122RWA000042 Amendment 0002

RMR/CSRP GAP Analysis

The purpose of this Amendment is to provide responses to comments/questions:

A. The following responses comments/questions are provided:

Comment/Question 1: Do the RMR and CRSP entities share the same Merchant Function, or are there separate Merchant Functions for each organization? If separate, do they follow similar processes and use similar technologies for trading, or are the quite different? The following statement is included at the CRSP website, but it’s not clear if they have their own marketing business processes and technologies:

“CRSP MC markets power from the Colorado River Storage Project, its participating projects (Dolores and Seedskadee) and the Collbran and Rio Grande projects.”

Response to Comment/Question 1: Yes, CRSP performs Merchant function for both CRSP and RMR.

Comment/Question 2: Does the RMR BAA provide BAA services for the CRSP Marketing arm, or does CRSP run its own BAA function?

Response to Comment/Question 2: Yes, RMR provides BAA WACM services for CRSP.

Comment/Question 3: In reading the PWS, there is an emphasis on requirements definition and solution architecture definition. Is it RMR/CRSP’s intent to use the SPP RTO West Gap Assessment to determine whether or not you want to participate in the market (cost, HR impact, etc.), or have you already decided to join the SPP RTO and you want to define the requirements / solution architecture in enough detail to engage vendors and negotiate and sign software contracts? If you are looking to make a market go/no-go decision then the requirements generally can be a bit high level. If you are looking to engage vendors and definitely join, then you need detailed technical requirements which increases scope and costs substantially.

Response to Comment/Question 3: WAPA is seeking detail requirements / solution architecture to engage vendors for software contracts.

Comment/Question 4: This question builds on Question #3 with respect to vendor engagement as a part of the Gap Assessment process. Does WAPA RMR/CRSP want the respondent to evaluate software vendor RFP responses as a part of the Gap Assessment scope? If you are looking for RFP response evaluation, the timelines and level of effort become dependent on the WAPA RFP process and the vendor response timeline. This request increases scope and may add some risk to delivery in the one-year timeframe

Response to Comment/Question 4: No, we are not looking for respondent to evaluate software RFP

Comment/Question 5: Only one SPP full RTO has been implementation in the last 5 years, a small gen-only BAA.

Response to Comment/Question 5: Should there be limited SPP RTO implementation in the last 5 years, offerors should include al consulted efforts for SPP for the original SPP RTO market 2004-2008 (day-

Solicitation - 89503122RWA000042 Amendment 0001

RMR/CSRP GAP Analysis ahead and real-time) and also the implementation of the SPP Integrated Marketplace which went live in 2014.

B. The date and time for the Request for Proposal closing remains as stated in Amendment 0001.

SF 30 (11_2016) (30)
Amendment 0002 Cont Page

File details come from the government source that posted it. Updated .