FY 24 Statement of Work OATI Transmission Service Request and ATC.pdf

CUI//PROCURE

Federal Energy Regulatory Commission – Office of Enforcement Statement of Work

1. BACKGROUND

The Federal Energy Regulatory Commission (FERC) is an independent agency that regulates the interstate transmission of electricity, natural gas, and oil. FERC’s Mission is to ensure reliable, efficient, and sustainable energy for consumers. Fulfilling this mission involves pursuing two primary goals:

Ensure that rates, terms and conditions are just, reasonable and not unduly discriminatory or preferential.

Promote the development of safe, reliable and efficient energy infrastructure that serves the public interest.

In an effort to support the first goal, the Commission protects consumers through market oversight and surveillance; assuring compliance with tariffs, rules, regulations, and orders; detecting, auditing, and investigating potential violations; and developing and formulating policies and regulations to address emerging issues. The Commission employs various methods in these activities, including:

Developing surveillance procedures to detect potential manipulation, anticompetitive behavior, and other anomalous activity.

Identifying potential subjects of nonpublic investigations.

Analyzing trading and other complex data related to manipulation or other improper conduct.

Analyzing long-term electric market trends.

Issuing, coordinating, and developing proposed policy reforms to address emerging issues affecting wholesale and interstate electric energy markets.

In support of these objectives, the Commission has contracted OATI to receive eTag data under Order 771 via the OATI webFERC solution. To supplement eTag data, the Division of Energy Market Oversight (DEMO) and Division of Analytics and Surveillance (DAS) in the Office of Enforcement (OE) are requesting access to the complete Transmission Service Request (TSR) and Available Transfer Capacity (ATC) databases. OE will use the TSR and ATC databases to monitor for the exercise of market power and market manipulation in the electricity markets. Currently, both TSR and ATC data are available only in disparate OASIS sites. The usability of each data source is limited because it is stored separately and inconsistently across transmission providers. In order to perform comprehensive and robust analysis, staff requires data from many transmission providers over periods of one or more years. Purchasing the two complete databases from OATI will save a significant amount of staff time downloading, standardizing and aggregating the data in preparation for analysis.

2. SCOPE

The scope of work includes, but is not limited to, labor, materials, hardware, software, administration, and management necessary to operate, support, maintain and improve/upgrade the webFERC database which houses TSR and ATC data. The scope includes providing the Commission access to all TSR and ATC data available in the Vendor’s systems.

3. OBJECTIVES

Commission program offices will use TSR and ATC data to support their respective missions. This includes, but is not limited to, surveilling the markets to detect potential market manipulation and anti-competitive behavior, evaluating whether market outcomes are just and reasonable, and better informing Commission policies and decision-making.

4. TASKS

The Vendor shall perform the following tasks:

4.1 TSR and ATC data management (initial set-up and on-going):

The Vendor shall populate the webFERC solution with the TSR and ATC databases.

The Vendor shall maintain a secure server environment and shall submit their annual SAS Type II or

SSAE 16 SOC (Type I, II, or III) audit report of their IT data center security controls, whichever reporting format is applicable.

The Vendor shall ensure data quality. Data available to the Commission shall accurately reflect TSR and ATC data available to OATI.

The Vendor shall ensure data is updated in a timely manner. Real-time updates are not required.

The Vendor shall provide configuration and data structure support. The database solution shall have a data structure that is consistent with best practices of database design allowing for efficient analysis of TSR and ATC using queries of varying complexity.

The vendor shall maintain and modify the database structure as FERC’s data uses evolve over time.

The Vendor shall maintain configuration management of the data that meets FERC’s policies regarding configuration hardening guidelines and obtain FERC written approval prior to making changes to the database structure.

The Vendor shall continue to operate under the Interconnection Service Agreement / Memorandum of Understanding (ISA/MOU) with the FERC signed in March 2013 to create the webFERC solution.

After the creation of the TSR data, the Vendor shall host all TSR data in the webFERC database for 2 years. After 2 years, the Vendor shall annually provide an electronic copy of expired data to the Commission in SQL form (including table structure definitions, insert statements and any relevant data views).

After the creation of the ATC data, the Vendor shall host all ATC data in the webFERC database for a sufficient period of time so as to allow the Commission to download the data into the Commission’s internal systems. This time period shall not be less than three (3) months.

The Vendor shall maintain and modify the database structure to maintain consistency with current TSR and ATC standards as they evolve over time.

