S-839-RFP_Attachments_A-F.docx

Attachment A: Responder Declarations The undersigned certifies, to the best of his or her knowledge and belief, that:

A. Response Contents. The information provided is true, correct, and reliable for purposes of evaluation for potential contract award. The submission of inaccurate or misleading information may be grounds for disqualification from the award as well as subject the Responder to suspension or debarment proceedings as well as other remedies available by law B. Authorized Signature. This Declaration is signed by the appropriate person(s), with the authority to contractually bind the Responder, as required by applicable articles, bylaws, resolutions, minutes, and ordinances.

C. Non-Collusion Certification.

1. The Proposal has been arrived at by the Responder independently and has been submitted without collusion and without any agreement, understanding or planned common course of action with any other vendor designed to limit fair or open competition; and

2. The contents of the Response have not been communicated by the Responder or its employees or agents to any person not an employee or agent of the Responder and will not be communicated to any other individual prior to the due date and time of this Solicitation. Any evidence of collusion among Responders in any form designed to defeat competitive responses will be reported to the Minnesota Attorney General for investigation and appropriate action.

D. Organizational Conflicts of Interest. To the best of Responder’s knowledge and belief, and except as otherwise disclosed, there are no relevant facts or circumstances which could give rise to an organizational conflict of interest. An organizational conflict of interest exists when, because of existing or planned activities or because of relationships with other persons,

1. a vendor is unable or potentially unable to render impartial assistance or advice to the State;

2. the vendor’s objectivity in performing the contract work is or might be otherwise impaired; or

3. the vendor has an unfair competitive advantage.

If after award, an organizational conflict of interest is discovered, an immediate and full disclosure in writing must be made to the State’s Chief Procurement Officer which must include a description of the action which the contractor has taken or proposes to take to avoid or mitigate such conflicts. If an organizational conflict of interest is determined to exist, the State may, at its discretion, cancel the contract. In the event the Contractor was aware of an organizational conflict of interest prior to the award of the contract and did not disclose the conflict to OSP, the State may terminate the contract for default. Organizational conflicts of interest terms apply to any subcontractors for this work.

E. Certification Regarding Lobbying. For State of Minnesota Contracts and Grants over $100,000, the undersigned certifies, to the best of his or her knowledge and belief that:

1. No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.

2. If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL, Disclosure Form to Report Lobbying in accordance with its instructions.

3. The undersigned shall require that the language of this certification be included in the award documents for all sub-awards at all tiers (including subcontracts, sub-grants, and contracts under grants, loans and cooperative agreements) and that all sub-recipients shall certify and disclose accordingly.

This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into and is a prerequisite for making or entering into this transaction imposed by 31 U.S.C. 1352. Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.

F. Copyrighted Material Waiver. By signing its Response, the Responder certifies that it has obtained all necessary approvals for the reproduction and distribution of the contents of its response.

G. Diverse Spend Reporting. The Sample Contract contains a clause for Diverse Spend Reporting. When this clause applies, Contractor will be required to register in a free portal to report diverse spend.

Please see Diverse Spend Reporting Frequently Asked Questions for additional information.

By signing this form, Responder acknowledges and certifies compliance with all applicable requirements indicated above.

Company Name:

Signature:

Printed Name:

Title:

Date:

Phone Number:

Email Address:

Attachment B: Exceptions to State’s Terms and Conditions The State presumes a responder agrees to the terms and conditions of this solicitation unless a responder takes specific exception to one or more of the conditions on this form.

The State reserves the right to reject, negotiate, or accept any exception listed to the State’s terms and conditions (including those found in the attached Sample Contract).

INSTRUCTIONS: A responder must explicitly list all exceptions to State’s terms and conditions, if any (including those found in the attached Sample Contract). Reference the clause number and page number of the State's term and condition for each of a responder’s exceptions. If no exceptions exist, state "NONE" specifically on the form below. Whether or not exceptions are taken, the Responder must sign and date this form and submit it as part of their response. (Add additional pages if necessary.)

By signing this form, I acknowledge that the above-named responder accepts, without qualification, all terms and conditions stated in this solicitation (including the sample contract) except those clearly outlined as exceptions above. This acknowledgement includes acceptance of the section of the Sample Contract, Exhibit A, titled “Contractor’s Documents.”

Signature:

Printed Name:

Title:

Date:

Attachment C: Cost Detail

1. Cost Proposal. Responders should review Exhibit D of the Sample Contract for additional pricing terms related to the Cost Proposal.

Responders must download and use the Exhibit D Price Schedule attached to this Solicitation. The Price Schedule must be completed by the Responder and uploaded with the response. If pricing is not returned with your solicitation response, your response will be rejected. Failure to use the Price Schedule may be cause for rejection. Responders are strongly encouraged to provide a price for all line items. The State reserves the right to reject responses that do not supply sufficient line items.

2. Catalogs and Price Literature.

Responders may submit copies of all applicable catalogs, on-line catalog addresses, or price lists used for pricing purposes with their response. Do not submit marketing material with your response unless otherwise requested.

All price lists proposed must meet accessibility requirements per the Minnesota IT Services, Office of Accessibility website: https://mn.gov/mnit/programs/accessibility/

3. Alterations or Erasures. The State reserves the right to reject a response containing an alteration or erasure of any price used to determine the lowest responsible responder unless the alteration or erasure is done in a manner that is clear and authenticated by an authorized representative of the Responder. An acceptable way to make an alteration or erasure is to cross out the price, print the correction in ink adjacent to it, and have an authorized representative of the Responder initial and date that correction.

Attachment D: Workforce and Equal Pay Declaration Page

Attachment E: Additional Information

1. Contractor’s Contact Information. Provide the contact information for the representative responsible for the management of the contract and the representative receiving purchase orders.

Contractor’s Legal Name

Address

Contact Person (Contract)

Email Address

Telephone Number

Contact Person (PO Order)

Email Address

Telephone Number

2. Prompt Pay Discount. What prompt pay discounts do you offer? Select all that apply, if “other,” specify terms in the comment section below:

Rev. April 2025 Rev. April 2025

· 1% in 30

· 2% in 30

· 3% in 30

· 1% in 10, Net 30

· 2% in 10, Net 30

· 3% in 10, Net 30

· 5% in 10, Net 30

· Other 1% in 15, Net 30

· 2% in 15, Net 30

· 3% in 15, Net 30

· 1% in 20, Net 30

· 2% in 20, Net 30

· 3% in 20, Net 30

· Net 30

Comments:

Attachment F: Specifications, Duties, Scope of Work

1. Instructions Attachment F provides specific details about the State’s requirements, including the technical specifications for the requested services, and solicits detailed information from responders regarding their proposed plans for meeting these requirements.

Thoroughly review the State’s Requirements and Scope of Work and provide detailed responses to the questions and submit all requested supplemental information.

NOTE: Do not include your cost proposal or any pricing information in your response to the questions in this Attachment. Include price information on Exhibit D to the Sample Contract, only.

2. Background and Objective The objective of the Solicitation is to select a Contractor that can accurately provide the State with reports of probable match deaths and exact match deaths of Active Recipients and Inactive Members. The State prefers that a responder provide both a standard death audit solution and a verified death audit solution.

For reference only, the State’s Recipient File currently contains approximately:

· 96,000 Recipient records for the TRA; and

· 183,000 Recipient records for PERA.

The State intends to utilize Contractor to provide death audit services on a semi-annual basis for the State’s Inactive file. The State is also seeking verification services for its Inactive file. The State’s Inactive File contains approximately:

· 70,000 Inactive records for the TRA: and

· 205,000 Inactive records for PERA.

For additional background information review Section 2, Summary of Scope, of the Solicitation.

3. Definitions.

For purposes of this RFP, definitions are as follows and will be set forth in the Contract:

Active Member. An individual, who is not retired, that is working for a covered employer.

Business Day. Monday-Friday, excluding Federal Public Holidays, from 8:00 a.m. – 5:00 p.m. Central Standard Time Exact Match Record. An individual record where the social security number (SSN), last name, first name, and date of birth data elements are exactly the same in the data file supplied by the State to Contractor and in the data found in Contractor’s Database. It also includes an individual record that required Verification Services to verify the accuracy of any non-matching data elements in order to meet the confidence level for an exact match as approved by the State. This type of record qualifies for the highest confidence level of a death match supplied by Contractor as agreed to by Contractor and State.

Inactive Member. An individual, who is not receiving a monthly benefit, that is no longer working for a covered employer.

Inactive File. The State file composed of individuals not currently receiving a monthly benefit or working for a covered employer.

Obituary Database. A computerized database of death information from proprietary and non-proprietary databases that will be used to perform the death match services. The database must include death information reported to the United States Social Security Administration, death information from the Office of Vital Statistics or similar office in each state willing to share their data with Contractor, death information from obituary data compiled by Contractor, and all the other entities and data sources including social media (also referred to as the “Sources”) Probable Match Record. An individual record in which some but not all of the data elements supplied by the State to Contractor match the data found in Contractor’s Database. This type of record will have varying confidence levels of a death match depending upon the number of data elements that match exactly, the number of data elements with a probable match, the number of data elements that are non-matching, and the ability of Contractor to verify the accuracy of the probable and non-matching data element.

Recipient. An individual receiving a monthly benefit.

Recipient File. The State file composed of individuals receiving a monthly benefit or may have a future interest in a monthly benefit.

Verification Services. The services provided by Contractor to research and verify whether data elements that are not an exact match are able to be verified as a match to increase the confidence level of a Recipient death match. The scope of these services is described in the Contract.

Verification Team. Team of subject matter experts that can provide verification services.

Attachment F, Supplement 1: File Layout Preferences The State prefers a fixed-length file with the following columns, at a minimum: SSN, Last Name, First Name, DOB, Address/Zip, Empty space for Group, and the State’s unique ID.

Attachment F, Supplement 2: Response Document Mandatory Specifications. Any specification that includes must is considered to be a mandatory specification and will be considered on a pass/ fail basis. Use of may and should in the specifications below is intention.

1. Qualifications.

1.1 Experience. Contractor must have provided Death Audit Services for a minimum of five (5) years.

1.1.2 Provide the number of employees, client base, and location of offices for your company:

1.2 Background Checks. Contractor must conduct background checks for Contractor’s employees that perform work under this contract (see Exhibit A of the Sample Contract, Paragraph 35, Background Security Compliance).

☐ Yes ☐ No Responder conducts the required background checks for its employees.

1.2.1 Describe how your company meets this requirement:

1.3 Data Protection Statutes (State and Federal). Contractor must comply with applicable state and federal statutes and regulations addressing data protection, including protection of sensitive data (e.g., Social Security Numbers and Dates of Birth) and Personally Identifiable Information.

☐ Yes ☐ No Responder complies with applicable state and federal statutes and regulations addressing data protection, including protection of sensitive data (e.g., Social Security Numbers and Dates of Birth) and Personally Identifiable Information.

1.3.1 Describe how your company meets this requirement:

1.4 Risk Control Procedures. Contractor must maintain reasonable risk control procedures to protect against unauthorized access of both computer resources and data to preclude erroneous or fraudulent activities.

☐ Yes ☐ No Responder maintains reasonable risk control procedures to protect against unauthorized access of both computer resources and data to preclude erroneous or fraudulent activities.

1.4.1 Describe Responder’s security policies, procedures, and processes for:

· Securing the State’s data files;

· Securing personally identifiable information;

· Detecting and preventing account fraud and abuse.

1.4.2 Describe Responder’s process for client notification and remediation in the event suspicious activity is detected:

1.5 Database Maintenance. Contractor must maintain its database in good working order.

1.6 Data Security Agreements. Contractor must sign both the TRA and PERA’s Data Security and Confidentiality Agreements in order to receive an award (see Exhibit E of the Sample Contract for the Agreements).

☐ Yes ☐ No Responder agrees to comply.

Contractor may be required to sign additional security documents if required by the end users (see Exhibit E of the Sample Contract for an example of such a document).

☐ Yes ☐ No Responder agrees to comply.

2.0 Service Requirements

2.1 Obituary Database. Contractor must maintain a computerized database of death information from proprietary and non-proprietary databases that will be used to perform the death match services. The database must include death information reported to the United States Social Security Administration, death information from the Office of Vital Statistics or similar office in each state willing to share their data with Contractor, death information from obituary data compiled by Contractor, and all the other entities and data sources including social media (hereinafter referred to as the “Sources”).

The desired database should provide coverage to identify and report deaths occurring within all fifty (50) states and the District of Columbia, and should include the territories of Guam, Puerto Rico, and the US Virgin Islands.

2.1.2 Database for fifty (50) States and District of Columbia.

☐ Yes ☐ No Responder’s proprietary and non-proprietary Sources of data utilized in Responder’s Death Database provide coverage to identify and report deaths occurring within all fifty (50) states and the District of Columbia.

If Responder’s Sources do not provide coverage for all fifty (50) states and the District of Columbia, identify which state(s) Responder is unable to provide coverage, and if Responder is actively working to obtain such coverage:

2.1.3 Database for US Territories.

☐ Yes ☐ No Responder’s proprietary and non-proprietary Sources of data utilized in Responder’s Death Database provide coverage to identify and report deaths occurring within the territories of Guam, Puerto Rico, and the US Virgin Islands.

If Responder’s Sources do not provide coverage within the territories of Guam, Puerto Rico, and the US Virgin Islands, identify which territory(ies) Responder is unable to provide coverage, and if Responder is actively working to obtain such coverage:

2.1.4 Database Sources.

2.1.4.1 Provide a listing of the proprietary and non-proprietary Sources of data (e.g. Social Security Administration Death Master File, Office of Vital Statistics or similar office in each state, etc.) in Responder’s Database that will be used to perform the death match services.

2.1.4.2 Provide a concise summary explanation of the Sources of data identified above.

· The summary should list the states that authorize Responder to obtain death information through the Office of Vital Statistics or similar office (Death Database).

· The summary should include:

(1) the ranges of dates of death data covered by each of the data Sources;

(2) the number of records contained in Responder’s Death Database; and

(3) the number of records added each year for the past three calendar years (2023, 2024, and 2025).

2.1.4.3 Provide a detailed description of the data elements maintained for each record in Responder’s Death Database.

2.1.5 Database Update Method and Frequency.

2.1.5.1 Provide a detailed description of the method and frequency of updates to Responder’s Death Database:

2.1.5.2 Provide a concise summary explanation of the Sources of data in Responder’s Database that is death information compiled from obituary data (Obituary Database). The summary should include information about the obituary Sources of data within all fifty (50) states and the District of Columbia with numbers of records in each state and the date ranges of obituary data in each state. This summary should include the number of records contained in Responder’s Obituary Database, and the number of records added each year for the past three calendar years (2023, 2024, and 2025).

2.1.5.3 Provide a detailed description of the data elements maintained for each record in Responder’s Obituary Database.

2.1.5.4 Provide a detailed description of the method and frequency of updates to Responder’s Obituary Database.

2.2 Work Plan. Provide a description of the deliverables to be provided by the Responder along with a detailed work plan that identifies the major tasks to be accomplished and be used as a scheduling and managing tool, as well as the basis for invoicing. This document should NOT list cost detail.

2.3 Training. Contractor must provide the State with training for the State’s administrators and end users on the use, capabilities, and functionality of the system. The training must be provided annually, or as agreed upon by the State and the Awarded Contractor. The format of the annual training may be live in-person or remotely through a live webinar. Contractor may provide additional or supplementary training opportunities through live in-person, remote live webinar, or prerecorded content.

2.2.1 Describe the training options available. Include with your response a concise summary of the content of the initial training and any optional subsequent trainings, any training materials that will be provided or made available to the attendees, the location or format of the offered training(s), the length of the offered training(s), and the number of attendees per training.

3.0 Scope of Work: Death Match Search.

Recipient File. The State will provide Contractor with an electronic Recipient File containing the data elements listed in Attachment F, Supplement 1 (File Layout Preferences). The State will provide Contractor with an updated electronic Recipient File on a quarterly basis, or on an interval as determined by the State. The file will be delivered by the State to Contractor in a text format and via a secure file transfer protocol (“SFTP”) server or through such arrangement as shall be mutually agreed to by the parties.

Upon receipt of the file, Contractor must compare the respective data elements provided by the State on each Recipient record against the data elements in Contractor’s database. The comparison process must be performed in the manner described in the Contract.

Inactive File. The State will provide Contractor with an electronic Inactive File containing the data elements contained in Attachment F, Supplement 1 (File Layout Preferences). The State may provide Contractor with an updated electronic Recipient File on a semi-annual basis, or on an interval as determined by the State. The file will be delivered by the State to Contractor in a text format and via a SFTP server or through such arrangement as shall be mutually agreed to by the parties.

