SNAP DRAFT PWS 11_15_2022 National Earned Income Verification Support Services.pdf

US Department of Agriculture (USDA)

Performance Work Statement:

National Earned Income Verification Support Services for the

Supplemental Nutrition Assistance Program

Contents Project Title General Information

1.0 Background and Purpose

2.0 Definitions

Contractor Requirements

3.0 Technical Requirements

4.0 Deliverables / Schedule

5.0 Government Furnished

6.0 Travel

7.0 Contractor’s Key Personnel

8.0 Security Requirements

9.0 Data Rights

10.0 Section 508 - Electronic and Information Technology Standards

11.0 Performance Requirement Measures

Project Title The National Earned Income Verification Support Service for the Supplemental Nutrition Assistance Program

General Information

1.0 Background and Purpose

1.1 Program and Policy Background:

The Supplemental Nutrition Assistance Program (SNAP, formerly the Food Stamp Program) is the Nation's largest domestic food and nutrition assistance program for low-income Americans. Households that apply for and are found eligible to participate in SNAP receive a benefit amount via an Electronic Benefits Transfer card that can be used to purchase food in authorized retail food stores. In 2021, SNAP helped an average of more than 41 million low-income people in the United States afford a nutritionally adequate diet each month. The Food and Nutrition Act of 2008 (the Act) is the Federal law that governs SNAP. As required by section 11(a) of the Act, participating State SNAP agencies (which include all 50 States, the District of Columbia, Guam, and the U.S. Virgin Islands) are responsible for directly administering the program while the U.S. Department of Agriculture Food and Nutrition Service (USDA-FNS) conducts oversight, provides technical assistance, and administers federal funding. USDA-FNS strives to apply data-driven strategies to improve program operations, access, and integrity on behalf of the American public.

Section 11(e)(2)(B) of the Act requires that States develop an application form and process for households to apply to participate in the program, and in doing so to declare their income and other household circumstances that are required by the Act for purposes of determining eligibility and benefit amounts. In turn, section 11(e)(3) of the Act requires States to obtain verification, with cooperation from the household, of the household’s stated income and certain other circumstances prior to approving an eligible household for benefits. Though not explicitly required by the Act, SNAP rules at 7 CFR 273.2(e) also require States to interview a responsible member of the household to review the information declared by the household on the application form and to explore and resolve with the household unclear or incomplete information. The Act requires States to consider an application to be filed if the household has submitted it with a name, address, and signature, even if other questions on the application are left blank, in which case States use the interview to complete the application with the household. This process is required at initial application, when the State determines eligibility, calculates monthly benefit amounts, and sets a period of eligibility (the certification period) of typically 6 to 12 months for eligible households. The Act requires States to complete the process to determine eligibility and benefit amounts within 30 days of the date the household files an application form, and within 7 days for households in immediate need. The Act also generally requires States to verify and determine income for the household if the household applies to recertify for SNAP at the end of its certification period, with the exception that States are not required to interview households certified for fewer than 12 months more frequently than once every 12 months. In addition, if a change in the household’s earned income occurs during its certification period, States may be required to obtain verification of earned income during the certification period to determine the household’s ongoing eligibility and monthly benefit amounts.

States have traditionally met the requirement to verify household statements about earned income by obtaining pay stubs or other documentation from the employer. Federal rules require States to inform the household of verification requirements, then the household generally has primary responsibility for obtaining documentation and providing it to the State. In many cases, the State and household identify new circumstances and information that must be verified during the interview. For example, during the interview with the household the State sometimes identifies new earned income sources that the household did not declare on the application form. While SNAP rules require that the State provide the household at least 10 days to provide the required verification within the 30-day application processing period, completing this process delays the eligibility determination and may be challenging.

On the part of the household, it generally requires them to request and obtain new documentation from employers and to deliver it to their local office in-person, by mail, or electronically when that option is available. On the part of the State, it generally requires them to quickly review and process the new documentation provided by applicants.

In some cases, the State may contact the household’s employer(s) directly in order to assist the household with obtaining the necessary documentation to verify its earned income, which is time consuming and sometimes unsuccessful. Moreover, in these cases, employers are not always timely or responsive in providing the requested documentation, especially employers that contract with a third-party entity to manage aspects of their payroll process and payroll data. As a result of these inherent challenges to the verification process, lack of verification is a leading cause of procedurally based denials of SNAP applications and delays in providing benefits to eligible households for many States.

