Accessibility Information

Users of assistive technologies such as screen readers should use the following link to activate Accessibility Mode before continuing: Learn more and Activate accessibility mode.

COTS Analytical Platform for Improper Payments

Solicitation Number: SS-BPD-11-0040
Agency: Department of the Treasury
Office: Bureau of the Public Debt (BPD)
Location: Bureau of the Fiscal Service
  • Print
:
SS-BPD-11-0040
:
Sources Sought
:
Added: Mar 04, 2011 4:50 pm
This "Sources Sought" posting is for market research purposes only, any solicitation resulting from this market research will be competed through the issuance of a separate Request for Quote at a later date. Your request to provide a demonstration in response to this posting will be reviewed and considered by the government, but note that not all requests may be granted. A representative sampling will be chosen and may be limited due to various reasons such as time constraints and the same software being presented by multiple re-sellers.

Date: March 21-22, 2011
Location: Embassy Suites, 900 10th Street NW, Washington, DC, 20001
Audience: Approximately 25 Government Personnel

Background
Through various Presidential and Office of Management and Budget (OMB) directives , Federal agencies have been directed to detect and prevent improper payments through a Do Not Pay List (DNPL). These directives require the establishment of a DNPL to serve as a source through which all agencies check the status of a potential contractor, grantee, or beneficiary by linking the agency to relevant eligibility databases, to the extent allowed by law.

The objective for this Vendor Day is to conduct market research to identify possible solutions, which will assist with eligibility determination in order to prevent an improper payment from being made to ineligible recipients. In the case where an improper payment is made, the solution should assist with detecting the payment, so that appropriate action can be taken.

Improper Payments Defined
An improper payment is any payment that should not have been made or that was made in an incorrect amount under statutory, contractual, administrative, or other legally applicable requirements. Incorrect amounts are overpayments and underpayments (including inappropriate denials of payment or service). An improper payment includes any payment that was made to an ineligible recipient or for an ineligible service, duplicate payments, payments for services not received, and payments that are for the incorrect amount. In addition, when an agency's review is unable to discern whether a payment was proper as a result of insufficient or lack of documentation, this payment must also be considered an error.


The term "payment" in this guidance means any payment (including a commitment for future payment, such as a loan guarantee) that is:


1. Derived from Federal funds or other Federal sources;
2. Ultimately reimbursed from Federal funds or resources; or
3. Made by a Federal agency, a Federal contractor, a governmental or other organization administering a Federal program or activity.


This includes Federal awards subject to the Single Audit Act (31 U.S.C. Chapter 75) that are expended by both recipients and sub-recipients.


High-Level Requirements
Vendor should have the capability to design and host a single Do Not Pay Portal, in which Federal agencies can quickly and efficiently access distributed databases, in order to verify eligibility information for various government programs.


Vendors should be able to quickly demonstrate an existing Commercial Off-the-Shelf (COTS) analytic platform, via either Software as a Service or a stand-alone system. These services or products must demonstrate the ability to detect and potentially prevent improper payments, by applying fuzzy logic, to compare specified criteria against data maintained in the distributed databases mentioned above.


These programs are exceedingly complex, maintaining large databases, and will require a solution that can conduct timely and accurate analysis. Examples of existing solutions/customers are required.


Since the requirements for this project are still being defined, the above mentioned product/service may require the vendor to create a database, on which to run the analysis. The database will need to pull data from various existing databases, while only duplicating data necessary to conduct the analysis. The data, which is pulled from the distributed databases, may be in a non-standard form, requiring the product to structure the data, prior to entering it into the database.


Vendor Day Specifics
Vendors should limit attendance to five personnel. Included in the vendor representatives should be enough technical expertise to provide a good overview of the product/service and to address technical concerns, as well as, compliance with the Federal Information Security Management Act (FISMA) and National Institute of Standards and Technology (NIST) guidelines.


Equipment that will be provided by the Vendor Day host (Bureau of the Public Debt) includes:

• Laptop computer with MS Office 2007.
• Projector.
• Screen.
• Internet connection.


Presenters will be responsible for operating the computer; and anything other than the equipment listed above will need to be provided by the presenters.


Demonstration Methods:
Live demonstrations of existing solutions are the only acceptable forms of presentation.


To Schedule a Demonstration
Please email psb3@bpd.treas.gov in response to this notice. Please be prepared to provide an organizational POC, so that once specific times and dates are available, that information can be relayed.

:
Avery 5F
200 Third Street
Parkersburg, West Virginia 26106-5312
United States
:
Embassy Suites
900 10th Street NW

Washington, District of Columbia 20001
United States
: