Attachment_B_-_Technical_Requirements_Checklist.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- CalcBench XRBL Data for EDGAR (BNE) Federal contract opportunity
- Solicitation number
- RFQ-17PR-TDP-0275
About this file
Attachment B - Technical Requirements
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment_C_-_IPP_Waiver.pdf | ||
| Attachment_A_-_Pricing_Format.docx | DOCX document | |
| RFQ-17PR-TDP-0275.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
TECH Chklst
| Attachment B - Technical Requirements Checklist | |||||
| TECHNICAL REQUIREMENTS CHECKLIST | |||||
| 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). For example, only proposals with a "Y" in column C will be evaluated. Instructions for the Offeror: Place a Y (Yes) or N (No) in column C. In column D, include the corresponding name of the Offeror's product(s) which meets the Government's requirement. Blanks in column C will be counted as "No." The Offeror shall provide any additional comments/notes on a separate attachment and the comment/note should be numbered to coincide with the requirement below that is being addressed. Additional information describing the Offeror's Technical capability is limited to twenty (20) pages. Pages submitted above the twenty (20) page limit will not be evaluated. Column E is used to only provide a brief statement on how and by how much the Offeror's product exceeds the government's requirement. Each Offeror MUST schedule a demo of its product either via webcast or at the Government's offices at 717 14th Street, Washington DC. The Contracting Officer will email the Offeror the designated time and date and the demo form which must be completed and returned. The purpose of the demo is to illustrate or highlight product features already mentioned in Column A,B, C of the checklist and in the Offeror's technical proposal which presumably will be comprised of its marketing literature or excerpts from the marketing literature. | OFFEROR | OFFEROR | OFFEROR | EVALUATOR COMMENTS - NOTE WETHER THE VENDOR MEETS,DOES NOT MEET, OR EXCEEDS REQUIREMENTS. If the requirement is not met or if the requirement is exceeded note why this is the case. Reference the page(s) in the technical proposal or the point covered in the demo. REQUESTS FOR CLARIFICATION SHOULD BE NOTED ON A SEPRATE SHEET AND REFERENCE THE ROW NUMBER OF THE REQUIREMENT. | |
| Row Number | REQUIREMENTS | Does the data model or data set provided by the Offeror meet the requirement? (Y/N) | Insert Product Name next to the corresponding requirement | 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 information on "EDGAR XBRL financial statements going back to 2009," an offeror may state "EDGAR XBRL financial statements going back to 2009 plus notes on corrected financial statement data elements" Product ABC" | NOTE---THIS COLUMN WILL NOT BE PROVIDED ON THE RFQ - ONLY ON THE EVALUATION COPY |
Data - DATA SETS
| The Office of Financial Research (OFR) intends to procure a commercial subscription agreement for vendor-hosted standardized XBRL data subscription and analytic services which include online and help desk support PLUS data cleaning and correction. The data set accessed through the service must include the following: | |
| 1 | All public XBRL filings submitted to the SEC via the EDGAR disclosure system since June 30, 2009. |
| 2 | Data sets must be available at the time Offeror responds to this solicitation. |
| 3 | Going forward, the service must add XBRL data and exhibits subsequently filed with the SEC to the repository on a timely basis. |
| 4 | The cost of maintaining a complete, up-to-date set of XBRL filings shall be included in the pricing proposal. |
| 5 | The data in the repository must include scrubbed and normalized data with processes to correct common XBRL errors on filed company financial statements including but not limited to |
| 5A | · Sign switches (about 50% of filings) - for example - reporting the incorrect polarity of a number such as reporting a negative number which should have been positive |
| 5B | · Scale errors (about 8% to 12% of filings) - for example - reporting 5 when the number 5000 should have been reported |
| 5C | · DEI errors (about 3% of filings) - for example - reporting incorrect information for the fiscal period, fiscal year, or document balance sheet date |
| 6 | The vendor shall provide access to additional publicly available interactive data files (e.g.XML, XBRL) from the SEC such as the Forms 3/4/5 and the Mutual Funds Risk/Return Forms (starting in December 2010) |
| 7 | The subscription service shall be accessible via the Internet. It must have an intuitive and user-friendly interface for accessing and analyzing the service's data via any computer connected to the Internet through a standard browser (e.g., Internet Explorer) and an Excel application plug-in. If the web-based interface is used, users must be able to download their analyses from the Internet -based interface into a spreadsheet format |
| 8 | The subscription service shall be accessible via the Internet. It must have an intuitive and user-friendly interface for accessing and analyzing the service's data via any computer connected to the Internet through a standard browser (e.g., Internet Explorer) and an Excel application plug-in. If the web-based interface is used, users must be able to download their analyses from the Internet -based interface into a spreadsheet format |
| 9 | The subscription service shall keep the associated technologies, data, and services up-to-date with relevant technology standards, and must keep the methodology (of searches and data requests), stored searches and analyses, and search and analysis history, secure and up to date. |
| 10 | The subscription service shall allow for full access to a downloadable feed via an application programming interface (API). The API should be able to be integrated into multiple programming platforms and configurable to allow a user to extract information by specific data sets, fields and filters. The API must be able to return populations ranging from single-company specifications to database-wide downloads and in a format that allows users to render and analyze the information in external database platforms. |
| 11 | The subscription service shall provide training, in either live, web-based live, or video-based format (or a combination of the three formats) to users, as well as timely phone or email technical support |
| 12 | Data sets updated on a monthly basis for all live funds covered |
| 13 | The updates shall be available to Treasury no later than the date in which the data is also available within the industry. |
| Subscription Service System Performance. | |
| The subscription service shall allow users to do the following: | |
| 1. Perform financial data searches for a supplied search term such as company name. | |
| 2. Perform metadata or financial searches for a supplied company ticker, CUSIP or CIK to build company profiles and financial statements for analysis. | |
| 3. Perform targeted searches that match user defined tags and location terms. | |
| 4. Retrieve individual company’s descriptive information, financials and/or ratios. | |
| 5. Query for companies based on specific filters or screening criteria. | |
| 6. Retrieve insider rosters and trading activity. | |
| 7. Access institutional ownership data for investor targeting. | |
| 8. Access a downloadable feed of the entire population of standardized XBRL data available from the Offeror via an application programming interface (API). | |
| Documentation and Assistance | |
| 14 | Information detailing the methodology and any data dictionaries shall be provided concurrent with award. |
| 15 | The data dictionary shall be provided and updated as additional features are added or deleted and provided to licensed government users when made available to commercial clients |
| 16 | The contractor shall provide the same level of help desk assistance provided its commercial customers such as user training, and analytical and technical support |
| Data Delivery | |
| 17 | Data may be delivered through a secure FTP download in a government accessible format such as .xml or excel or accessible through a Web Portal. |
| 18 | The data delivery method shall provide ability to conduct analysis and produce reports based on queries designed by the user utilizing data fields provided by the Contractor. |
| 19 | The data delivery method shall permit download of the data feed |
| 20 | The data delivery method shall have view and download capabilities |
| 21 | The data delivery method shall allow for standardized reports |
| 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 .