1.2 Project Purpose:

USDA-FNS intends to implement a nationwide verification support service, to be referred to as The National Earned Income Verification Support Service for SNAP, for all 53 State agencies that administer SNAP (hereafter referred to as “States”). USDA-FNS seeks a Contractor that can provide States with the opportunity to automatically verify a significant portion of applicants’ employment status and earned income amounts for purposes of determining SNAP eligibility and benefit amounts, and to a lesser extent for purposes of conducting SNAP Quality Control reviews (these are quality control reviews to determine SNAP payment error rates required of State SNAP agencies per Federal requirements, not to be confused with Contactor responsibilities that may be characterized with the same term in other contexts) and claims calculations. FNS requires services from a third-party income database (TPID) Contractor that can respond to individual queries from across the nation with usable verification data, including the preceding 60 days of earned income data and additional months as requested. The Contractor shall also have the capacity to respond to queries in real time (within seconds) with the payroll data (a match) or to indicate lack of data, among other requirements.

1.3 Scope and Objectives:

The scope and primary objectives of The National Earned Income Verification Support Service for SNAP are as follows:

a. Provide States with a standardized, secure, and user-friendly process by which SNAP eligibility workers and other State personnel may verify SNAP applicant and participant declarations about their earned income amounts via a robust TPID.

b. Extend participation to individual States or groups of States on a voluntary basis, using a phased approach, with the ultimate goal of reaching full participation among all 53 States.

c. Provide States with training and technical assistance upon initial participation and as needed thereafter.

d. Provide States with ongoing technical support via a helpdesk.

e. Provide USDA-FNS and States with quantitative data on the frequency by which the TPID provides data that is usable for purposes of verifying earned income for SNAP at the national, state, and substate level.

2.0 Definitions

Term Abbreviation or Acronym

Definition

Current match Not applicable In response to a query, TPID data that includes, at a minimum, the following information reported directly from the employer:

i. Employee name, Date of birth, and SSN;

ii. Employer name, Address, and Contact information;

iii. Employment status;

iv. Pay frequency (e.g., weekly, biweekly, etc.);

v. All available, but at least one, paycheck(s), earnings statement(s), or other documentation of payment(s) from the employer to the employee issued within the 60-day period preceding the submission of the query.

Data that falls outside this period is not considered a match.

Term Abbreviation or Acronym

Definition

Blanket Purchase Agreement BPA An agreement established by a government buyer with a Schedule contractor to fill repetitive needs for supplies or services (FAR 8.405-3).

Blanket Purchase Agreement Call Order

BPA Call Order A call against an existing blanket purchase agreement to request a service or product provided under the established agreement.

Food and Nutrition Act of 2008 The Act The Federal law that governs SNAP.

Helpdesk Not applicable A department or team that provides technical assistance to

State and Federal personnel regarding usage of The National Earned Income Verification Support Service for SNAP upon request.

Look-back match Not applicable In response to a query, TPID data that includes, at a minimum, the following information reported directly from the employer:

i. Employee name, Date of birth, and SSN;

ii. Employer name, Address, and Contact information;

iii. Employment status;

iv. Pay frequency (e.g., weekly, biweekly, etc.);

v. All available, but at least one, paycheck(s), earnings statement(s), or other documentation of payment(s) from the employer to the employee issued within the 24-month period preceding the submission of the query. Data that falls outside of this period is not considered a match.

Personally Identifiable Information

PII Any representation of information that permits the identity of an individual to whom the information applies to be reasonably inferred by either direct or indirect means.

Supplemental Nutrition Assistance Program

SNAP The Supplemental Nutrition Assistance Program, formerly called the Food Stamp Program. State SNAP agencies, which including all 50 States, the District of Columbia, Guam, and the US Virgin Islands, directly administer SNAP for their residents. USDA-FNS oversees the administration of SNAP at the Federal level.

Social Security Number SSN A unique numerical identifier assigned by the Social Security Administration to U.S. citizens and other residents used for tracking income, benefits, and other purposes.

Query Not applicable A request submitted to the Contractor for a current match or a look-back match. A query is submitted based on an individual Social Security Number.

Third-party income database TPID A database containing employer-provided payroll records that is not State or Federally compiled or managed.

Contractor Requirements

3.0 Technical Requirements

USDA-FNS requires a technically proficient, experienced, and reliable TPID Contractor’s services for The National Earned Income Verification Support Service for SNAP that can meet the requirements listed below.

