XBRL_Solicitation_89603019Q0032.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO. DUNS: DUNS+4:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24.

ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS 82

40763

See SCHEDULE

89603019Q0032 02-22-2019

Hye Park and Sonja Ablola 202-502-8128 or -8694 03-22-2019 12:00

00039 Federal Energy Regulatory Commission Procurement Division Attn: Hye Park (202) 502-8128 or -8694 888 First Street, NE, Room 4J Washington DC 20426

X

813920

$15 Million

N/A

X

00039

Federal Energy Regulatory Commission Warehouse P-1 Attn: TBD 888 First Street, NE, Warehouse P-1 Washington DC 20426

00039

Federal Energy Regulatory Commission Procurement Division Attn: TBD 888 First Street, NE, Room 4J

00039

Federal Energy Regulatory Commission Division of Financial Services Attn: Payment/Invoice 888 First Street, NE, Room 42-71

See CONTINUATION Page

The purpose of this RFQ is to purchase XBRL and related support and maintenance.

Questions Due NLT 12pm EST, 3/1/2019 to Hye.Park@ferc.gov and Sonja.Ablola@ferc.gov Quotes Due NLT 12pm EST, 3/22/2019 to Hye.Park@ferc.gov.

and Sonja.Ablola@ferc.gov Please provide your most favorable discount to the Gov't.

Notice: This procurement applies to the following forms:

Form-1, Form-2, Form-6, Form-60, Form-714, Form-3Q Gas, Form-3Q Elec and Form-6Q

It is possible that subsequent to award FERC may identify additional forms that need to be converted to XBRL. FERC reserves the right to increase the contract value by up to 50% on a non-competitive basis consistent with the changes paragraph at 52.212-4 (c).

This procurement is being conducted consistent with FAR Subparts 13.1 and 13.5.

See CONTINUATION Page

X X

A.2 PRICE/COST SCHEDULE

ITEM INFORMATION

ITEM

NUMBER

DESCRIPTION OF

SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

00001 SOW Tasks 1 thru 4:

Task 1. XBRL Project Management

Task 2. XBRL Taxonomy and Validation Development

Task 3. XBRL Training

Task 4. Development, Testing, Pre-Deployment, and Preparation for Transition to Operations

This CLIN will be exercised and funded at award.

This is a Firm Fixed Price

CLIN.

Offorer shall propose invoice schedule. See proposal instructions.

Contract Period: Base POP Begin: 04-22-2019 POP End: 01-21-2020

1.00 LO __________________ __________________

00003 SOW Task 7. Security Requirements

This CLIN is not separately priced. The contractor shall comply with the SOW Task 7 Security Requirements during the performance of the contract. Cost for Security Requirements shall be included in the pricing for the respective CLINs.

Contract Period: Base POP Begin: 04-22-2019 POP End: 01-21-2020

00004 SOW Task 8. Conversion of VFP data for prior years up to 7 years (Optional).

This CLIN is Firm Fixed Price per year of data.

One Lot equals one year of VFP data.

This is an Optional CLIN.

Contract Period: TBD POP Begin: TBD POP End: TBD

FERC does not know with certainty when this CLIN will be exercised;

however, FERC anticipates that this CLIN will be exercised in the base period and/or option period 1.

7.00 LO __________________ __________________

00005 SOW Task 9. XBRL Expertise/Consulting Services

(100 hours of SME Level

III)

This is a Labor Hour CLIN.

This CLIN is for up to 100 hours of SME Level III consulting hours at a fixed labor rate of $_______________ per hour. Work under this CLIN will be authorized via written work orders issued by the COR.

This CLIN will be exercised and funded at award.

Contract Period: Base POP Begin: 04-22-2019 POP End: 01-21-2020

The POP for this CLIN may be extended as Optional CLINs are exercised.

00006 SOW Task 11. Over and Above (Optional)

This is a Time and Material

CLIN.

This CLIN will be exercised and funded at award.

This CLIN is established to cover any unanticipated costs related to CLINs 00001, 10002, and 00004 that could not have been anticipated at date of award.

See the table provided below for the labor categories and rates for this CLIN.

Work under this CLIN shall be authorized via written work orders issued by the

COR.

Contract Period: Base POP Begin: 04-22-2019 POP End: 01-21-2020

The POP for this CLIN may be extended as Optional CLINs are exercised.

00007 Other Direct Costs (ODCs) for CLINs 00001 and 10002.

This CLIN will be exercised and funded at award based on any ODCs identified in the successful offeror's quote.

This is a Firm Fixed Price

CLIN.

Contract Period: Base POP Begin: 04-22-2019 POP End: 01-21-2020

The POP for this CLIN may be extended when CLIN 10002 is exercised.

10002 SOW Task 5 and Task 6:

Task 5. Deployment to Production (Optional)

Task 6. Operations, Maintenance and Support (Optional)

This is an optional CLIN.

This is a Firm Fixed Price

CLIN.

Contract Period: Option Period 1 POP Begin: Based on the final ruling from the Commission adopting the final Taxonomy POP End: Plus one year

12.00 MO __________________ __________________

10003 SOW Task 7. Security Requirements

This CLIN is Firm Fixed Price per month.

This is an Optional CLIN.

Contract Period: Option Period 1 POP Begin: Based on the final ruling from the Commission adopting the final Taxonomy POP End: One year

20002 SOW Task 10 - Operations, Maintenance and Support

This is a Firm Fixed Price

CLIN.

Contract Period: Option Period 2 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN

10002. The exact dates are TBD based on Commission rulings.

20003 SOW Task 7. Security Requirements

This CLIN is Firm Fixed Price per month.

This is an Optional CLIN.

Contract Period: Option Period 2 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 10003. The exact dates

30002 SOW Task 10 - Operations, Maintenance and Support

This is a Firm Fixed Price

CLIN.

Contract Period: Option Period 3 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 20002. The exact dates

30003 SOW Task 7. Security Requirements

This CLIN is Firm Fixed Price per month.

This is an Optional CLIN.

Contract Period: Option Period 3 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 20003. The exact dates

40002 SOW Task 10 - Operations, Maintenance and Support

This is a Firm Fixed Price

CLIN.

Contract Period: Option Period 4 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 30002. The exact dates

40003 SOW Task 7. Security Requirements

This CLIN is Firm Fixed Price per month.

This is an Optional CLIN.

Contract Period: Option Period 4 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 30003. The exact dates

50002 SOW Task 10 - Operations, Maintenance and Support

This is a Firm Fixed Price

CLIN.

Contract Period: Option Period 5

POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 40002. The exact dates

50003 SOW Task 7. Security

This CLIN is Firm Fixed Price per month.

This is an Optional CLIN.

Contract Period: Option Period 5 POP Begin: TBD POP End: TBD

The POP for this CLIN will be 1 year following CLIN 40003. The exact dates

GRAND TOTAL __________________

Labor Categories and Rates for CLIN 00006

Labor Category Description Unit of

Measure

Labor Rate for Base Period

Labor Rate for Option Period 1

Subject Matter Expert III

Level III (CZ03) - Provide technical, managerial, and administrative direction for problem definition, analysis, requirements development, and implementation for complex to extremely complex systems in the subject matter area. Make recommendations and advise on organization-wide system improvements, optimization or maintenance efforts in the following specialties:

information systems architecture; networking;

telecommunications; automation;

communications protocols; risk management/electronic analysis; software;

lifecycle management; software development methodologies; and modeling and simulation.

Commensurate experience in IT and in new and related older technology that directly relates to the required area of expertise.

Hour $ $

Database Specialist II

Level II (AX02) - Evaluate and recommend available DBMS products to meet user requirements. Determine file organization, indexing methods, and security procedures for specific user application. Commensurate experience and education.

Hour $ $

Project Manager III

Level III (CR03) - Typically oversee all aspects of the project, leading a team on large projects or a significant segment of large and complex projects. Analyze new and complex project-related problems and create innovative solutions that normally involve the schedule, technology, methodology, tools, solution components, and financial management of the project. Provide applications systems analysis and long and short-range plans for application selection, systems development, systems maintenance, and production activities for necessary support resources. Commensurate experience and education for the specific level.

Hour $ $

Test Engineer

Evaluate, recommend, and implement automated test tools and strategies. Design, implement, and conduct test and evaluation procedures to ensure system requirements are met. Develop, maintain, and upgrade automated test scripts and architectures for application products. Write, implement, and report status for system test cases for testing.

Analyze test cases and provide regular progress reports. Serve as subject matter specialist providing testing know-how for the support of user requirements of complex to highly complex software/hardware applications. Direct and/or participate in all phases of risk management assessments and software/hardware development with emphasis on analysis of user requirements, test design and test tools selection.

Hour $ $

Technical Writer III

Level III (DF03) - Write and/or edit technical documents, including business proposals, reports, user manuals, briefings and presentations, functional descriptions, system specifications, guidelines, special reports, and other project deliverables to meet contract requirements. Develop outlines and drafts for review and approval by technical specialists and project management ensuring that final documents meet applicable contract requirements and regulations. Research and gather technical and background information for inclusion in project documentation and deliverables. Consult relevant information sources, including library resources, technical and financial documents, and client and project personnel, to obtain background information, and verify pertinent guidelines and regulations governing project deliverables. Commensurate experience, education, and level of supervision and direction.

System Architect II

Level II (DB02) - Establish system information requirements using analysis of the information engineer(s) in the development of enterprise-wide or large-scale information systems. Design architecture to include the software, hardware, and communications to support the total requirements as well as provide for present and future cross-functional requirements and interfaces.

Ensure these systems are compatible and in compliance with the standards for open systems architectures, the OSI and ISO reference models, and profiles of standards -such as IEEE OSE reference model - as they apply to the implementation and specification of information management solution of the application platform, across the API, and the external environment/software application.

Ensure that the common operating environment is compliant with the Agency enterprise architecture and applicable reference models. Evaluate analytically and systematically problems of workflows, organization, and planning and develop appropriate corrective action. Provide daily supervision and direction to staff.

Hour S $

System Programmer

Create and/or maintain operating systems, communications software, data base packages, compilers, assemblers, and utility programs. Modify existing software as well as create special-purpose software to ensure efficiency and integrity between systems and applications.

A.3 DELIVERY SCHEDULE

ITEM NUMBER QUANTITY DELIVERY DATE

00001 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE Washington, DC 20426

USA

1.00

MARK FOR: 202-208-0200

00003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

00004 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

7.00

00005 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

00006 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

00007 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

10002 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

12.00

10003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

20002 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

20003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

30002 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

30003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

40002 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE Washington, DC 20426

40003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

50002 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

50003 SHIP TO: Federal Energy Regulatory Comm Attn: P-1 Warehouse 888 First Street NE

Statement of Work (2/22/2019)

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:

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

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

Controlled Unclassified Information

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:

• Collecting annual and quarterly reports of electric utilities, natural gas and oil pipeline companies and licensees.

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

• Analyzing long-term trends in gas and electric markets.

• Developing, issuing, and coordinating policy reforms to address emerging issues affecting wholesale and interstate electric and gas energy markets.

On April 16, 2015, the Commission issued an order announcing its intention to replace its current electronic filing format for financial forms data collections currently submitted through Visual FoxPro (VFP), noting that it would pursue Extensible Markup Language (XML) format as the replacement. This includes Forms 1, 1-F, 2, 2- A, 3-Q electric, 3-Q gas, 6, 6-Q, FERC-60, and FERC-714 (collectively “VFP Forms”).

Forms are collected using the VFP application, which the Commission distributes to filers to enter their data.

The VFP application has limited validations, mostly to ensure proper data types (e.g., a number field does not allow character data). The filer enters the information into the VFP application and submits the data to FERC via the application. There is a separate VFP application for each VFP Form.

The main steps of the existing form collection process are:

1. Filer prepares data and submits each form separately through a VFP application1 provided by FERC

2. The VFP application packages and submits the data to FERC

3. FERC receives the VFP submissions

1 The VFP application creates a visual representation of the form that is fillable and requires the filer to type in the data.

http://www.ferc.gov/docs-filing/forms/eforms-refresh.asp

4. FERC validates the data

5. FERC loads data into database

6. FERC renders each submission into a PDF and posts it to eLibrary

7. Data is made available to the public in yearly produced zipped files available on the FERC website containing VFP coded data

One of the driving factors for reforming and modernizing the data collection process is the age and maintainability of the current database application and collection process. Microsoft no longer supports VFP.

Microsoft released the last version of VFP in 2007 and terminated support in 2015. This poses significant software security issues for filers and FERC.

The Commission conducted an XBRL assessment (Attachment 1) to obtain recommendations to replace the VFP forms with XBRL. After reviewing the XBRL assessment, FERC has identified the XBRL standard over custom XML code as the most efficient solution to provide the needed functionality of the Forms. XBRL builds upon XML by adding features important to business reporting, improving efficiency, and reducing burden on FERC staff to make changes to the Forms in response to regulatory changes to the collection of Forms data.

3. OBJECTIVE/SCOPE

The objective of this requirement is to replace the VFP Forms and applications with a technical XBRL solution that allows filers to file in a system that uses XBRL and to allow Commission staff to update taxonomies2, filing, and reporting requirements for these Forms independent of IT resources. The objective is to provide subject matter expertise and XBRL transition technical support, and to provide ongoing operational and technical support. The contractor shall develop a FERC taxonomy and necessary components with business analysts and IT staff to ensure filers can file Forms data with the Commission using XBRL.

The contractor shall provide XBRL consistent with standards set by XBRL US, such that upon completion the FERC taxonomy shall be certified by XBRL.US.

2 For purposes of this document, we shall use interchangeably taxonomies and FERC taxonomy. A FERC taxonomy means the collection of all taxonomies necessary to cover the filing and data collection requirements of all VFP Forms.

https://ws.sp.ferc.gov/CIO/OCIO/Team%20Documents/XBRL/Atch%201%20-%20FERC%20XBRL%20Assessment%20Final%202018-05-17%20Redacted.pdf https://software.xbrl.org/