Upon receipt of the file, Contractor shall compare the respective data elements provided by the State on each such Inactive record against the data elements in Contractor’s database. The comparison process must be performed in the manner described in the Contract.

3.1 Standard Death Audit Service. For each Probable Match Record with a confidence level in the range of a probable match as described in the Contract, Contractor must identify the source(s) of the match. For any probable match, regardless of probability, Contractor must provide the State a copy of the obituary record or the text of the obituary record for the reported probably match if such record is available.

☐ Yes ☐ No Responder’s proposed solution includes a standard death audit service. If yes, provide a response to the following questions. If no, skip ahead to section 3.2.

3.1.1 Describe the different confidence levels utilized by Responder’s proposed standard service solution (i.e., high, medium, and low, where high means a 75% likelihood or higher of a match). Provide a description of how Responder defines confidence levels for members that are not an exact match on SSN, DOB, first name, and last name.

3.2 Verified Death Audit Service. For each Probable Match Record with a confidence level in the range of a probable match as described in the Contract, Contractor must perform Verification Services. The results of Contractor’s Verification Services must be included on the Death Match Search Report and communicated to the State using the logic as described in the Contract. Contractor must be able to provide verification services through a team of subject matter experts (“Verification Team”) skilled at verifying any data elements that are not an exact match to the corresponding data element provided by the State. Contractor must be able to perform verification services in order to convert probable death matches into a death match with a confidence level high enough to consider the death match an exact match.

☐ Yes ☐ No Responder’s proposed solution includes a verified death audit service. If yes, provide a response to the following questions. If no, skip ahead to section 3.3.

3.2.1 Describe the different confidence levels utilized by Responder’s verified match service and what confidence level Responder corresponds to an exact match. Describe how the Respondent defines confidence levels for members that are not an exact match on SSN, DOB, first name, and last name.

3.2.2 Provide a detailed description of the confidence level methodology Responder will use to convert a probable match into an exact match. Describe how Responder reports a probable match Responder is unable to verify.

3.2.3 Describe how the data elements provided by the State will be matched to Responder’s Death Database, including how Responder’s proposed solution uses fuzzy logic.

3.2.4 Describe how the data elements provided by the State will be matched to the Respondents Obituary Database, including how, for each obituary match, Responder makes the determination of whether a match is an exact match or a probable match.

3.2.5 Describe how Responder prevents duplicate reporting of exact or probable matches:

☐ Yes ☐ No Responder has a team of subject matter experts that can provide verification services (“Verification Team”). If Yes, provide a response to the following questions:

· List the number of members on the team including a description of their training and years of experience performing verification services (note do not include Non-Public/Trade Secret data (as defined by Minn. Stat. § 13.37); and

· Describe all the methods utilized by the Verification Team to verify non-matching data elements.

3.3 Ad Hoc Search Capabilities. Contractor must provide the State with ad hoc search capabilities to perform unlimited single record and list run searches of Contractor’s Database. The State must have ad hoc access to address and relative search capabilities. The State requires verification services for ad hoc searches.

3.3.1 Describe the ad hoc search capabilities of Responder’s proposed solution, including how the State will access the Database.

If there are additional costs associated with the State accessing ad hoc searches, those costs must be identified on the State’s Price Schedule, Exhibit D to the Sample Contract.

3.4 Reports.

3.4.1 Format of Reports.

3.4.1.1 The preferred format of the State’s outbound file, inbound file, and matching indicator logic is found in Attachment F, Supplement 1 (File Layout Preferences). However, the specific file format to be used will be negotiated and included in the final Contract. Once included in the Contract, the Contractor agrees that any changes to the file format to be used for the outbound file, inbound file, and matching indicator logic shall be subject to the Amendment provisions of the Contract.

☐ Yes ☐ No Responder will use the preferred file format and matching indicator logic supplied by the State in Attachment F, Supplement 1 (File Layout Preferences).

If Responder does not intend to use the preferred file format, a sample file format in Microsoft Excel must be included in Responder’s Technical Proposal along with a justification or explanation for Responder’s modification of the preferred file format.

3.4.1.2 Responder should include a summary of how future modifications to the State’s preferred file formats and matching indicator logic would improve the death match and obituary match results supplied by Responder.

3.4.1.3 Describe how the components and functionality of reports will meet the following requirements:

· The report must allow for new deaths reported by Contractor to the State (deaths that are being reported for the first time) to be clearly separated from any other deaths in the report.

· The State must have the ability to sort and filter the report and to export or download the report as a CSV or TSV file.

☐ Yes ☐ No Responder can meet these requirements.

3.4.2 Death Match Search Report.

3.4.2.1 Upon the completion of each death match search, Contractor must provide to the State a report indicating the data elements matched for each individual record.

The report must utilize matching indicators and confidence level logic that identifies all the Source(s) for Exact Match Records and Probable Match Records. For each Probable Match Record, the logic utilized by Contractor must identify all the data elements that were exact or probable matches using the reporting logic described in the Contract. For each Probable Match, Contractor must attach the top three documentary Sources that indicate a match and a copy of an obituary record or text of the obituary record, if such obituary documentation is available.

☐ Yes ☐ No Responder can meet these requirements.

3.4.2.1.1 Describe how Responder will determine what constitutes the top three documents that indicate the probability of a match:

3.4.2.1.2 Provide a sample report for Responder’s proposed standard service. All protected or confidential information must be redacted from the sample report. The report must:

· Separate current deaths (reported for the first time) and previously reported deaths. The current deaths and previously reported deaths must be separated by record type (recipient or inactive);

· Indicate the level of confidence in the match;

· Indicate the Source(s) of the match;

· Attach the top three documentary Sources that indicate a match; and

· Attach an obituary record or text of the obituary record, if such documentation is available.

3.4.2.1.3 Provide a sample report for Responder’s proposed verified match service. All protected or confidential information must be redacted.

The sample report must:

· Separate current deaths (reported for the first time) and previously reported deaths. The current deaths and previously reported deaths must be separated by record type (recipient or inactive);

· Indicate the Source(s) of the match; and

· Show a detailed example of how potential matches on both death records and obituary records will be verified by Responder including fields matched and the level of confidence in each match.

3.4.2.2 Timing and Delivery of Report. Contractor must deliver the Death Match Search Reports to the State on a weekly basis, with each weekly report due on Monday by 6:00 a.m., Central Time. Delivery must be securely transmitted by SFTP server or through such secure means as agreed to by the parties. The SFTP server must be hosted by Contractor and cannot be hosted by a third party. Contractor must provide the State with written notification via email to the State’s identified contacts when the report is available.

☐ Yes ☐ No Responder can meet these requirements.

3.4.2.2.1 Describe Responder’s ability to meet this turnaround time:

3.4.2.2.2 For reports including verification services, describe the turnaround time required for the Verification Team to perform their services and return a report to the State.

If no, describe how Responder will notify the State when a report is available:

3.4.3 Ad Hoc File – Death Match Search Report. At the State’s request, the State may provide Contractor with an ad hoc file of individual records and Contractor must provide a Death Match Search Report. The format of the report is identical to the file format layout in Attachment F, Supplement 1 (File Layout Preferences) or similar format agreeable to the parties.

3.4.3.1. For a single record search Contractor must deliver the Ad Hoc File – Death Match Search Report within one (1) business day of the State’s issuance of a Purchase Order for these services.

☐ Yes ☐ No Responder can meet these requirements.

3.4.3.1.1 Describe Responder’s ability to meet this turnaround time:

3.4.3.1.2. For reports including verification services, describe the turnaround time required for the Verification Team to perform their services and return a report to the State:

3.4.3.2 For a list run search Contractor must deliver the Ad Hoc File – Death Match Search Report within five (5) business days of the State’s issuance of a purchase order for these services.

☐ Yes ☐ No Responder can meet these requirements.

3.4.3.2.1 Describe Responder’s ability to meet this turnaround time:

3.4.3.2.2 For reports including verification services, describe the turnaround time required for the Verification Team to perform their services and return a rep:

4. Service Catalog.

4.1 Provide a list of Additional Services that may be of interest:

Note: Provide pricing for “Additional Value Added-Options” and “Discount Off Service Catalog” options in Exhibit D: Price Schedule.

Attachment F, Supplement 3: PERA Vendor Risk Assessment Questionnaire The responder must pass security requirements prior to Award. As part of the security assessment process, Responders must download and submit Attachment F, Supplement 1: PERA Vendor Risk Assessment Questionnaire attached to this Solicitation.

Rev. 12/19 Page 1 of 15

Rev. 9.01.2021