3.1 Standard Query Process

a. The Contractor shall provide a standardized, secure, and user-friendly process by which thousands of authorized State and Federal personnel can submit queries, using only an individual’s SSN as an identifier, in attempt to obtain either a current match or a look-back match data for the individual from the TPID. This process is hereafter referred to as the standard query process.

b. The standard query process shall allow authorized State and Federal personnel to choose between submitting a query for a current match or a look-back match, as defined in PWS Section 2.0 and PWS Requirement 3.2, prior to submitting a query for one or the other.

c. The standard query process shall include, after a query is submitted, the delivery of a response communicating whether the requested match (either a current match or a look-back match) that corresponds with the submitted SSN is available in the TPID and offer a means for viewing the requested data, if available. The standard query process must complete this exchange within seconds of the query submission, meaning 59 seconds or less.

d. As part of the standard query process, when a match is available and viewed, State and Federal personnel shall have the ability to query and view that same match data again for a 24-hour period. During that 24-hour time period that transaction will be considered a single query and match (not counted separately as multiple queries and matches).

e. As part of the standard query process, the Contractor shall provide State and Federal personnel with the opportunity to request assistance from the helpdesk described subsequently in item 3.5.

f. The standard query process shall be available to authorized State and Federal personnel 24 hours a day, 7 days a week.

g. In the event that the standard query process described in this section is temporarily unavailable, the Contractor shall notify the COR and all authorized State and Federal personnel immediately and shall provide an alternative process by which authorized State personnel can query for data.

h. The Contractor shall track incidents of unavailability of the standard query process, including the respective causes and durations of periods of unavailability in minutes or hours, for each calendar month and the Contractor shall produce reports on that data.

3.2 Required Content of Matches

USDA-FNS requires that the TPID provide specific, actual employment and income data reported directly from the employer. In the vast majority of verification actions, SNAP rules and operations require that the data be recent; older data is generally unusable and therefore unnecessary. In a small minority of verification actions, SNAP rules and operations require the data to cover a longer look-back period. Therefore, the two distinct matches that USDA-FNS requires the Contractor to provide are referred to as a “current match” or a “look-back match.” These two datasets are defined below and also in PWS Section 2.0.

a. A current match, which is strictly defined as follows (note that this term is also defined in PWS Section 2.0):

In response to a query, TPID data that includes, at a minimum, the following information reported directly from the employer:

i. Employee name, Date of birth, and SSN;

ii. Employer name, Address, and Contact information;

iii. Employment status;

iv. Pay frequency (e.g., weekly, biweekly, etc.);

v. All available, but at least one, paycheck(s), earnings statement(s), or other documentation of payment(s) from the employer to the employee issued within the 60-day period preceding the submission of the query. Data that falls outside this period is not considered a match.

b. A look-back match, which is strictly defined as follows:

In response to a query, TPID data that includes, at a minimum, the following information reported directly from the employer:

i. Employee name, Date of birth, and SSN;

ii. Employer name, Address, and Contact information;

iii. Employment status;

iv. Pay frequency (e.g., weekly, biweekly, etc.);

v. All available, but at least one, paycheck(s), earnings statement(s), or other documentation of payment(s) from the employer to the employee issued within the 24-month period preceding the submission of the query. Data that falls outside of this period is not considered a match.

3.3 Geographic Scope and Volume of Data

a. The TPID shall have and maintain an employer network from which it can provide current match data, as defined in PWS Requirements 3.2.a, for a significant volume of employees nationwide. In quantitative terms, the TPID shall include and maintain data that meets the definition of a current match for at least 30 percent of all workers included in the national Total Nonfarm Payroll as defined and published as final by the U.S.

Department of Labor’s Bureau of Labor Statistics for the most recently available calendar year.

b. After contract award, the Contractor shall track the data element described by PWS Requirement 3.3a for each federal fiscal quarter.

c. The Government reserves the right to increase or modify this threshold after contract award based on the availability of new data or changes in the Government’s needs or objectives.

3.4 Delivery of Access to Standard Query Process

a. Initial Delivery of Access to New Participant States:

i. In the context of initially providing access to the standard query process described in PWS Requirement 3.1 on a State-by-State basis, the Contractor shall progressively provide access to individual States or groups of States based upon requests from the COR.

ii. Upon receipt of such a request to provide access to a State or groups of States, the Contractor shall engage directly with State points of contact designated by the COR.