In addition to development of a FERC taxonomy, which is the preliminary requirement to the complete XBRL solution, the solution shall include:

a. develop, test, implement and operate a comprehensive technical solution for forms data collections that accommodates all changes to the collection of Forms “VFP Forms” 1,2,6,60, 714 and related sub-forms;

b. develop, obtain FERC approval and deploy an XBRL taxonomy for Forms 1,2,6,60, 714 and related sub-forms data that incorporates industry input, including that of software vendors (FERC taxonomy);

c. advise and guide business analysts, program office staff, and Chief Information Officer (CIO) staff through the development, testing, acceptance, and implementation of an XBRL taxonomy;

d. provide a schedule of actions and milestones required to replace the VFP forms with XBRL;

e. implement the proposed schedule and replace VFP with updated forms collections;

f. provide an XBRL specialist and training for business analysts and non-IT staff to implement changes to the taxonomy;

g. identify IT infrastructure support requirements (e.g. hardware, software) to plan, design, develop, test, deploy, operate, and maintain proposed technical solution.

h. integrate the collection processes into the FERC systems. The XBRL implementation shall cover the processes to collect process and load the XBRL filings into a database. There are four points of integration:

• Submission process - the contractor for accepting XBRL filings shall create a submission process.

• Publishing rendered XBRL per the formats provided on FERC.gov – The contractor shall create a process to publish the Forms as pdfs and html, in eLibrary, and make publicly accessible in a human-readable format, through other means with COR approval.

• Database access to the XBRL forms database - The XBRL database shall be implemented in SQL Server. The contractor shall provide the process to extract XBRL data, including instructions on how to develop the database.

http://www.ferc.gov/docs-filing/forms/eforms-refresh.asp http://www.ferc.gov/docs-filing/forms.asp#1

• Access to data within the XBRL database – The contractor shall provide instructions on how to connect and query the XBRL database. The instructions shall provide access for staff and for applications such as SAS or SQL Server to connect and query XBRL data.

To accommodate the Commission’s Notice of Proposed Rulemaking (NOPR) and Final Rule schedule and to implement solutions that may be needed during transition to operations, i.e. after filers make first submissions in XBRL, the XBRL database solution shall be tested and ready for deployment within nine (9) months of contract award.

Notice: This procurement applies to the following forms: Form-1, Form-2, Form-6, Form-60, Form-714, Form-3Q Gas, Form-3Q Elec and Form-6Q. It is possible that subsequent to award FERC may identify additional forms that need to be converted to XBRL. FERC reserves the right to increase the contract value by up to 50% on a non-competitive basis consistent with the changes paragraph at 52.212-4 (c).

PLACE OF PERFORMANCE

The location of the work performed under this requirement shall be: 888 First Street NE, Washington DC, 20426.

TASKS

The contractor shall complete the following tasks described below:

Task 1: PROJECT MANAGEMENT/ KEY PERSONNEL

1.1 Single Point of Contact

The Contractor shall provide a single point of contact, Contractor Project Manager, for the management of the project and coordinate with the Contracting Officer’s Representative (COR). The point of contact shall be responsible for ensuring that the services and deliverables required by FERC are provided in accordance with the contract requirements.

1.2 Pre-Kick-Off Meeting Prep/ Coordination and Draft Project Plan

The contractor shall prepare copies of the draft project plan that was submitted with the proposal for distribution at the Kick-Off meeting.

1.3 Kick-off Meeting

The Contractor shall meet with the COR and other FERC representatives at the 999 North Capitol Street NE, Washington DC within ten (10) business days of the award to discuss all current activities and the scope of work. Two business days prior to the kickoff meeting, the contractor shall provide an agenda for the meeting.

At the kickoff meeting, the contractor shall provide the draft project plan and timeline, updated roster of key personnel, and proposed communication schedule.

1.4 Weekly Meetings

The Contractor shall meet weekly with the COR, technical staff and other stakeholders to discuss project updates and critical issues to be resolved. Notify the COR, in writing, within one (1) business day, if issues arise that prevent the Contractor from attending a meeting. Notify the COR, in writing, within three (3) business days of any event which will create a delay in the schedule and/or result in additional cost to FERC.

All notifications shall be submitted electronically to the COR in writing and shall document the reason for the delay, the status of the budget, the impact on the project, and the action the Contractor is taking to bring the project back on schedule.

1.5 Technical Meetings

The Contractor shall participate in or facilitate meetings, conference calls, and/or workgroups with FERC Program staff and industry stakeholders. Within three (3) business days of the meeting, develop and provide brief, summarized minutes after meetings that: identify the attendees, summarize the meeting, and document all action items.

1.6 Project Plan

Within 1 week following the kick-off meeting, the contractor shall provide in electronic format an updated project plan to include the following:

