Amendment_0003.pdf

(x)

TFSAOFR14CI0007

x x copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram 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 telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

Parkersburg WV 26101 200 Third Street

FSA-PARKERSBURG

Avery 5F Administration Branch Division of Procurement Bureau of the Fiscal Service

Parkersburg WV 26101 Attn: B. Burnworth

FSA-BBURNWORTH

200 Third Street Avery 5F Division of Procurement Bureau of the Fiscal Service

02/19/20140003

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

01/30/2014

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 date, 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.)

The purpose of this amendment 0003 is to extend the due date for proposals, answer vendor provided questions, replace the specifications on page 15 of the original document, replace the contract documents, exhibits, and attachments list on page 17 of the original document, replace the technical acceptability under "Instructions to Offerors" on page 21 of the original document, replace Attachment A with Attachment A1, and add Attachment A2.

Proposals are now due by 1400 EST (2 pm) on March 4, 2014.

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)

GINA HANNA

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

NSN 7540-01-152-8070

Previous edition unusable

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

TFSAOFR14CI0005

Responses to Trade and Quote Questions

Question 1: The Contract Minimum and Maximum section as well as Section 1.2 specifies a licensing model where a given number of users are licensed over a given time period. Is there an inherent requirement by the Treasury to limit the number of users? Or would the Treasury consider an alternate licensing model that does not hinge on user limits?

Answer 1: No - If an enterprise license is available covering an unlimited number of users, the Offeror should also provide such pricing within its price proposal. If available, Treasury would also like to know the Offeror’s seat pricing structure.

Question 2: The Background section (page 15) refers to a need to perform applied research on the data; is the bidder required to provide these research/analytics tools in addition to the data?

2A) If yes, please describe the functionality required for analytics.

2B) If no, please describe what research or analytic tool(s) may be leveraged by the Treasury.

(This detail will provide additional guidance on our understanding of your needs on both the data delivery and the data format front.)

2C) In either scenario, please provide an example(s) of the type of query that the Treasury may want to perform. (This detail will provide additional guidance on our understanding of your needs on both the data delivery and the data format front.)

Answer 2: B, No. We just need a platform or facility through which the data is cleaned and provided. Once

Treasury has access to this data, it has the analytical tools necessary to conduct the analyses it intends to examine. C, Treasury would like to look at panel data sets and run basic descriptive statistics on the individual securities as well as in an industry or portfolio level basis, and be able to look at these results throughout history. Beyond that, Treasury intends to run model-based statistics such as regressions in Excel or other software packages in order to support our ongoing research.

Question 3: In several instances the specifications seem to contain conflicting guidance on data needs.

Please confirm, is the Treasury interested in purely historical data (commonly referred to as “TAQ” and available on a T+1 basis), historical intra‐day data (available on a T+15min basis), and/or real‐time, low‐latency data (streaming trades and quotes essentially as they happen)?

3A) If historical *and* real‐time data are required, would the Treasury consider a phased deployment or are both data sets required Day 1?

Answer 3: Treasury requires historical data on a T+1 basis.

Question 4: In Section 1.1., the specifications state a requirement for CBOE data. Please confirm, is the

Treasury interested in only equities data or is there a need for options data as well?

Answer 4: Treasury requires equity data; however, if a vendor provides options market data as part of its commercial product Treasury will consider this in its best value determination. Any options market data provided by the vendor can be discussed in the vendor’s 20 page limit technical proposal.

Question 5: In Section 1.1, the specifications indicate requirements for the ‘data found on the consolidated tape’ (which consists of top of book data) as well as ‘full book data.’ Please confirm whether the Treasury requires both top of book data as well as full depth of book, or one or the other?

Answer 5: Treasury requires top of the book data.

Question 6: In Section 1.1, please confirm whether ‘intraday’ translates to an intraday access requirement, and if so, and what time interval (e.g. 15 min delayed); or whether the Treasury requires a true real‐time, low‐latency delivery of market data.

Answer 6: Treasury requires an end of day data upload containing all the Trade and Quote data from that days activities. For example: the day’s activities covers 8AM to 6PM local time for the exchange location.

Question 7: In Section 1.1, what does the Treasury qualify as a ‘major exchange’?

Answer 7: Treasury qualifies the following as major exchanges:

• NYSE MKT LLC (formerly NYSE AMEX and the American Stock Exchange)

• BATS Exchange, Inc.

• BATS Y-Exchange, Inc.

• NASDAQ OMX BX, Inc. (formerly the Boston Stock Exchange)

• Chicago Stock Exchange, Inc.

• EDGA Exchange, Inc.

• EDGX Exchange, Inc.

• The Nasdaq Stock Market LLC

• National Stock Exchange, Inc.

• New York Stock Exchange LLC

• NYSE Arca, Inc.

• NASDAQ OMX PHLX, Inc. (formerly Philadelphia Stock Exchange)

Question 8: In Section 1.1, please clarify the requirement for ‘TAQ real time tick data for a two week period’.

Answer 8: Treasury amended its requirements. See updated specifications and updated Attachment A1, and

Attachment A2 which was added to state the required data fields and the years covered.

Question 9: In Sections 1.1, 3, and 3.1, the specifications list several formats for the data – comma delimited, text, xls, etc. Is the data required in *all* formats or simply one of the acceptable formats listed?

Answer 9: Treasury requires the data to be available in at least one format.

Question 10: In Section 1.1, must the mapping requirements for all symbols used by a corporate entity be applied/inherent in our provided data set or exist as a stand‐alone file that can be applied against the raw data?

Answer 10: At the minimum, Treasury requires the data be provided in a stand-alone file.

Question 11: Referring to Section 1.1, is the Treasury aware the requirements for all historical market data back to 1993 surpass what the exchanges themselves have available, in some instances?

Answer 11: Treasury amended its requirements. See updated specifications and updated Attachment A1, and Attachment A2 which was added to state the required data fields and the years covered.

Question 12: Please explain the requirement for individual market data feeds in addition to data from the

Consolidated Tape.

12A) If there is a true need for real‐time market data feeds from direct venues, the list provided contains feeds that could be considered ‘parent’ feeds and others that could be considered ‘child’ feeds. Some of the parent feeds inherently contain all of the data that a child feed provides. In those instances, would it be acceptable to provide only the parent feed or is there a true need for each individual feed, regardless of data duplication?

Answer 12: Treasury amended its requirements. See updated specifications and updated Attachment A1, and Attachment A2 which was added to state the fields.

Question 13: Clause 52.212‐2 (page 22) states the Treasury may accept an offer by written reply; how then should a potential bidder incorporate necessarily legal Ts&Cs such as standard master agreements?

Answer 13: Offerors shall submit with their proposal any agreements that the government is required to sign, any exceptions taken to the Use of Information and/or any other recommended changes to government terms and conditions. The government will review the offerors requested changes and supplemental agreements all of which will be negotiated with the offeror as allowable by federal regulations.

Question 14: Contractor licenses the information to be provided under the bid from a third party supplier. Both Contractor and the Government will be subject to the terms of the license agreement between Contractor and the third party supplier, some of which conflict with the Terms, Conditions and Clauses. It is Contractor’s understanding that the procurement of this information from all bidders would be subject to the same license agreement terms. Is the Treasury amendable to modifications to the Terms, Conditions and Clauses for such license agreement terms, as well as execution of additional documentation with the third party supplier as required?

Answer 14: See answer to #13 above. Please indicate which agreements (if any) belong to the offeror and which belong to a third party.

Question 15: Is the Government amendable to rates charge increases imposed by the third party supplier on recipients of the information?

Answer 15: Contract prices proposed at award are fixed for the duration of the contract. You may increase the prices for the option years only if identified in your proposal which will be outlined in the signed award.

DEPARTMENT OF THE TREASURY

OFFICE OF FINANCIAL RESEARCH

SPECIFICATIONS

TRADE AND QUOTE DATA

Background

On July 21, 2010, President Obama signed the Dodd-Frank Wall Street Reform and Consumer Protection Act (the "Dodd-Frank Act"), which created the Financial Stability Oversight Council (FSOC or “the Council”) and the Office of Financial Research (OFR).

The FSOC is charged with three primary purposes: to identify risks to the financial stability of the United States, to promote market discipline, and to respond to emerging threats to the stability of the U.S. financial system. The FSOC brings together the expertise of federal financial regulators, state regulators, and an insurance expert appointed by the President.

The mission of the OFR is to support the Council in promoting financial stability by: collecting data on behalf of the Council; providing such data to the Council and member agencies; standardizing the types and formats of data reported and collected; performing applied research and essential long-term research; developing tools for risk measurement and monitoring; performing other related services; making the results of the activities of the OFR available to financial regulatory agencies; and assisting such member agencies in determining the types of formats of data authorized by Dodd-Frank Act to be collected by such member agencies.

Specification Requirements

1. Data Coverage (Market and Historical):

1.1 Sets

OFR requires the trade and quote data (TAQ) found on the Consolidated Tape and its Over-The-Counter counterpart corresponding to the OTC/UTP data feed, Tape C which is the single consolidated source of data for NASDAQ listed securities. The Consolidated Tape is an electronic program that provides continuous, real-time data on trading volume and price for exchange-traded securities. Through the consolidated tape, numerous major exchanges - including the NASDAQ, and the New York Stock Exchange - report their trades and quotes.

