Attachment_A1_-_TAQ_Technical_Req_Checklist.xlsx
XLSX spreadsheet 16 KB Posted
- Solicitation number
- TFSAOFR14CI0007
About this file
Attachment A1
View the file
Other files
| File | Type | Posted |
|---|---|---|
| SF-30.pdf | ||
| Attachment_A1_-_TAQ_Technical_Req_Checklist.xlsx | XLSX spreadsheet | |
| Amendment_000004.pdf | ||
| Attachment_A2_-_TAQ_Data_Field_Requirements.xlsx | XLSX spreadsheet | |
| Amendment_0003.pdf | ||
| SF30.pdf | ||
| SF30.pdf | ||
| Attachment_B_-Past_Performance_Questionnaire.docx | DOCX document | |
| Attachment_A_-_Checklist.xlsx | XLSX spreadsheet | |
| Attachment_C_-_Pricing_Format.docx | DOCX document | |
| TFSAOFR14CI0007.pdf | ||
| Attachment_D_-_IPP_Waiver_attachment_NOV_2013.pdf |
Show all 12
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TA Chklst
| Column A | Column B | Column C | Column D | Column E | Column F |
| ATTACHMENT A1 - TECHNICAL REQUIREMENTS CHECKLIST | |||||
| OFFEROR | OFFEROR | OFFEROR | |||
| Row Number | INSTRUCTIONS: The Government is seeking an existing commercial product and not the development of a new product. NOTE: IF ANY MANDATORY REQUIREMENT IS NOT MET, THE OFFER WILL BE CONSIDERED TECHNICALLY UNACCEPTABLE AND THE OFFEROR'S PROPOSAL WILL NOT BE EVALUATED FURTHER. OPTIONAL REQUIREMENTS are denoted by "OPTIONAL" in column B. Only proposals with a "Y" in column D will be evaluated. Place a Y (Yes) or N (No) in column D. Blanks in column D will be counted as "No." In column E, include the corresponding name of the Offeror's product(s) which meets the Government's mandatory and optional requirements. In column F, please provide a brief description of how and by how much the Offeror's product exceeds the requirements listed in column C. In addition, as a separate attachment, the Offeror has twenty (20) pages to provide any additional comments/notes. Offerors shall elaborate on methodology, data coverage, any additional data offered not listed in the requirements below, data delivery modes, and data sources. This includes information on where the data is extracted, how the data is collected, where the data originates, and the frequency with which the newly collected data is updated. Offerors may also provide the Government with any insight as to why the elements that exceed the requirements might be found beneficial to the Government. The comments/notes shall be mapped to the row number of the requirement below that is being addressed. Pages submitted above the twenty (20) page limit will not be evaluated. | Does the data provided by the Offeror meet the requirement? (Y/N) | Insert Product Name next to the corresponding requirement [add as many columns as applicable to cover all the products you provide that meet the requirements] | For requirements where the Offeror 's product exceeds the Government's requirement, the Offeror must state how and by how much, and include its product name(s). For example: if the Government's requirement is for the vendor to provide historical trade and quote information back to 1993," an offeror may state "33,000 equities with information back to 1990. Product ABC." | |
| Requirements | |||||
| Data Coverage (Market and Historical) | |||||
| 1 | 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. | ||||
| OPTIONAL | Does the Offeror provide Options Market data? If so, please describe in Technical Proposal. | ||||
| The following are the US major exchanges where coverage is required: | |||||
| 2 | · NYSE MKT LLC (formerly NYSE AMEX and the American Stock Exchange) | ||||
| 3 | · BATS Exchange, Inc. | ||||
| 4 | · BATS Y-Exchange, Inc. | ||||
| 5 | · NASDAQ OMX BX, Inc. (formerly the Boston Stock Exchange) | ||||
| 6 | · Chicago Stock Exchange, Inc. | ||||
| 7 | · EDGA Exchange, Inc. | ||||
| 8 | · EDGX Exchange, Inc. | ||||
| 9 | · The Nasdaq Stock Market LLC | ||||
| 10 | · National Stock Exchange, Inc. | ||||
| 11 | · New York Stock Exchange LLC | ||||
| 12 | · NYSE Arca, Inc. | ||||
| 13 | · NASDAQ OMX PHLX, Inc. (formerly Philadelphia Stock Exchange) | ||||
| The Data Sets shall contain trade and quote data covering the following spaces: | |||||
| 14 | Intraday data containing price and volume of trades down to the level of individual trades. | ||||
| 15 | 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. | ||||
| 16 | Where data is available prior to January 1, 2004, Treasury requires, at a minimum, for it to be time stamped to the second. | ||||
| 17 | Coverage for the United States equities from major exchanges. | ||||
| 18 | Full historical top of the book, best bid and offer, and last trade data. | ||||
| 19 | Historical data on a T+1 basis. | ||||
| 20 | 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. | ||||
| 21 | 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. | ||||
| 22 | The data shall be presented in a format that covers the entire list of data field descriptions identified in Attachment A2. (NOTE: Attachment A2 must also be completed and returned with Offeror's Technical Proposal.) | ||||
| UPDATES | |||||
| 23 | Following a day’s activities, new data shall be available to Treasury, at a minimum, within a 24 hour period. | ||||
| 24 | 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. | ||||
| 25 | 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. | ||||
| HISTORY | |||||
| The history of the data shall commence as stated below: | |||||
| 26 | o The data within the following exchanges shall commence, at a minimum, back to the year 1993: | ||||
| 27 | NYSE MKT LLC (formerly NYSE AMEX and the American Stock Exchange) | ||||
| 28 | The Nasdaq Stock Market LLC | ||||
| 29 | New York Stock Exchange LLC | ||||
| 30 | o The data within the following exchanges shall commence back to its year of inception: (NOTE: Since the inception date for the exchanges below varies, please note the year in which the Offeror's data commences for each exchange below in column F next to the corresponding row.) | ||||
| 31 | BATS Exchange, Inc. | ||||
| 32 | BATS Y-Exchange, Inc. | ||||
| 33 | NASDAQ OMX BX, Inc. (formerly the Boston Stock Exchange) | ||||
| 34 | Chicago Stock Exchange, Inc. | ||||
| 35 | EDGA Exchange, Inc. | ||||
| 36 | EDGX Exchange, Inc. | ||||
| 37 | National Stock Exchange, Inc. | ||||
| 38 | NYSE Arca, Inc. | ||||
| 39 | NASDAQ OMX PHLX, Inc. (formerly Philadelphia Stock Exchange) | ||||
| 40 | The data shall extend to current coverage throughout the performance period in accordance with the update requirements stated above. | ||||
| DOCUMENTATION | |||||
| 41 | Information detailing the methodology and any data dictionaries for the TAQ feeds and historical data shall be provided by the vendor concurrent with award. | ||||
| 42 | The contractor shall provide at least the same level of documentation, training, and technical support as provided its commercial customers. | ||||
| DATA DELIVERY | |||||
| 43 | 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. | ||||
| 44 | 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. | ||||
| Secure File Transfer Protocol (Secure FTP) | |||||
| 45 | 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. |
Note that the Government reserves the right to reject any and all Offers/Proposals if the mode of data access, the security, subscription or license agreement terms, or the utility of file formats is not acceptable to the Government.
Technical Acceptability Checklist
Sheet3
File details come from the government source that posted it. Updated .