Attach_C_-__Awardee_Checklist_-final.docx

ATTACHMENT C: The below checklist to be completed and submitted with Factor 2 – Technical Capability, however, please note that this checklist will not be used for evaluation purposes. This document will be used to determine classification of data provided and for purposes of determining how data would be onboarded once awardee(s) has/have been selected:

Vendor: [INSERT VENDOR NAME]

Product: [INSERT PRODUCT NAME]

(If more than one product is involved, please respond individually by product to the items listed above. If an item above is “Not Applicable,” please indicate accordingly in your response.)

In order to prepare for any IT-related logistics related to the potential purchase of this data, OFR request the Offeror address the following:

Does the data you provide contain any Personal Identifiable Information (PII)? This includes information that can be used to distinguish or trace an individual’s identity, either alone or when combined with other personal or identifying information that is linked or linkable to a specific individual. Below are examples of PII. Note that this is not an exhaustive list.

· Information that directly identifies or links to an individual, such as:

· Name

· Contact information (email address, mailing address, phone number)

· Bank or credit card account number

· Social Security number

· Vehicle identification number

· Information that is linkable to an individual, or when combined with other data elements may directly identify an individual, such as:

· Date of birth

· MAC, IP addresses

· Gender, race, or ethnicity

· ZIP code

Please provide a Yes, No, or Not Sure response. If the response is “Yes” please include the fields you believe cover PII. If the response is “Not Sure” please include fields that you are unsure as to whether the information contains PII.

Data size for the initial load of historical data

Method in which the historical data will be provided (note: if provided via external media, the government prefers to maintain ownership of the media)

Data size for the on-going updates

Frequency of how often on-going data is updated

Method in which the on-going data updates will be automated/provided/secured, including instructions for accessing the data

· examples of the government’s preference include:

· Direct point-to-point transfers with IBM Sterling Connect Direct (Preferred);

· Secure File Transfer Protocol (SFTP) service;

· Web Service API (REST, SOAP, XML-RPC) over SSL; or

· Direct HTTPS download (no CAPTCHA) via consistent URL

Point of contact (POC) to resolve technical issues with initial load and updates

Level and availability of Training/Help Desk support provided

Whether some form of a data dictionary or data description document is provided that includes file/data structures, field names, definitions, calculation formula, inter-field relationship and other information pertinent to understanding the data provided

Whether data are provided in a pipe-delimited (or other form of text delimited if there are pipes in the data) format [a pipe-delimited format is OFRs preferred method]

Whether feeds contain an MD5 or SHA checksum for each source file so data received can be verified [this is OFR’s preferred means; however, if this cannot be provided than address what documentation is available that includes the number of rows per file so OFR can verify the data is transmitted accurately]

Any limitations the Offeror may have with keeping its data available for download indefinitely

Whether the data comes with a software client that OFR is expected to install within its technical environment and whether the software client is necessary in order for OFR to utilize the data. If a software client is involved, please provide any pertinent details.