Securities often trade on more than one exchange and the consolidated tape reports a security's trading activity for all of these exchanges, not just its primary exchange.

• The Trade and Quote files must provide data comprising trades, quotes, and reference data and symbology for CTA/UTP real-time market data, and top of the book data for US major exchanges. The following are the US major exchanges where coverage is required:

• NYSE MKT LLC (formerly NYSE AMEX and the American Stock Exchange)

• BATS Exchange, Inc.

• BATS Y-Exchange, Inc.

• NASDAQ OMX BX, Inc. (formerly the Boston Stock Exchange)

• Chicago Stock Exchange, Inc.

• EDGA Exchange, Inc.

• EDGX Exchange, Inc.

• The Nasdaq Stock Market LLC

• National Stock Exchange, Inc.

• New York Stock Exchange LLC

• NYSE Arca, Inc.

• NASDAQ OMX PHLX, Inc. (formerly Philadelphia Stock Exchange)

• The Data Sets shall contain trade and quote data covering the data fields as referenced in Attachment A2 and cover the following spaces:

o Intraday data containing price and volume of trades down to the level of individual trades.

o Where data is available back to January 1, 2004 through current data received during the performance period, Treasury requires for it to be time stamped to the millisecond.

o Where data is available prior to January 1, 2004, Treasury requires, at a minimum, for it to be time stamped to the second.

o Coverage for the United States equities from major exchanges.

o Full historical top of the book, best bid and offer, and last trade data.

o Historical data on a T+1 basis.

o End of day data upload containing all the Trade and Quote data from the major exchanges from that day’s activities. The day’s activities cover 8:00 AM to 6:00 PM local time for the exchange location.

• The data shall contain all equity symbols and shall contain mapped data linking together the data for all symbols used by a corporate entity throughout its history.

• The data shall be presented in a format that covers the entire list of data field descriptions identified in Attachment A2 – “Data Field Descriptions Checklist.”

1.2 Updates

• Following a day’s activities, new data shall be available to Treasury, at a minimum, within a 24 hour period.

• As new data becomes available outside of the day’s activities, such data shall be made available to Treasury at the time it is also available to the Contractor’s commercial customers.

• Changes to the data elements and addition of new data shall be identified in each data update as an email alert to the licensed users.

1.3 History

• The history of the data shall commence as stated below:

o The data within the following exchanges shall commence, at a minimum, back to the year 1993:

NYSE MKT LLC (formerly NYSE AMEX and the American Stock Exchange) The Nasdaq Stock Market LLC New York Stock Exchange LLC o The data within the following exchanges shall commence back to its year of inception: (Note: the inception date for the exchanges below varies.)

BATS Exchange, Inc.

BATS Y-Exchange, Inc.

NASDAQ OMX BX, Inc. (formerly the Boston Stock Exchange) Chicago Stock Exchange, Inc.

EDGA Exchange, Inc.

EDGX Exchange, Inc.

National Stock Exchange, Inc.

NYSE Arca, Inc.

NASDAQ OMX PHLX, Inc. (formerly Philadelphia Stock Exchange)

• The data shall extend to current coverage throughout the performance period in accordance with the update requirements stated above.

2. Documentation

• Information detailing the methodology and any data dictionaries for the TAQ feeds and historical data shall be provided by the vendor concurrent with award.

• The contractor shall provide at least the same level of documentation, training, and technical support as provided its commercial customers.

3. Data Delivery

• The contractor shall provide the data in its original form or according to file formats commonly used in industry and accessible by the Department of the Treasury such as compressed ASCII, comma delimited, text files, excel, and XML.

• The TAQ data delivered via FTP shall be updated at least within a 24 hour period covering the data fields included in Attachment A2 and remain current throughout the performance period of the contract.

3.1 Secure File Transfer Protocol (Secure FTP)

• The government requires the data in a format that will allow its users to persist the data. The data shall be delivered via a secure FTP download or comparable protocol.

CONTRACT DOCUMENTS, EXHIBITS, AND ATTACHMENTS

Technical Acceptability

The Contractor shall complete the Technical Acceptability Checklist, Attachment A1 (columns D, E and F), strictly following the instructions provided in the checklist. The Contractor shall also complete the Data Field Descriptions Checklist, Attachment A2, strictly following the instructions provided in the checklist.

DOCUMENT/EXHIBIT/ATTACHMENT TITLE

Attachment A1 – Technical Acceptability Checklist (MUST BE COMPLETED BY OFFEROR OR WILL NOT BE

CONSIDERED)

Attachment A2 – Data Field Descriptions Checklist (MUST BE COMPLETED BY OFFEROR OR WILL NOT BE

CONSIDERED)

Attachment B – Past Performance Questionnaire (PPQ)

Attachment C – Pricing Format

Attachment D - IPP Waiver Form