Indication within 17 calendar weeks from the contract award date to delivery of the XBRL taxonomy for the VFP Forms.

The project plan shall indicate within 9 months from the contract award date to the tested, accepted and deployment-ready system is completed. Deployment ready includes having converted and transferred all historical VFP submissions to the XBRL database and conversion of three (3) prior years of VFP submissions to

XBRL.

Estimated filings per year by Form type to be converted

Form Type Annual Count

Form-1 204

Form-2 170

Form-6 241

Form-60 40

Form-714 106

Form-3Q Gas 680

Form-3Q Elec 816

Form-6Q 964

1.7 Project Management and Reporting

The Contractor shall:

A. SDLC. Follow the Systems Development Life Cycle (SDLC) policy (Attachment 2) or deliver the documentation required by FERC of the SDLC when using Agile or similar development methodology on the project collaboration website.

B. Monthly Status Report. Provide a Monthly Status Report for each monthly reporting period, due on or before the 7th business day after the end of the reporting period. This monthly report shall cover all services covered by this agreement. This report shall contain seven (7) sections:

1. Project description,

2. Activities planned for the upcoming reporting period,

3. Activities performed during the prior reporting period,

4. Progress on deliverables as stated in the Project Management Plan

5. Project issues and risks that may impact schedule, budget, and/or quality,

6. Details of the resources used, total hours, and total dollars expended, and https://ws.sp.ferc.gov/FERCollaborate%20Library/FERC%20SDLC%20V4.0%20May%2031%202018.pdf

7. Any other program specific requirements (i.e., quarterly reporting, annual reporting, various module updates, etc.).

C. Final Report. Provide a final report that shall include all previously delivered documents, templates and meeting material or presentation slide decks, as well as any incorporated corrections/clarifications based on comments and questions provided by the Government during meetings and presentations. The final deliverable is due no later than 10 business days before the end of the period of performance

Task 2: XBRL Taxonomy and Validation Development.

3.1 Develop and complete a FERC taxonomy

The contractor shall develop taxonomies for the VFP Forms data. Additionally, the contractor shall work with business users and IT staff during the process to create sample XBRL instance documents from previous VFP submissions as a starting point for taxonomy development. This taxonomy will incorporate new fields and concepts from the current data required to be submitted as footnotes as much as possible, to eliminate the need to report data as a footnote. Once the taxonomy is completed, the Contractor shall obtain final approval (via email) within 14 days on the taxonomies from the COR.

3.2 Develop and complete validation rules currently in the VFP forms into an XBRL format

The contractor shall create validation rules in XBRL for the VFP Forms using the rules currently provided in the existing VFP Forms, and develop additional rules as requested with input from program office subject matter experts. The contractor shall obtain final approval (via email) for the validation rules in XBRL from the COR.

The contractor alerts the COR that the product is complete, the COR (working with FERC staff) verifies completion and replies to the contractor.

3.3 Integrate the XBRL System with FERC’s Current Systems and Environments

The contractor shall provide a fully integrated development, test and production environment for the XBRL data collection system within the existing FERC infrastructure to include changes to applications (see Attachment 3 for list) and databases as required.

https://ws.sp.ferc.gov/CIO/OCIO/Team%20Documents/XBRL/Atch%203%20List%20of%20FERC%20infrastructure,%20application%20and%20databases.zip

FERC will provide the following:

• Windows 2012 R2 Servers

• Microsoft SQL Server 2014 Databases

• SFTP Servers

• Networking and Internet availability

• Windows 10 desktop client (for product development) o Note: Current desktop client is Windows 7 but will be Windows 10 at the time of award

• Applications at Attachment 3

The contractor shall create three instances of the XBRL data collection system to include a development environment to be used to develop software, databases, tools, and reports; a test environment to test the completed XBRL data collection system; and a production environment to be used by the public to file their forms and to be used by FERC staff to analyze the forms data.

All forms filed using the completed XBRL system shall include a valid company ID (CID) that links the forms to the company registration database tables in the FERCOnline Database.

3.4 Provide Written Process to Apply Maintain Changes to XBRL data

A. The contractor shall provide a written process to apply and maintain changes to the XBRL data collections in accordance with the FERC configuration management policy.

B. The contractor shall provide the capability for the filer to request confidential treatment of data filed through the XBRL system.

C. The contractor shall provide the capability to store public data and non-public data in the XBRL database and use Role-Based access to ensure data is only available as authorized.

2.5 Plan, build and deliver the supporting infrastructure, tools, database design and reporting

The contractor shall develop a plan and deliver the supporting infrastructure, tools and database design for the VFP Forms. The plan shall include but is not limited to, building XBRL databases, storing XBRL data, reporting XBRL information, building and/or using tools to render data from XBRL databases, identifying required ports to be open and implementing an open source or proprietary software to support XBRL data collections.