iii. Based on information provided by the State points of contact to the Contractor, the Contractor shall provide initial access and the training materials described in PWS Requirement 3.5.d to at least 50 State personnel, or fewer if specified by the State points of contact, within 20 business days. Upon completion of this task for an individual State, the State shall be considered to be participating in The National Earned Income Verification Support Service for SNAP.

iv. Based on information provided by the State points of contact to the Contractor, the Contractor shall account for the tracking of queries and matches by local office as defined by individual States, per PWS Technical Requirement 3.6.

v. The Contractor must approach this process with a degree of flexibility to accommodate differences across State administrations.

vi. The Contractor shall track and produce reports on the number of business days elapsed prior to completion of this task for each State.

b. Ongoing Delivery of Access to Additional State Personnel within Participant States:

i. After a State has obtained initial access as described in PWS Requirement 3.4.a, the Contractor shall provide a process by which State points of contact can request and obtain access to the standard query process for additional State personnel or groups of State personnel. The Contractor must approach this process with a degree of flexibility to accommodate differences across State administrations.

ii. Upon receiving such a request, the Contractor shall deliver access to the requested individuals within 3 business days of that request.

iii. The Contractor shall track and produce reports on requests for access and the number of business days elapsed prior to resolution of those requests.

c. Delivery of Access to USDA-FNS Personnel:

i. The Contractor shall provide a process by which the COR can request and obtain access to the standard query process for USDA-FNS personnel or groups of USDA-FNS personnel.

ii. Upon receiving such a request, the Contractor shall deliver access to the requested individuals within 3 business days of that request.

iii. The Contractor shall track requests for access and the number of business days elapsed prior to resolution of those requests.

3.5 Helpdesk and Training Materials

a. The Contractor shall provide a helpdesk by which State personnel can submit questions and report issues.

b. The helpdesk shall provide initial responses via email within two business days.

c. The Contractor shall track questions and issues reported to the helpdesk for each calendar month, including initial response times in hours and the number of business days elapsed prior to resolution.

d. The Contractor shall provide State and Federal personnel with basic training videos and written materials, delivered electronically (not paper-based), that teach how to do the following:

i. Submit a query for a current match or look-back match.

ii. Interpret current match and look-back matches.

iii. Obtain technical assistance and support from the helpdesk.

e. The Contractor shall update and redistribute the above described training videos and written materials as needed based on system or process changes.

3.6 Tracking of Queries and Matches

The Contractor shall track and produce reports on the below data elements on queries and matches (a, b, c, d, and e) over the lifecycle of the contract on a monthly, quarterly, and annual basis.

a. The overall number of queries submitted for current matches and look-back matches, respectively, by each

State and the local offices therein as defined by the State.

b. The number of instances in which each State and the local offices therein as defined by the State queried the same SSN for a current match multiple times, excluding any instances in which the State queried the same SSN for a current match multiple times within a single 24-hour period.

c. The overall number of current matches and look-back matches, respectively, provided to each State and the local offices therein as defined by the State.

d. The overall number of queries submitted for current matches and look-back matches, respectively, by Federal personnel.

e. The overall number of current matches and look-back matches, respectively, provided to Federal personnel.

3.7 Compatibility with Government Applications Software

As specified in the BPA call orders, the Contractor shall provide deliverables and/or a reproductive copy of deliverables on media in a format that is compatible with the government office applications software.

3.8 Data Security and Protection of PII

Privacy Act of 1974 - Work performed under this task order may require contractor personnel to have access to Personally Identifiable Information (PII), as defined in OMB memorandum M-07-1616 and as further governed by the Privacy Act, Title 5 of the United States Code (U.S.C.), Section 552a and other applicable law. Contractor personnel shall adhere to all applicable agency rules, regulations, and policies governing the use and safeguarding of PII, including SNAP regulations at 7 CFR 272.1(c).

3.9 Project Support Services

The Contractor shall provide project support services as required in individual BPA call orders. These services shall include:

https://www.ecfr.gov/current/title-7/subtitle-B/chapter-II/subchapter-C/part-272#p-272.1(c)

a. Coordinate multiple concurrent and/or sequential work projects.

b. Prepare comprehensive project reports and correspondence based on information gathered from different project related sources, e.g., the TPID.

c. Monitor overall project status, conduct project coordination. This would include, but not be limited to:

maintaining project schedules; identifying project task scheduling conflicts and notifying responsible parties regarding the conflicts; making arrangements for technical status updates and working group meetings; and preparing presentations, presentation materials, and agendas.

d. Prepare presentations in support of project related management briefings, if needed.

e. Provide system administrator support for a project document repository. This task will include, but not limited to, the following elements: process and maintain record of access requests to the database for authorized personnel; and maintain standardization of the structure of the document repository

f. The Contractor shall prepare, analyze and update program documentation. The Contractor shall review the current documents together with other documentation and update the documentation to reflect the current program status, e.g., maintenance of required records, associated data entry, cost related information, if requested, etc.

3.10 Program Management

The Contractor shall provide program management services for programs or work that represents an overall status of all BPA calls at the BPA level. These services may include, but not be limited to: planning, coordinating with States, conducting financial analyses such as earned value analyses, if applicable, scheduling, monitoring performance, and reviewing program execution actions in support of Government activities.

3.11 Strategic Planning Support

The Contractor shall support USDA-FNS with strategic planning to promote and expand participation in The National Earned Income Verification Support Service for SNAP among the 53 State agencies that operate the program. States are not required to participate; it is a State choice. While USDA-FNS will control and lead strategic planning, the Contractor will support its efforts via this requirement.

4.0 Deliverables / Schedule

The Contractor shall submit PWS Deliverables in a timely fashion. All PWS Deliverables will be accepted or rejected in writing by the COR within fifteen business days after receipt. The table below lists and describes the PWS Deliverables. Please note that all or multiple PWS Technical Requirements may potentially pertain to a single PWS Deliverable in the form of certain reports and meetings, depending on BPA calls in progress at the time and other factors.

No. Deliverable Description Frequency Related PWS Technical Requirement(s)

Delivery Format Due By

4.1 Strategic

Planning Support

The contractor shall submit an initial plan to the COR by the 10th business day following the date of the contract award and amend as requested thereafter based upon details specified at the BPA Call Order level.

At initial contract implementation and amended as required in each BPA Call Order.

3.11 Via email to COR. 10 business days after the

date of the contract award.

4.2 Standard Query

Process and Helpdesk

The Contractor shall provide a process for query submission and data delivery that meets the specifications of PWS Technical Requirement 3.1, and a helpdesk per PWS technical requirement 3.5.

One-time 3.1 and 3.5 Demonstration for COR and specified USDA-FNS personnel, including a walkthrough of the actual process and MS PowerPoint slides documenting functionality and process.

30 business days after contract award.

4.3 Training

Materials

The Contractor shall provide all training materials per PWS technical requirement 3.5.

One-time 3.5.d Via email to COR. 30 business days after contract award.

4.4 Monthly Status

and Progress Report per BPA Call Order

Monthly status and progress report shall be prepared for each active BPA Call Order. The report shall include: a narrative and quantitative description of what was accomplished during the reporting period; total price and staffing data by labor category (if applicable), cumulative cost data (if applicable), and an overview of

Monthly 3.1, 3.4.a, and 3.11 Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The 5th business day of each month after contract award.

activities planned for the following reporting period. The report shall identify issues encountered that may impact the price, scope, or schedule.

4.5 Monthly

Cumulative Status and Progress BPA (inclusive of all Call Orders) Report

Monthly cumulative of all BPA Call Orders issued since date of contract award.

Monthly 3.1, 3.4.a, and 3.11 Via email to COR. The 10th business day of each month after contract award.

4.6 Ongoing

Delivery of Access to Additional State Personnel Report

The Contractor shall provide a report that tracks State-by-State requests for access to the standard query process and the number of business days elapsed prior to resolution of those requests for each calendar month.

Monthly 3.4.b Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The 5th business day of each month after contract award.

4.7 Standard query

process availability Report

The Contractor shall provide a report on incidents of unavailability of the standard query process, including the respective causes and durations of periods of unavailability in minutes or hours, for each calendar month.

Monthly 3.1.h Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The 5th business day of each month and as requested on an ad hoc basis.

4.8 Helpdesk

Responsiveness Report

The Contractor shall track questions and issues reported to the helpdesk for each calendar month, including initial response times in hours and the number of business days elapsed prior to resolution.

Monthly 3.5.c Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The 5th business day of each month and as requested on an ad hoc basis.

4.9 Geographic

Scope and Volume of Data Report

The Contractor shall produce a report on the data elements described by PWS Requirement

