Business for Profit

Appendix F

Data Request: Retailer Detailed Transaction Data Files

memorandum

Date	Month day, 2019
To	Recipient
From	Robin Koralek, Project Director Chris Logan, Principal Investigator Dr. Eric Williams, Social Science Analyst/Project Officer (USDA/FNS)
Subject	SNAP Online Pilot Evaluation: Retailer Data Request

Welcome to the SNAP Online Pilot Evaluation. As you know, the United States Department of Agriculture (USDA) Food and Nutrition Service (FNS) is seeking to learn how the Electronic Benefits Transfer Online Purchasing Pilot is implemented across retailers and States. The evaluation will inform FNS’ decisions about whether and how to make SNAP online purchases more widely available, how to ensure the accessibility and quality of online purchases, and how to ensure that protections against abuse remain strong or grow stronger. This document provides information about the data we will collect from you.

Abt Associates, and its partners Altarum and Novo Dia Group, are conducting this evaluation the Online Purchasing Pilot, which is authorized under the Agricultural Act of 2014¹ (The Farm Bill). FNS is sponsoring this data collection.

Overview of the Evaluation

This evaluation will help FNS learn how the pilot operates, the implementation challenges and lessons learned, the characteristics of SNAP online customers, the risks and benefits of online purchasing for the integrity of SNAP, and the requirements for expansion. The evaluation team will examine:

1. Pilot implementation, including SNAP online transaction approaches; the process, challenges, and lessons of implementation; the characteristics of SNAP households that shop online; and the level of effort for stakeholders (e.g., retailers, states, EBT processors).

2. Pilot integrity, including delivery patterns and their relationship to customer addresses and retailer locations; customer profiles and their relationship to EBT cards and SNAP households; customer shopping patterns; and problems such as refunds and cart abandonment.

After pilot operations begin, we will be in touch about setting up conversations about the pilot design, testing, and implementation. For now, we will focus on data requests to ensure you are able to provide the data elements we need for the evaluation.

Data Requests

We will request the following types of data for the evaluation:

1. Optional transaction data including information about individual transactions including order number, store, amount charged, payment method, number of items, fulfillment method, delivery address, quantity ordered and fulfilled, and timing of fulfillment. These data will include all purchases associated with orders made by SNAP customers and any refunds associated with these orders.

2. Summary data including information about orders and payment methods, customers and customer profiles, deliveries and shipping, fees, refunds, and customer service calls.

3. Retailer store data including retailer’s store numbers, FNS retailer numbers, store names and addresses. Retailer store lists are only applicable to retailers with multiple stores in the pilot.

Attached are three documents with the data elements and specifications we will request for the transaction data and the summary data. Please be aware that these are not data templates or layouts; they are provided as a basis of information and discussion.

Attachment 1 – SNAP online transaction data elements.xlsx

Attachment 2 – SNAP online summary data elements.docx

Attachment 3 – SNAP online retailer store data elements.docx

Data Use Agreement

We will work with you to develop a data use agreement (DUA). The DUA will authorize recipients (i.e., the Abt team) to use the data you provide for a designated purpose (i.e., this evaluation). Terms of the DUA will include: whom the data may be released to, how the data is to be handled and protected, data destruction or return requirements when the work is done or period of performance is over, procedures in the event of unauthorized disclosure, name of custodian or security officer, legal terms (such as termination, audit rights, liability, indemnification, liquidated damages, civil and criminal penalties), and flow down requirements for business partners. We understand you may already have a standard DUA which we can work with.

Data Security

Protecting the data we receive from you is our highest priority. Abt Associates Inc. Abt complies with the Privacy Act of 1974, Health Insurance Portability and Accountability Act of 1996 (HIPAA), and the E-Government Act of 2002, including Title III: Federal Information Security Management Act (FISMA), which covers site security, security control documentation, access control, change management, incident response, and risk management.

Abt has a dedicated Analytic Computing Environment (ACE3) for the purpose of only storing and analyzing sensitive information such as Personally Identifiable Information (PII) and Protected Health Information (PHI). This environment allows our team to access and work with data using tools such as SAS and STATA without the data leaving the environment. ACE3 is FISMA Moderate (SP800-53 rev.4) and FIPS 140-2 compliant and built with a combination of FedRAMP and Abt-developed systems. PII will be stored and accessed only in this secure environment. Approval must be granted for access to this environment and its project folders. Authentication to ACE3 is via Active Directory and requires the use of DUO multi-factor authentication. Users connect to the system via remote desktop sessions (RDS) directly to the environment.

Transferring Data to Abt

Abt uses a secure data transfer application, Huddle, for the secure, encrypted transmission of sensitive information such as Personally Identifiable Information (PII) and Protected Health Information (PHI), to and from its external clients. Huddle is a FedRAMP collaboration cloud service tool that stores data in the cloud and meets U.S. federal security requirements for encryption. The data is encrypted in-transit through the use of TLS, and at rest with 256-bit AES, and is FIPS 140-2 compliant. Only authorized study team members have access to the project folders in Huddle, and access is restricted and controlled via folder permissions in Huddle. Details about accessing this site will be sent separately.

Evaluation Contacts

If you have any questions, please contact:

Robin Koralek (Project Director) at [email protected] or (301) 347-5613

Chris Logan (Principal Investigator) at [email protected] or (617) 349-2821

Eric Williams (FNS Contracting Officer’s Representative) at [email protected] or (703) 305-2640

Next Steps

After you review this letter we would like to meet to discuss the data requests and the DUA, and to answer any questions you may have. In particular, we want to know if there are any data elements you will not be able to provide or have concerns about.

We expect it will take you 12 hours (one hour per month) to prepare and submit the detailed transaction files.

Public reporting burden for this collection of information is estimated to take one hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to: U.S. Department of Agriculture, Food and Nutrition Services, Office of Policy Support, 3101 Park Center Drive, Room 1014, Alexandria, VA 22302, ATTN: PRA (0584-xxxx*). Do not return the completed form to this address.

SNAP Online Purchasing Evaluation: Optional Transaction Data Request

Data Element	Description	Notes
Order_no	Unique order number	file includes examples with multiple records with same order #
Store_no	Internal store number OR FNS store number	Applies only to retail stores. Number should be unique to the location.
Store_Address	Physical address of store	Separate fields with 2 lines for street address, city, state, zip code.
Approval_Code	Transaction approval code from First Data	To come from First Data. 6 digit code, will repeat so Abt will use date and card # for matching.
Card_no	Last 4 digits of card number
Card_type	Type of card (EBT, credit, debit, other)	Sample values: AMEX, DEBITCARD, DISCOVER, EBTSNAP, EBTCASH, MASTERCARD, VISA, GIFT.
Tender_type	Type of tender - payment or refund
TOT_AMT_CHRGED	Total amount charged to specified card type	For each order, each payment/refund will be a separate record
Payment_Create_Time	Time and date of payment.	Date and time of authorization. Format to be discussed.
Order_Placed_Time	Time order was placed	Date and time based on store location. Format to be discussed.
Item_Pick_Complete_time	Time order picking was completed	Date and time based on store location. Format to be discussed.
Time_bw_Order_Placed_and_Pick_in_mins	Time between order placed and order pick completed.	Time in hours, minutes and seconds.
Order_Dispensed_Time	Time order was dispensed (picked up or delivered)	Date and time based on store location. Format to be discussed.
Time_bw_Pick_and_deliver_time_in_mins	Time between order pick completion and order dispensed.	Time in hours, minutes and seconds.
Delivery_Type	Pickup or delivery	Also differentiate express vs regular or other categories with different rules or fees
REFUND_REASON	Reason for refund	Not applicable for purchases
REPEAT_CUSTOMER	1 if customer has made a previous online grocery purchase from retailer	Lookback period to be discussed
NEW_CUSTOMER	1 if customer has not made a previous online grocery purchase from retailer	Lookback period to be discussed
PREV_ORDER_CNT	Number of previous online grocery orders made by customer to retailer	Lookback period to be discussed
ONTIME_ITEM_PICK_IND	Indicator that order was available for pickup on time	Optional
ONTIME_HOME_DELIVERY_IND	Indicator that order was delivered on time	Optional
DELIVERY_METHOD	Method of delivery	Home, locker, store etc. - categories will depend on retailer policies.
CALLS_RSN	Reason(s) for call(s) to customer service about purchase	Option. Can include multiple reasons separated by commas
Quantity_Ordered	Number of units ordered
Quantity_Picked	Number of units picked
Quantity_Substituted	Number of units substituted for items not available
Quantity_Not_Picked	Number of units ordered but not picked (no substitute available)
Shipping Address	Shipping or delivery address for order	Separate fields with 2 lines for street address, city, state, zip code.

1Agricultural Act of 2014, Conference Report to Accompany H.R. 2642. P. 144-147.