2.6 Develop Standard Operating Procedures

The contractor shall develop standard operating procedure (SOP) for maintaining the proposed solution. The solution provided by the contractor shall fully replace the current VFP forms. The contractor shall also provide written recommended alternatives for hosting the proposed solution (cloud or on premise). The solution provided shall allow for Role-Based Access to any XBRL tools and backend database access shall follow the concept of least privilege.

Minor taxonomy updates and other standard day-to-day operations completed by FERC end users shall be fully audited and logged. Any updates to the backend database or other system level infrastructure changes shall follow FERC’s Configuration Management Policy (See Attachment 4). The contractor shall provide a reporting capability so that the public can query the XBRL database and download any data from the submitted forms and view human-readable renders of each submission. The download shall not exceed 30 seconds for the download of data for any one filing. Downloads containing multiple years of data and/or multiple companies shall not exceed 30 seconds per year of data or per individual company. For example a download containing two years of data would not exceed one minute (2 years * 30 seconds per year).

Task 3: XBRL Training

3.1 Train business users to develop and maintain XBRL taxonomies

The contractor shall provide hands-on training for up to ten (10) business users in developing, making changes to, and maintaining XBRL taxonomies and validation rules independently from IT Staff and/or external XBRL experts. The training shall also include configuration control and concepts. IT staff shall also participate in XBRL taxonomy development training.

https://ws.sp.ferc.gov/CIO/OCIO/Team%20Documents/XBRL/Atch%204%20Configuration%20Management%20Policy%202018.pdf

The contractor shall provide written recommendations and alternatives to the Commission on the appropriate open source or commercial software solution and train business users and IT staff on the use of the software to support taxonomy development and maintenance. The contractor shall provide written quick reference guides for all training conducted.

3.2 Train IT staff on XBRL database maintenance

The contractor shall provide hands-on training for up to 10 FERC federal IT staff on XBRL database maintenance, to include building XBRL databases, storing XBRL data, and building and/or using tools to render data from XBRL databases. The contractor shall provide a specific list of roles and responsibilities that shall be for IT staff and not for business staff. The contractor shall also train IT staff on how to use open source or proprietary software to support XBRL data collections. The contractor shall provide written material for all training conducted.

3.3 Provide End User Implementation and Reference Guide

The contractor shall provide a written instruction guide that describes the processes to create XBRL submissions for each of the forms to include how to correct and refile data. The guide shall provide information that directs the filer to the correct website for filing as well as instructions regarding how to process acceptance or rejection confirmation and validation reports for each filing.

3.3a – End User Implementation and Reference Guide – draft

This will be the initial completed version of the guide for review by FERC staff

3.3b - End User Implementation and Reference Guide – final

This will be the final version that shall be completed by the contractor that will include comments and edits to the draft by the COR

Task 4: Development, Testing, Pre-Deployment, and Preparation for Transition to Operations

For all project activities the contractor must follow the FERC Systems Development Life Cycle Policy or other methodology as approved on the contract. In addition, the contractor shall follow the Commission’s Configuration Management Policy (Attachment 4)

4.1 Develop and Implement a Testing Plan

The contractor shall provide and implement a test plan and conduct Quality Assurance Testing (QA) and User Acceptance Testing (UAT) for the deployment of the taxonomy in the initial environment. This includes, developing test cases, conducting UAT meetings to prepare testers and interested stakeholders, recording the agenda and the meeting minutes IAW FERC CIO Meeting Management Procedures (Attachment 5). The test plan shall provide testing and test results for the following:

1. Provide evidence in the form of documented test results that task 2.1 through 2.6 above have been completed

2. Business staff can add, delete, or update the taxonomy without IT intervention

3. The Commission can perform tasks in accordance with task 3.2 above

A complete end-to-end submission of all XBRL forms is successful and verified by the COR. All XBRL validations are correct.

4.2 Provide Deployment, Post Deployment and Operations and Maintenance Support Plan

4.2 a The contractor shall provide a plan that describes how they shall deploy, handle post deployment issues for 90 days post deployment and ensure a smooth transition.

4.2 b The contractor shall provide a list to track post deployment issues, triage and fix any development or taxonomy issues, and provide additional training or communications regarding any adjustments.

4.2 c The contractor shall provide a disposition plan that includes a list of all VFP assets to be removed from the Commission. The disposition plan will contain a list of CRQs that must be created and submitted by the contractor. The CRQs will contain the steps to be performed by the IT Support Services to disposition the VFP assets.

