The file's text, extracted by GovTribe without its formatting.
FERC-13-P-0050 CEDMS Q&A
| 1 |
| On pg5, 4.1, FERC indicates a desire for “direct access in a relational database.” Does ‘direct access’ translate to SQL queries running as read-only transactions? Or does FERC expect to make/apply updates to the database via SQL queries? Please clarify? Also, if permissible to share, for what business purpose/end will these changes be made (this may help us understand training needs and resource allocation)? |
| Direct access includes read-only transactions against the tables, views and procedures created by the vendor. FERC also expects to have the ability to write, to a database, custom tables, views and procedures that facilitate FERC’s analysis of the data provided. |
| 2 |
| On pg5, 4.1, FERC mentions that “the Vendor shall provide configuration and data structure support.” Does FERC expect the Offeror to make changes to the database structure as part of this service (e.g., structure changes as related to market changes)? Or does FERC simply require access to a subject-matter expert to assist in understanding the data structure with regard to SQL queries, data dependencies, etc.? We are seeking further clarity around desired expectations. |
| FERC is expecting the vendor to make changes to the database as the market structure changes and provide support to implement and explain those changes. Additionally, FERC would expect to work collaboratively with the vendor to augment the data structure to facilitate FERC’s analysis of the data provided. |
| 3 |
| On pg5, 4.1, FERC indicates that “the Vendor shall work with the Commission to develop and implement automated procedures, queries, indexes, and other structures that will augment Commission access to relevant data.” Can you please clarify your interpretation of “access to relevant data”? Are development and implementation of these automated procedures, queries, etc., a part of initial deployment only, or expected to be an ongoing exercise; if the latter, at what projected (estimated) frequency? |
| Augmenting “access to relevant data” is intended to indicate tables, views and/or procedures that will improve the efficiency of frequent queries and facilitate the use of the database. Development and implementation of these automated procedures, queries, etc. are expected to be an ongoing interactive exercise between the vendor and FERC. While it is difficult to estimate the frequency in which this support would be required (see example in Q4, below), FERC expects that the type of support needed would most frequently involve assistance with assuring the efficiency and accuracy of procedures, queries, etc. developed by FERC rather than full development and implementation of database code. FERC would expect a budgeted number of hours for this type of support, in the order of five to ten hours per month, to be provided as part of the vendor’s proposal. |
| 4 |
| On pg. 5, 4.1, FERC mentions that “the Vendor must provide a data storage environment with read and write capability.” Can FERC provide examples of what type of ‘write’ capabilities you foresee being required? |
| FERC expects to use write capability to improve the efficiency of repeated activities for which we intend to use the database solution. For example, FERC may need to calculate LMP values at aggregate nodes by hour using diverse bundles of pnodes. Because FERC would be using this calculation daily, we could possibly create a stored procedure that automates generation of a daily table that contains the calculated aggregate nodes. |
| 5 |
| On pg5, 4.2, FERC mentions a desire for efficient and robust query performance. Can FERC provide any insight into their expectations around query response times? |
| FERC would expect that the offeror provides an explanation of its database infrastructure that would ensure efficient and robust query performance. As described in the Section 4.2 of the Statement of Objectives, “The Vendor is encouraged to provide the technical specifications of the hardware that will house the solution as well as the database software platform.” |
| 6 |
| With respect to training (4.3), what are FERC’s expectations around the initial training session and twice-annual training sessions? For example, should we plan for a certain number of days of training? How much detail does the team desire with regard to the content/data as well as SQL and database queries? We can certainly propose an agenda, but a framework of expectations will help us ensure we are meeting each group’s needs. |
| The initial training session should include (1) a general introduction to the database solution and what data it contains, (2) an in-depth review of the data documentation and structure and (3) a review of any database objects provided by the vendor to facilitate data use and analysis. The subject of the twice annual trainings will be mutually agreed upon by FERC and the vendor. Subjects may include new-hire training, reviews of database updates and changes, and query optimization. |
| 7 |
| On p6 under 6.0 Deliverables, FERC is requesting the following deliverable: Data Dictionary and entity-relationship diagram (ERD). What is FERC’s expectation around changes following initial delivery? What qualifies as an item requiring a new/updated dictionary or status update? Our team strives to manage this carefully, since database changes tend to affect internal processes. |
| FERC would expect that any change in the database that requires an update to the ERD or data structure would be documented and shared with FERC. |
| 8 |
| Disaster Recovery (DR). Can FERC provide input regarding the expected Recovery Point Objective (RPO) and Recovery Time Objective (RTO)? Are there any additional requirements related to DR? |
| RPO of 4 hours |
RTO of 12 hours
| 9 |
| Does FERC require Mon-Fri 8x5 or Mon-Sun 24x7 support? |
| FERC requires Mon-Friday 8x5 support consistent with Eastern Prevailing Time business hours. |
| 10 |
| Will there be an opportunity to present our solution to respective stakeholders following submission of response? |
| No, solicitation does not provide for product demos. |
| 11 |
| Beginning on page 15 of the Solicitation and continuing through page 39 there is a list of FAR provisions-- is acceptance of all of these provisions by the respondent assumed if no exceptions are identified in the submission? |
| Yes, these are the expected clauses in the contract award. Failure to meet contract requirements will result in contract termination. |
| 12 |
| For FAR 52.227-14 Rights in Data - please explain FERC's need or requirement for "unlimited rights" to data that would be provided by the respondent; specifically, does FERC need to be able to "disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly" the Comprehensive Electric Market Data? If the extent of this right is not acceptable to the respondent should this be highlighted in the non-price exceptions? Should the respondent propose acceptable rights in data? |
| For data and software first produced for FERC under this contract, FAR 52.227-14 shall apply. |
For data and software that the Offeror currently provides under Commercial End User License agreements, Offerors shall submit a copy of their Commercial End User License Agreement with their proposal. The Agreement can be submitted as an Appendix and will not count toward any page limits. The Agreement will be incorporated by reference to the contract to the extent the license is consistent with Federal law and otherwise satisfies the Governments needs.
| 13 |
| Please clarify the Price Proposal details on page 14 of the Solicitation: it states that the proposal should contain firm, fixed prices and extended dollar amounts for each of the CLINS identified in Section B. Questions are: |
· Does Section B begin on page 3?
· What are the individual CLINS?
· Is it acceptable to propose pricing for components that meet the basic requirements and then also propose one or more optional add-on components that add incremental value to the solution beyond meeting the basic requirements?
Please refer to Section A.2 Price/Cost Schedule.
Offerors may submit multiple offers. Pricing for Optional Add-on components will be considered a multiple offer and will be processed in accordance with FAR 52.212-1 (e) Multiple Offers.
NOTE: This provision was incorporated by reference; see Block 27a of SF 1449 on page 1 and page 12. Provisions and clauses incorporated by reference have the same force and effect as those included in full text. Full text is available at http://acquisition.gov/far/index.html
| 14 |
| What is a "price related exception" on PG 14 of the CEMDS document? |
| Price related exceptions are exceptions, assumptions, and/or constraints that apply to the pricing data submitted. |
| 15 |
| How many users will there be? The CEMDS document refers to training for 50 users. Is that the expected user count? |
| FERC expects that the user base for this product will be approximately 50. Nonetheless, user count may increase in the future. FERC requests vendors to submit pricing for |
(1) a site license of an unlimited user base (FERC currently employees ~1200) OR
(2) pricing for fifty (50) licenses and propose the cost for additional licenses in increments of ten (10) users.
Offerors may opt to submit pricing under both of the scenarios depicted above. If so, Offerors must submit as two separate volumes and the proposals will be treated as multiple offers as described in question 13 above.
| 16 |
| For the SAS Type II Audit Report - we use a colocation site for our solution and they require a non-disclosure to share the full Audit Report. We can share their Summary Report SSAE - 16 SOC I Type II Summary Report. This includes an Auditors Statement and the Table of Contents. Will this meet the need or will the FERC sign a non-disclosure so that they can release the entire report? |
| Audit Report is required as part of proposal submission. In order to expedite the process, the NDA may be submitted to FERC prior to submission of the proposal so we may sign and return. |
| 17 |
| What does "front end and back end" access to the database refer to on page 5 of the CEMDS document? Is the FERC also requiring that the respondents provide a front end User Interface as well as Data Base access? |
| Yes. FERC is requiring both a front-end and back-end user interface. FERC considers front-end access as a GUI/browser-based application that allows users to explore CEMDS data. FERC considers back-end access as the ability to query the CEMDS data using SQL (please see Section 4.2, bullet 3 in Statement of Objectives) |
| 18 |
| What are FERCs "Interconnection Service Agreements" referred to on page 5 of the CEMDS document? Is this the Service Agreement attached to RFP? If so are we expected to execute this agreement prior to the response or just commit to meeting the requirement? |
| ISA is the included as attachment to the RFP. In proposal response Offerors shall commit to meeting the requirement. Agreement must be executed by Awardee prior to “go-Live” (i.e. establishing connection to FERC). Failure to execute the Agreement will result in contract termination. |
| 19 |
| On page 5 FERC requires Generation outages information. What source of historic, current and planned outages is the FERC seeking? |
| FERC is seeking all public outage information, both unplanned and planned, both historic and current. The offeror may offer other outage data in its proposal. |
| 20 |
| On page 5, FERC requires Transmission data, but the data described mostly includes information surrounding outages. Would FERC consider proposals that provide additional transmission data such as transmission service reservations and interconnection queues? |
| The list of required data elements in the solicitation was intended to provide a minimum baseline for offerors. |