The Vendor shall work with Commission staff to adapt and develop tables and views to improve the utility of the database to the Commission. The Vendor shall allocate up to 24 hours of consulting services per month to perform these tasks. If consulting hours for one month are unused they may be rolled over to the next month, never exceeding a total of 48 hours in any given month.

4.2 Access to the TSR/ATC data And Security Requirements

The Vendor shall provide FERC access to all TSR and ATC data available in its systems.

The Vendor shall provide a robust, dedicated and encrypted connection utilizing TLS 1.2. Please note that this security requirement is subject to data communications security requirements provided by OMB/NIST and may change to a more stringent standard at a future date. This connection should enable transfer of any query results to the Commission.

The Vendor shall ensure constant access to TSR and ATC data with 24 by 7 reliability (99.0% uptime)

The Vendor shall provide up to 50 credentials to access the database through the Vendor's proprietary user interface.

The Vendor shall provide FERC direct access to the database without requiring the use of a proprietary user interface. The TSR/ATC database solution shall be capable of efficient large query runs using SQL query language. FERC staff will develop and submit any queries, while the Vendor shall ensure that the database solution is sufficiently robust to process submitted queries.

o Examples of queries include:

All final ATC transactions for a given time, product, path, customer All TSR transactions for a given time, product, path, customer All ATC transactions of a certain product, for a given customer All TSR transactions of a certain product, for a given customer

4.3 Support and expert advice and assistance

The Vendor shall provide webSmart OASIS training covering ATC and TSR concepts once the solution is deployed.

The Vendor shall provide data documentation for the TSR and ATC data. This documentation must include a column description for all data columns and where applicable an Entity Relationship Diagram (ERD) and SQL statements required to relate tables within the data model.

The Vendor shall provide updates to data documentation as TSR or ATC data model changes.

The Vendor shall provide comprehensive training at least once a year and robust Helpdesk support for the webFERC database solution. This support shall be extended to include the TSR and ATC databases.

The Vendor will accommodate staff requests for training on specific matters.

The Vendor shall meet FERC policy regarding Incident Handling Process and Procedures.

4.4 Other Constraints

The following constraints apply to the proposed database solution:

The Vendor shall include all TSR and ATC data available in its systems via the webFERC solution.

The Vendor shall securely house and maintain the data.

The Vendor shall have expertise and experience in collecting, organizing, managing and storing TSR and ATC data. This expertise should include, at minimum, having successfully provided services as an approved OASIS service Agent.

The Vendor shall comply with all relevant federal information security standards regarding a secure VPN interconnection.

The Vendor shall communicate to FERC any unauthorized data disclosures and/or data breeches within two hours of discovery of the incident.

5. OTHER PERFORMANCE REQUIREMENTS

Not Applicable

6. SECURITY REQUIREMENTS

A security clearance is not required in performance of this effort.

6.1. Contractor Interfaces

Not applicable

6.2. Disclosure of Information

Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the Contracting Officer.

The contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

6.3. Limited Use of Data

Not Applicable

7. PLACE(S) OF PERFORMANCE

OATI systems and Commission Locations.

8. PERIOD OF PERFORMANCE

Base Period - 12 months from contract award.

Option Period I - 12 months from the end of the based period

Option Period II - 12 months from the end of option period I

Option Period III - 12 months from the end of option period II

Option Period IV - 12 months from the end of option period III

9. DELIVERABLES

The following deliverables will be required under the resultant contract:

Fully functional access to the TSR and ATC databases via the webFERC solution

Help desk access and performance commitments

Data Dictionary (with units for applicable fields, whether the value is unitless, or unit a not-applicable indicator) and entity-relationship diagram (ERD)

Change management documentation

System build, testing and production timeline

Weekly status reports (during deployment and system changes/upgrades only)

Ongoing Consulting Services

9.1. Project Plan

Not applicable

9.2. Monthly Status Report

Not Applicable

9.3. Final Report

Not Applicable

9.4. Deliverable Table

Not Applicable

9.5. Inspection and Acceptance Criteria

Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the place of delivery by the COTR.

9.6. General Acceptance Criteria

General quality measures, as set forth below, will be applied to each work product received from the contractor under this statement of work.

‐ Accuracy - Work Products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

‐ Clarity - Work Products shall be clear and concise. Any/All diagrams shall be

‐ Easy to understand and be relevant to the supporting narrative.

‐ Consistency to Requirements - All work products must satisfy the requirements of this statement of work.

‐ File Editing - All text and diagrammatic files shall be editable by the Government.

‐ Format - Work Products shall be submitted in hard copy (where applicable) and in media mutually agreed upon prior to submission. Hard copy formats shall follow any specified Directives or Manuals.