https://ws.sp.ferc.gov/FERCollaborate%20Library/Configuration%20Management%20Policy.pdf https://ws.sp.ferc.gov/FERCollaborate%20Library/CIO%20Meeting%20Management%20Standard%20Operating%20Procedure.doc https://ws.sp.ferc.gov/CIO/OCIO/Team%20Documents/XBRL/Atch%205%20CIO%20Meeting%20Management%20Standard%20Operating%20Procedure.doc

4.3 Provide and Execute Communications Plan

The contractor shall provide a Communications Plan that shall set expectations for the FERC Messaging Transition from VFP to XBRL. The contractor shall provide reports, updates, and statuses that involve a project plan, resources, technical details and approach. Communications shall be provided to and approved by the COR.

A communications plan consists of the following steps:

• what we want to accomplish with the communications (our objectives),

• ways in which those objectives can be accomplished (our goals or work),

• to whom our communications shall be addressed (our audiences),

• how we shall accomplish our objectives (timeframe, meetings, etc.), The audiences requiring communication are as follows, including suggested summaries of communications necessary:

• FERC Executives o Project Briefing o Information Overview Session (Town Hall)

• CIO

o Project Plan updates o Technical details o Resources

• FERC Program Office Staff o Special Instructions o Project Plan o SharePoint document repository

• Filers of eForms Data o Physical Media (Posters) o Email & website updates o Classroom and Web Based Training

• The public o Physical Media (Posters) o Email & website updates o Classroom and Web Based Training

Task 5: Deployment to Production

The contractor shall deploy the completed system, transition to an operational state, and identify to the government the VFP assets to be dispositioned per the plan described in Section 4.2. The contractor shall validate that the operational system is functioning in accordance with test plans described in Section 4.1. The production system shall have 3 years of converted data as described in the requirement for the project plan in section 1.6.

Task 6: Operations, Maintenance and Support

6.1 Provide ongoing operational and technical support

The contractor shall provide ongoing operational and technical support in accordance with the plan in Section 4.2.

6.2 Provide ongoing operational support of the XBRL taxonomy

The contractor shall develop an operational plan for the supporting updates to the XBRL taxonomy and any other related hardware, software, or services required to support the XBRL taxonomy and applications, databases, reporting, and tools.

6.3 Provide Customer Support

The contractor shall provide Tier 3 and Tier 4 services for customer support incidents related to XBRL system issues. Support must be available during FERC business hours (7:00 AM-6:00 PM (EST) Monday -Friday) excluding holidays and government closures. The FERC definitions for Tier 3 and Tier 4 are as follows:

Tier 3 – Administrative and engineering support for Infrastructure, Enterprise IT Systems and Business Systems. Tier 3 support provides administration including day-to-day system monitoring, higher-level troubleshooting, and an immediate configuration support. Tier 3 support provides escalated support for Enterprise IT and Business Systems.

Tier 4 – Contractor support as well as internal applications developers, engineers and Subject Matter Experts (SME) for Infrastructure, Enterprise IT Systems and Business Systems. This level of expertise has a higher-level skill and view of the IT infrastructure, Enterprise IT Systems and Business Systems.

Plan for system availability and capacity using existing performance data and anticipated growth/change needs.

The FERC IT Support Services Contractor shall provide tiers 1 and 2 ticket entry, support and incident routing

Task 7: Security Requirements

7.1 Suitability Requirements

The Contractor shall pre-screen all persons proposed for work under this contract for basic suitability. To facilitate this process, the Contractor shall designate a Security Officer (and an alternate in case of primary Security Officer’s absence) with the authority and responsibility for performing personnel security screening to the maximum extent practical. At a minimum, pre-screening shall include, but not be limited to, criminal records checks, verification of current home address, phone number, and prior work experience.

Other duties shall include the following: ensuring that all security forms are filled out correctly and completely and submitted to the COR in a timely manner; ensuring that only cleared employees are authorized access to the project area; ensuring that contract employees are denied access to classified National Security information; and ensuring that contract employees do not remove FERC data or materials from the project area.

The Contractor’s Security Officer shall make every effort to provide incurrence of avoidable costs by the Government for BIs by pre-screening all applicants to ensure that all personnel furnished are reliable and of reputable background and sound character.

Each individual employed or otherwise retained by the Contractor to perform work under this contract shall be fingerprinted at the FERC's Security Office, and shall also submit to the designated Contracting Officer's Representative (COR) one completed Optional Form (OF) 306 (Declaration for Federal Employment, answer Questions 1,3b, 5 through 17a). The Contractor shall be responsible for all costs associated with completing the forms required by the FERC's Security and Safety Division. Completed forms shall be submitted to the COR, without alteration or changes to said forms, at minimum 14 working days before the individual may begin work or be given access to any agency records, data, or information in connection with this contract.