Quarterly 3.3.b Via email to COR. The 15th day of the month following the end of the preceding quarter

3.3a for each federal fiscal quarter.

and as requested on an ad hoc basis.

4.10 Query and

Match Report for Participant States

The Contractor shall produce a report, limited to data elements a, b, and c, of PWS Requirement

3.6 representative of each preceding quarter to designated State personnel for each participating State.

Quarterly 3.6 Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The 15th day of the month following the end of the preceding quarter and as requested on an ad hoc basis.

4.11 Query and

Match Report for Participant States

The Contractor shall produce a report of all data elements listed in PWS Requirement 3.6 representative of each preceding quarter by the 15th business day of the month following the end of the preceding quarter and as requested on an ad hoc basis.

Quarterly 3.6 Via email to COR. The 15th day of the month following the end of the preceding quarter and as requested on an ad hoc basis.

4.12 Contractor

Personnel and Expenditure Report

The Contractor shall prepare a comprehensive personnel and expenditure report. The report shall include: BPA Call Order number, States being supported/impacted, and total amount of funds invoiced (detailed by labor, materials, Other Direct Cost, if applicable).

Quarterly Potentially all Technical Requirements, 3.1 through 3.11.

Via email to COR and designated State Points of Contact (as designated or approved by COR.)

The last Friday of each quarter, beginning 3 months after date of contract award.

4.13 In-Progress

Meetings (IPMs)

The Contractor shall participate in IPMs quarterly or as required.

IPMs are formal reviews during which the status of all BPA Call Orders is discussed. At each IPM, the Contractor shall address each active order, including a summary of the progress during the previous period and an overview of activities planned for the next period. In addition, the

Quarterly or as required.

Potentially all Technical Requirements, 3.1 through 3.11.

MS TEAMS or Webex. The 10th business day of each month after contract award.

Contractor shall address problems and issues encountered or anticipated which may impact performance in terms of price, scope, or schedule. The Contractor shall prepare meeting minutes of each IPM for the government’s review and concurrence. At the discretion of the government more frequent informal meetings may be required.

4.14 General

Contract Data Requirements

The Contractor shall prepare all documents, analyses, plans, manuals, specifications, meeting minutes, profiles, procedures, studies, technical reports, notices, estimates, proposals, charts, packages, notifications, guides, briefings, and other data items as specified on individual BPA Call Orders.

As required. 3.5, 3.6, and 3.9. As specified on individual BPA Call Orders.

As specified on individual BPA Call Orders.

5.0 Government Furnished

Government Furnished Property (GFP) which includes Government Furnished Material (GFM), Government Furnished Information (GFI), and Government Furnished Equipment (GFE) may be provided to support individual BPA Call Orders as identified in each BPA Call Order request.

6.0 Travel

Not applicable. There are no travel requirements for this requirement.

7.0 Contractor’s Key Personnel

7.1 General Personnel Requirements

The Contractor shall assure that the professional and technical personnel have sufficient qualifications to perform work as required by the government, and that those qualifications are maintained during the life of the contract. The Contractor shall be responsible for approving individual resumes and qualifications to ensure appropriate assignment to a labor category. It shall be the sole responsibility of the Contractor to staff their team properly and abide by the guidelines.

7.2 Minimum Qualifications for Key Personnel

Minimum Qualifications for two Key Personnel are as follows:

1. Project Manager:

a. Five or more years of project management experience on federal projects and/or programs.

b. Senior-level FAC-P/PM certified or certified in industry standard project management platforms (e.g., PMP, PMBOK, etc.)

c. Familiarity with SNAP policy or commitment of time and energy to understand the fundamentals of SNAP policy.

d. Experience managing projects involving the delivery of data matching or verification services to public or private sector entities.

e. Ability to establish and monitor project budgets, oversee quality control, and adherence to project schedules.

f. Strong verbal and written communication skills.

g. Demonstrated competency in requirements development management process, testing and evaluation, reporting program results, strategic planning, and business financial management.

2. Program Manager:

a. Five or more years of project management experience on federal projects and/or programs.

b. Senior-level FAC-P/PM certified or certified in industry standard project management platforms (e.g. PMP, PMBOK, etc.)

c. Familiarity with SNAP policy or commitment of time and energy to understand the fundamentals of SNAP policy.

d. Ability to establish and monitor project budgets, oversee quality control, and adherence to project schedules.

e. Strong verbal and written communication skills.