‐ Timeliness - Work Products shall be submitted on or before the due date specified in this statement of work or submitted in accordance with a later scheduled date determined by the Government.

10. QUALITY ASSURANCE

The COTR will review all listed deliverables periodically in order to ensure accuracy and quality of product.

11. ADMINISTRATIVE CONSIDERATIONS

11.1. Correspondence

To promote timely and effective administration, correspondence shall be subject to the following procedures:

a) Technical correspondence (where technical issues relating to compliance with the requirements herein) shall be addressed to the Contracting Officer's Technical Representative (COTR) with an information copy to the Contracting Officer (CO) and the Contract Administrator (CA).

b) All other correspondence, including invoices, (that which proposes or otherwise involves waivers, deviations or modifications to the requirements, terms or conditions of this SOW) shall be addressed to the Contracting Officer with an information copy to the COTR.

11.2. Points of Contact

11.2.1. Contracting Officer's Technical Representative (COTR)

a) The Contracting Officer's authorized technical representative, for this effort is as follows:

Federal Energy Regulatory Commission Office of Enforcement 888 1st Street, NE Washington, DC 20426 Denise Tabbs, 202-502-8315

b) The COTR is the individual within the Program Management function who has overall technical responsibility for this effort The COTR supports the CO/CA during administration of this effort by:

1) Making final decisions regarding any recommended rejection of deliverables;

2) Providing technical clarification relative to overall workload matters;

3) Providing advice and guidance to the Contractor in the preparation of deliverables and services;

4) Providing acceptance of deliverable products to assure compliance with requirements.

c) The COTR also provide technical direction to the Contractor, i.e., shifting work emphasis between areas of work; fills in details, or otherwise serves to accomplish the purposes of this effort.

Technical direction shall be within the general statement of work for this effort. The COTR does NOT have the authority to and may NOT issue any technical direction which:

1) Constitutes an assignment of work outside the general scope of this effort;

2) Constitutes a change as defined in the "Changes" clause;

3) In any way causes an increase or decrease in cost or the time required for performance;

4) Changes any of the terms, conditions, or other requirements of this effort; and

5) Suspends or terminates any portion of this effort.

d) All technical direction shall be issued in writing by the COTR or will be confirmed by the COTR in writing within 10 calendar days after verbal issuance. A copy of the written direction shall be furnished to the CO and the CA.

e) In addition to providing technical direction, the COTR will:

1) Monitor the Contractor's technical progress. including surveillance and assessment of performance, and recommend to the CO and CA, any changes in the requirement;

2) Assist the Contractor in the resolution of technical problems encountered during performance; and

3) Perform inspection and acceptance or recommendation for rejection of Contractor deliverables and identify deficiencies in delivered items. This does not replace any other quality assurance inspection requirements that are specified elsewhere within this SOW.

f) If in the opinion of the Contractor, any instruction or direction issued by the COTR is outside of their specific authority, the Contractor shall not proceed but shall notify the CO in writing within 5 working days after receipt of any instruction or direction, with an informational copy to the CA.

11.2.2. Contracting Officer

The Contracting Officer (CO) for this effort is as follows:

Federal Energy Regulatory Commission Procurement Operations Branch 888 1st St. NE Washington, DC 20426

11.2.3. Contract Administration

Not Applicable

11.2.4. INVOICING

The Contractor will submit an original invoice to:

Federal Energy Regulatory Commission Office of Finance

Attn: Deena Hamilton-Graham

888 1st Street, NE Washington, DC 20426

To constitute a proper invoice, the invoice must include the following minimum information and/or attached documentation:

‐ Name of business concern/letterhead;

‐ Invoice date and separate/distinct number;

‐ Contract and Task Order number;

‐ Description of services and dates upon which services were rendered;

‐ Payment terms;

‐ Name, title, phone number and complete mailing address of responsible official to whom payment is to be sent or to contact in case of a defective invoice;

‐ Total charges for the billing period.

12. TRAVEL

Not Applicable

13. CENTRAL CONTRACTOR REGISTRATION (CCR) - NEW CONTRACTS

Not Applicable

14. POST AWARD EVALUATION OF CONTRACTOR PERFORMANCE

Not Applicable

15. SECTION 508 COMPLIANCE REQUIREMENTS

Any/all electronic and information technology (EIT) procured through this effort must meet the applicable accessibility standards at 36 CFR 1194. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov.

16. GOVERNMENT FURNISHED PROPERTY/INFORMATION

Not Applicable

17. PERSONNEL REQUIREMENTS

Not Applicable