In addition to the forms above, individuals employed or retained by the Contractor to fulfill contract positions or duties for 180 days or more, and any individual designated to fulfill certain sensitive contract positions or duties COR, shall be required to submit to the COR, one SF85 or SF85P (and any additional investigative forms) based on a risk determination by the COR that shall take into account the sensitivity level of the contract position or duties assigned to the individual, the individual’s access, if any, to nonpublic or confidential information, and any other relevant considerations. The individual must submit these additional forms to the COR at least 7 working days before such.

Contractor employees may begin work on any day of the week, as directed by the COR, but will not have access to information technology (e.g., username and password) until processed through the FERC Security and Safety Division. Please note the pre-screening process could take less time but at minimum 14 days.

7.2 Background Investigations

All contractors and subcontractors performing work under this contract shall be subject to the same investigative requirements as those of regular FERC appointees or FERC employees with similar access requirements. Position risk levels must be assessed and approved by the COR utilizing OPM’s Position Risk Designation Tool.

The FERC must conduct and favorably adjudicate, pre-screening background investigations for each Contractor employee to begin working on the contract. If one passes the pre-screening process, the contractor can continue to work during the standard OPM background investigation process. Negative background investigation results however, can affect the continued employment of the contract employee. The extent of the background investigation will vary depending upon the Risk Level associated with each position and whether each position is permanent- or a temporary-term. Temp is defined as contract employees having access to Federally-controlled information systems and/or unescorted access to Federally-controlled facilities or space for six months or fewer. The investigative requirements are as follows which will apply to all contractors on this contract:

• Low Risk/Non-Sensitive Positions - The minimum background investigation required for Low Risk/Non- Sensitive positions is a National Agency Check with Written Inquiries (NACI). The five year reinvestigation required is another NACI. The SF-85, Questionnaire for Non-Sensitive positions, is required.

7.3 Investigation Costs

All costs associated with the required security clearances, including the required OPM investigation shall be assumed by the winning contractor. The FERC will be credited for all such costs via a credit to the first invoice following the completion of any/all investigations.

7.4 Contractor Financial Responsibility

Contractor is responsible for the cost of all new investigations, reinvestigations, and position risk designation changes.

7.5 Non-Disclosure Agreement

The Contractor and all personnel assigned to the contract that require access to the FERC network agree not to divulge to any unauthorized person non-public or confidential information obtained from FERC in performance of their duties under the contract. All documentation, electronic data and information collected or generated by the Contractor in support of this contract shall be considered Government property, and shall be returned to the Government at the end of the performance period. The Contractor will be required to sign a Non-Disclosure/Confidentiality Agreement prior to commencement of work to protect the proprietary/intellectual property of FERC.

7.6 Contractor Personnel Changes

During performance of this contract, the Contractor will keep the COR apprised of changes in personnel to ensure that performance is not delayed by compliance with credentialing process.

7.7 Property Rights

FERC will own the intellectual property rights to any software developed on its behalf to the maximum extent practical.

FAR Part 52.227-14 and 52.227-19

7.8 FERC Security Training Requirements

All Contractor employees and subcontractor employees requiring access to FERC information and FERC information systems shall complete the following before being granted access to FERC networks:

• Sign and acknowledge understanding of and responsibilities for compliance with the FERC Rules of Behavior relating to access to FERC information and information systems;

• Successfully complete FERC Cyber Security Awareness Training (CSAT) and annual refresher training as required;

• Successfully complete FERC General Privacy training and annual refresher training as required; and

• Successfully complete any additional cyber security or privacy training, as required for FERC personnel with equivalent information system access – e.g., any role-based information security training required in accordance with NIST Special Publication 800-16, Information Technology Security Training Requirement.

The Contractor shall provide to the Contracting Officer a copy of the training certificates for each applicable employee within 1 week of contract start date and annually thereafter, as required.

7.9 Contractor Location

Custom software development and outsourced operations shall be located in the United States. FERC information, including FERC-specific custom code will not be allowed to be stored or transferred outside the continental United States.

7.10 Handling of Third Party Requests for Access to Records

In the event that the Contractor receives any subpoena or other voluntary or mandatory request for access to data first produced under this Contract, the Contractor shall immediately notify the COR and the CO, so that the Government may intervene or take any other steps it deems necessary to protect its interests.

7.11 Contractor Information Systems Subject to the Federal Information Security Management Act of 2002 (FISMA)

All agency information systems, see 44 U.S.C. 3505(c), operated by or on behalf of the Government by a Contractor or subcontractor containing Federal data shall be subject to the requirements of the FISMA, including routine testing without advance notice to or approval of the Contractor or its subcontractors. See 44 U.S.C 3544(b).

7.12 Security Controls

Contractors shall be required to ensure compliance and validation with the relevant security control requirements of NIST SP 800-53 Revision 4 or FIPS 200 that are appropriate to the sensitivity and criticality of the data or system.