f. Demonstrated competency in requirements development management process, testing and evaluation, reporting program results, strategic planning, and business financial management.

8.0 Security Requirements

The contract provision set forth below covers the basic security standards for Sensitive-But-Unclassified (SBU) work.

• General o The Government anticipates that the work to be performed under this contract may involve access to SBU materials and non-sensitive materials. SBU materials may include, but are not limited to: computer systems and information, Privacy Act protected information, and FNS proprietary information. Duplication or disclosure of the data and other information to which the Contractor may have access as a result of this contract is prohibited by Public Law.

o In general, services performed by Contractor’s personnel may fall within three (3) “risk” categories as described below:

High Risk (MBI): Contract personnel with network administrative rights.

Moderate Risk (NACI): All other contract personnel with access to SBU FNS data or information.

Low Risk (Fingerprint): Contract personnel performing less than 180 days.

• Types and Number of Background Investigations Required o Work performed under the contract may fall within one or more of the risk categories defined in paragraph (a)(2) above. As a result, the Contractor ’s personnel shall undergo a background investigation. The type of background investigation required will be commensurate with the risk factor associated with the duties of each position and the type of access required. Prior to award of the contract, the Contracting Officer’s Representative (COR) will determine the exact number and types of background investigations that may be required for all Contractor positions.

o The Contractor will not be permitted to commence performance under the contract until a sufficient number of its personnel, as determined by the COR, have received requisite background investigations. A “Background Investigation Request” form (FNS-775) shall be completed by the COR and submitted to the Contract Management Division (CMD) for processing.

o During the life of this contract, the Contractor shall ensure that no Contractor or sub-Contractor employee commences performance hereunder prior to receipt of authorization from the Contracting Officer or COR.

• Background Investigations Requirements o The minimum investigative requirements are as follows:

High Risk Positions: The background investigation shall be an MBI (Minimum Background Investigation). The MBI includes a NACIC, a face-to-face personal interview between the investigator and the subject, and telephone inquiries to selected employers.

Moderate Risk Positions: The background investigation shall be a NACI (National Agency Check and Inquiries). The NACI consists of a

NAC, written inquiries and record searches covering specific areas of a subject’s background during the past 5 years.

Low Risk Positions: The background investigation shall be a Federal Bureau of Investigation Name and Fingerprint check.

• Separation/Termination of Contractor Employees/Completion of Contract o At the completion of the contract or separation/termination of any Contractor employee, a “Government Contractor Separation Checklist” (FNS-774) shall be completed and signed by the COR and Contracting Officer.

• USDA-FNS Computer System Access o To perform this contract the Contractor may require computer access to FNS systems. As necessary, the Contractor shall notify the COR in writing when a Contractor’s employee requires any type of computer access. The COR shall provide form FNS-674, Computer System Access Request, to the Contractor. The Contractor shall complete the form, obtain approval from the COR, and submit the form to the FNS Security Office staff. The Contractor shall notify FNS when computer system access for employees can be terminated. Written notification to terminate computer access shall be provided by the Contractor to the COR and to the FNS Security Office staff immediately upon termination of any Contractor employee removed from this contract or when access is no longer required. Immediately upon completion of the contract the Contractor shall provide a complete listing of all Contractor employees given access to FNS computer systems with a statement that computer access shall be terminated and complete a “Government Contractor Separation Checklist” for each Contractor employee. All notifications shall be provided to the COR and the FNS Security staff listed below:

Office of Information Technology Information Security Office 1320 Braddock Place Alexandria, VA 22314, (703) 305-2242

Additionally, ALL new contract employees accessing USDA-FNS systems and/or sensitive data are required to complete Security Training prior to obtaining computer and sensitive data access. This training shall be coordinated with the COR. A disk or hard copy of the security training may be sent to Contractor s whose staffs are performing at off-site locations.

9.0 Data Rights

The government will retain unlimited, limited, or restricted rights to resulting documentation, information and products, as applicable. Additionally, the appropriate data and data rights clauses and provisions will be included in the solicitation and resulting contract.

10.0 Section 508 - Electronic and Information Technology Standards

IT Accessibility Requirements

Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it shall be accessible to people with disabilities. Federal employees and members of the public who have disabilities must have access to, and use of, information and data that is comparable to people without disabilities.

Products, platforms and services delivered as part of this work statement that are ICT, or contain ICT, must conform to the Revised 508 Standards, which are located at 36 C.F.R. § 1194.1 & Apps. A, C & D, and available at https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines

Item that contains ICT: Data services or information retrieval systems

Applicable Functional Performance Criteria:

All functional performance criteria apply when using an alternative design or technology that achieves substantially equivalent or greater accessibility and usability by individuals with disabilities, than would be provided by conformance to one or more of the requirements in Chapters 4-6 of the Revised 508 Standards, or when Chapters 4-6 do not address one or more functions of ICT.

301.1 Scope - The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

302.1 Without Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision - Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color - Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing - Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech - Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength - Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

https://www.section508.gov/ict-accessibility#e301_1 https://www.section508.gov/ict-accessibility#e302_1 https://www.section508.gov/ict-accessibility#e302_1 https://www.section508.gov/ict-accessibility#e302_1 https://www.section508.gov/ict-accessibility#e302_1 https://www.section508.gov/ict-accessibility#e302_1 https://www.section508.gov/ict-accessibility#e302_1

302.9 With Limited Language, Cognitive, and Learning Abilities - ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Applicable requirements for software features and components:

All WCAG Level AA Success Criteria, 502 Interoperability with Assistive Technology, 503 Application

E207.1 General - Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5

E207.2 WCAG Conformance - User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

E207.2.1 Word Substitution - When Applying WCAG to Non-Web Software For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”

E207.3 Complete Process for Non-Web Software - Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.

Applicable requirements for hardware features and components: All requirements apply

Applicable support services and documentation: All requirements apply

Electronic Content Technical Criteria:

E205.1 General -Electronic content shall comply with E205.

E205.2 Public Facing -Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

602 Support Documentation

603 Support Services https://www.section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 https://www.section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 https://www.section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 https://www.section508.gov/ict-accessibility#e207_1__e207_2__e207_2_1__e207_3 https://www.section508.gov/ict-accessibility#e205_1_general https://www.section508.gov/ict-accessibility#e205_2_public_facing https://www.section508.gov/ict-accessibility#602__603__302

302 Functional Performance Criteria

Exceptions:

E501.1 Scope - Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

11.0 Performance Requirement Measures

No. Performance Standard Related PWS

Requirement(s)

Related PWS Deliverable(s)

Method of Surveillance Frequency Consequence for Failure to Meet Performance Standard

11.1 The Contractor shall provide the standard query

process and a helpdesk.

3.1 and 3.5 4.2 COR review of PWS Deliverable 4.2.

One time TBD

11.2 The Contractor shall provide training materials

per PWS technical requirement 3.5.

3.5 4.3 COR review of PWS Deliverable 4.3.

One time TBD

11.3 The contractor shall submit an initial plan to the

COR by the 10th business day following the date of the contract award and amend as requested thereafter based upon details specified at the BPA Call Order level.

3.11 4.1 COR review of PWS Deliverable 4.1.

At initial contract implementation and amended as required.

TBD

11.4 The Contractor shall provide new participant

states with access to the standard query process and the training materials for at least 50 State personnel (or fewer if specified by the State points of contact) within 20 business days of request by the COR.

3.4.a and 3.5.d 4.5 COR review of PWS Deliverable 4.5.

Monthly TBD

11.5 The Contractor shall provide a process by which

State points of contact can request and obtain access to the standard query process for additional State personnel or groups of State personnel. Upon receiving such a request, the Contractor shall deliver access to the requested

3.4.b 4.6 COR review of PWS Deliverable 4.6.

Monthly TBD https://www.section508.gov/ict-accessibility#e501_1_scope_exception

No. Performance Standard Related PWS

Requirement(s)

Related PWS Deliverable(s)

Method of Surveillance Frequency Consequence for Failure to Meet Performance Standard individuals within 3 business days of that request.

11.6 The standard query process will be available to

participant states 24 hours a day, 7 days a week.

3.1.f 4.7 COR review of PWS Deliverable 4.7.

Monthly TBD

11.7 The helpdesk shall provide an initial response to

all requests within two business days.

3.5.b 4.8 COR review of PWS Deliverable 4.8.

Monthly TBD

11.6 The TPID shall maintain data that meets the

definition of a current match as defined in PWS Requirements 3.2.a for at least 30 percent of all workers included in the national Total Nonfarm Payroll as defined and published as final by the U.S. Department of Labor’s Bureau of Labor Statistics each federal fiscal quarter.

3.3 4.9 COR review of PWS Deliverable 4.9.

Quarterly TBD