Performance Work Statement_06_29_2023.docx

COTS Data Quality Subscription RFQ No 47HAA023Q0089

GENERAL SERVICES ADMINISTRATION (GSA)

OFFICE OF ADMINISTRATIVE SERVICES (OAS)

OFFICE OF INTERNAL ACQUISITION (OIA)

Performance Work Statement (PWS) Rev.01 (06/20/2023) Solicitation Id: 47HAA023Q0089

Name of Requirement: Commercial off-the-Shelf (COTS) Data Quality Subscription

Client: FAS - Federal Acquisition Service (Q), and PBS - Public Building Service (P)

Acquisition: This Solicitation is herein competitively issued under the Open Market:

NAICS Code: 541611 Administrative Management and General Management Consulting Services

Contract Type: Firm-Fixed Price contract

Table of Contents

1.0 GENERAL

1.1 Background

Collecting and publicizing data about Government procurements provides public transparency about federal spending. The ability to look at all contract awards across many agencies is a key component in establishing trust in our Government and facilitates:

· Strategic sourcing and creating efficiencies; and,

· Improving government-wide management of its contract dollars.

Federal Procurement Data System (FPDS) is the single authoritative repository of federal acquisition data. Congress, the press, state government officials, Inspector Generals & auditors, FOIA offices, the Government Accountability Office, and many other interested parties rely on the accuracy of FPDS.

· FPDS is a searchable repository of millions of federal contract actions.

· FPDS covers over 180 data points on federal contracts based on contract data entered at the agency level.

· FPDS data will be increasingly used by contractors, our elected officials, media, public interest groups, citizens, etc. Accurate data promotes effectiveness, efficiency and credibility of the acquisition process with all stakeholders.

Performance of the services specified herein will drive greater accuracy of the General Services Administration’s (GSA) data residing in FPDS.

1.2 Scope

GSA requires a contractor to provide a customized site hosted on their website that maintains currency with the FPDS ATOM (public data) feed, SAM Application Programming Interface (API) feeds, and the Federal Acquisition Regulations (FAR) and provides:

· Reporting capabilities for up to 3,000 individual user accounts with customization of dashboards and reports based on GSA’s organizational structure.

· Data checks/validations of FPDS transactions, using primarily FAR-based logic and validation rules, and creation of associated dashboards and reports for the data checks/validations;

· Individually targeted emails to the data submitter or GSA-designated POC alerting them of potential data check/validation issues on each submitted FPDS action;

· On-demand requests for reports of contractor responsibility.

1.3 Objective

Provide a website for GSA users to find FPDS transactions flagged for FAR, FPDS data element dictionary, or other logic based possible errors. Additionally, provide a means for contracting officers (COs) to quickly gather the information necessary for them to make a contractor responsibility determination.

1.4 Applicable Documents

1.4.1 Compliance Documents

The following documents provide specifications, standards, or guidelines that must be complied with in order to meet the requirements of this contract:

· Provided website, reports, and messaging must meet current ICT Accessibility 508 Standards. Reference https://www.section508.gov/ for further development support.

1.4.2 Reference Documents

The following documents may be helpful to the Contractor in performing the work described in this document:

· FPDS ATOM Feed FAQ (https://www.fpds.gov/wiki/index.php/ATOM_Feed_FAQ)

· SAM API Overview (https://open.gsa.gov/api)

· FPDS Data Element Dictionary (https://www.fpds.gov/downloads/Version_1.5_specs/FPDS_DataDictionary_V1.5.pdf)

· FAR (https://www.acquisition.gov/browse/index/far)

· For Verification and Validation in 3.1.4:

· FAR 4.604(a) (https://www.acquisition.gov/far/4.604)

· GSAM 504.604 (https://www.acquisition.gov/gsam/part-504#GSAM_504_604)

· ‘Exhibit A - V&V Review Score Sheet.xlsx’ is the GSA export format for the Verification and Validation.

2.0 CONTRACT TYPE

The Government will award a Firm-Fixed Price contract.

3.0 SPECIFIC REQUIREMENTS/TASKS

Submitted with the quote, the offeror shall submit a project roll-out plan and past performance information (requirements detailed in 5.0 Deliverables Schedule).

3.1 CLIN001 & CLIN002 - Website with data checks and reporting

· The contractor shall provide on its website a customized site for the GSA with customized dashboards and report capabilities to support up to 3,000 individual users. Through the website the contractor must provide:

· 3.1.1 - Data checks/validations that identify potential data errors or inconsistencies using FPDS and SAM data elements;

· These are not data type/format checks, but business rules constructed based on FAR-based logic, FPDS Data Dictionary definitions, or logical validation rules;

· Contractor provided website and data checks must remain current daily with the FPDS public data feed, SAM public data feed, and the FAR;

· Include FPDS data for all transactions where contractingOfficeAgencyID (FPDS API field):

· CLIN 001: 4730, 4732, 4735, 4775

· CLIN 002: 4740

· Process for reporting exceptions to data checks/validations flags that are reviewed by GSA personnel and, if accepted, marked as an approved exception;

· 3.1.2 - Contractor dashboard/reports available through website must at a minimum:

· be filterable by GSA’s organizational structure, with performance for all of GSA, for each of the 47XX Agency IDs, GSA-provided contractingOfficeID (FPDS API field) groupings, and by individual contractingOfficeID. GSA-provided groupings may change during the life of the contract;

· Identify the FPDS Procurement Instrument Identifier (PIID), Modification Number, Reference PIID for individual flagged transactions;

· Include summary view with counts of FPDS transactions flagged by each data check, percent of total transactions, and counts by status (e.g. corrected, not corrected, exception status) of flags.

· Separate monitoring, reporting, and dashboard for DATA Act-specific elements;

· 3.1.3 - Automated notifications of possible data errors or inconsistencies;

· Individually targeted emails to

· the Contracting Officer (CO) or FPDS data submitter alerting them of potential data check/validation issues on submitted FPDS actions;

· office POCs, listing all the potential data check/validation issues on submitted FPDS actions for their office code(s);

· GSA will set the email schedule/volume, which may differ by contractingOfficeID.

· 3.1.4 - Contractor must provide a website section for Verification and Validation (V&V) of FPDS transaction review in accordance with FAR 4.604(a) and GSAM 504.604. This must include at a minimum:

· Load GSA supplied list of transactions for review by PIID, Modification Number, Reference PIID (if applicable), and GSA reviewer

· Contractor must provide web based forms for review of each transaction that

· shows FPDS values for twenty-five (25) OMB required fields and up to ten (10) additional FPDS fields at the request of GSA that may change for each V&V review cycle;

· allows entry of correct value if FPDS is incorrect and a comment field for any explanation;

· fields that allow reviewer to enter reviewer and contracting officer email addresses

· Summary of overall response rate and accuracy rate by field;

· Option to export report to Microsoft Excel that matches formatting of provided ‘Exhibit A - V&V Review Score Sheet.xlsx’;

· All fields found to be incorrect must be included by the contractor in data check automated notifications (3.1.3).

· 3.1.5 - Contractor Engagement and Communications

· Contractor shall maintain the website, dashboards, and all contractor supplied tools.

· Contractor shall provide live technical support via phone and email during normal business hours.

· Live user training sessions (that are recorded and provided to GSA) at least quarterly unless waived by GSA.

· Contractor shall run subscription start-up meetings:

· Initial call with GSA Contracting Officer’s Representative (COR) for introduction, review the requirements, go-live schedule, and schedule initial training sessions.

· Go-live meeting with GSA COR when the site is operational for orientation and review.

· Introductory training with Data Quality POC group. Review site access, data quality checks and reports, and contractor responsibility report tool.

· Follow-up meeting with Data Quality POC group to answer questions from initial report reviews.

· All mass-communications to GSA users from the contractor shall be reviewed and approved/rejected by GSA COR prior to issuing. This includes but is not limited to:

· Introductory and new user credential messaging

· Added/updated service offerings

· User surveying

3.2 CLIN 003 - Contractor Responsibility Report - FAS

· 3.2.1 - Contractor shall provide contractor responsibility report creation on demand by GSA users.

· At a minimum data for user submitted Unique Identity ID (UEI) should be gathered from SAM, FPDS, VetBiz, and GSA eLibrary.

· Information from SAM should be pulled via API at the time of request.

· All other data should have been updated with the latest information within the last 48 hours.

· At a minimum the following information shall be included:

· Excluded Parties Listed System (EPLS)

· Debt subject to offset

· SAM and FPDS contract terminations

· Self certified business types and certified business types by SBA and VetBiz

· Small business representations by NAICS code

· Buy American Certificates and Trade Agreements Certificates

· All Reps and Certs information from SAM

· Contractor contact information from SAM

· Contractor Commercial and Government Entity (CAGE) Information

· Users shall be able to submit at least one (1) and at least as many as fifty (50) UEIs for reports at a time.

· Single UEI request reports shall either download from the website or be delivered to the user via email within five (5) minutes on average. Multiple UEI requests should be completed within fifteen (15) minutes.

· Up to 500 users. GSA will provide a list of the users who will need the ability to request reports and their Contracting Office ID (e.g. 47Qxxx - aligns with FPDS API Field contractingOfficeID).

3.3 Optional CLIN 004 - Contractor Responsibility Report - PBS

· 3.3.1 - Contractor shall provide contractor responsibility report creation on demand by GSA users.

· At a minimum data for user submitted Unique Identity ID (UEI) should be gathered from SAM, FPDS, VetBiz, and GSA eLibrary.

· Information from SAM should be pulled via API at the time of request.

· All other data should have been updated with the latest information within the last 48 hours.

· At a minimum the following information shall be included:

· Excluded Parties Listed System (EPLS)

· Debt subject to offset

· SAM and FPDS contract terminations

· Self certified business types and certified business types by SBA and VetBiz

· Small business representations by NAICS code

· Buy American Certificates and Trade Agreements Certificates

· All Reps and Certs information from SAM

· Contractor contact information from SAM

· Contractor Commercial and Government Entity (CAGE) Information

· Users shall be able to submit at least one (1) and at least as many as fifty (50) UEIs for reports at a time.

· Single UEI request reports shall either download from the website or be delivered to the user via email within five (5) minutes on average. Multiple UEI requests should be completed within fifteen (15) minutes.

· Up to 400 users. GSA will provide a list of the users who will need the ability to request reports and their Contracting Office ID (e.g. 47Pxxx - aligns with FPDS API Field contractingOfficeID).

3.4 Optional CLIN 005 - Option for on demand reports, additional email alerts, or data collection forms.

· 3.4.1 - Contractor shall accept at GSA’s request up to ten (10) new reports, operational adjustments to existing reports, dashboards, new email alert automations, or web based forms to be produced an option year.

· Any new request will use data from FPDS ATOM Feed or SAM API.

· GSA will provide a PWS for each request of data segmentation, and calculation methods or business rules as needed.

· This CLIN is an option for years 2-5 of the contract to provide GSA the ability to have the contractor make adjustments to better meet business needs. GSA may choose to execute this option in all, some, or none of those years.

3.5 Optional CLIN 006 - Automated FPDS Transaction correction.

· 3.5.1 - The contractor shall correct data errors in FPDS on GSA transactions.

· Contractor shall have an automated email to FPDS transaction CO’s allowing them to opt-in to the correction.

· Once the FPDS transaction CO has opted into the changes, the contractor shall either manually or through an automated process make all the updates.

· These CLINs are options for years 2-5 of the contract. GSA may choose to execute either of these options in all, some, or none of those years.

· Include FPDS data for all transactions where contractingOfficeAgencyID (FPDS API field):

· CLIN 006: 4730, 4732, 4735, 4775

3.6 Optional CLIN 007 - Dun & Bradstreet financial information added to Contractor Responsibility Report

· 3.6.1 - The contractor shall procure a subscription to Dun & Bradstreet financial data and add to reporting.

· Add summary results to the Contractor Responsibility Report

· Create a filterable dashboard available through site in 3.1.

· Data fields and summaries needs requirements will be developed in partnership with GSA.

4.0 PERFORMANCE REQUIREMENTS SUMMARY

(The Service required—usually a shall statement)

Method of Surveillance

3.1.2 3.4.1

3.1.3 3.4.1

3.1.5 3.6.1

3.2.1 3.3.1 3.6.1

The contractor delivered reports inline with the deliverables schedule for 3.2.1

No more than one user reported >30 min delay a month (excluding contractor reported issue of downtime with data source or planned outage)

5.0 DELIVERABLES SCHEDULE

· an understanding of this PWS;

· their ability to produce a solution;

· an estimated schedule for development, testing, access, and training per the Specific Requirements/Tasks and this Deliverables Schedule of this RFQ for CLINs 001-003.

· Solutions can be for federal, state, local, or private sector customers.

· Recent is defined as an active contract providing service within the last three (3) years. Past performance must be recent and relevant to be considered.

For each offeror shall provide:

1. Name of the project;

2. Agency/company name receiving services;

3. Detailed description of the project;

4. Project start and completion dates;

5. An explanation of Program Management techniques and the Quality Control measures that were used to meet the customers needs.

6. Name, title, address, phone number, and email address for customer who can attest to the services provided.

· An outline of developments completed in the previous month.

· An outline of changes/adjustments during the next reporting period;

· A discussion of any problems encountered or anticipated that might affect site availability or report requests;

· Any other relevant information, including an analysis and explanation of personnel or budget issues;

· Monthly summary in Section 5.0 Deliverables for 3.1.1 / 3.2.1.

3.1.1 3.2.1 3.3.1

Users shall at a minimum be able to filter flagged transactions and find summary counts by data check/validation for the current fiscal year. Additional fiscal years and reporting may be deployed after thirty days.

N/A

--provide an initial sample within first thirty (30) calendar days of contract;

-- At GSA request (as often as monthly) load transaction list and data for each review within five (5) business days of receipt;

-- add additional fields at request of GSA within three (3) business days of notification.

Once 45-120 calendar days into contract for follow-up and questions

COR will propose a date for the second session based on GSA testing and adoption.

3.2.1 3.3.1

Regular use is upon user request and shall be live within thirty (30) calendar days of contract award.

Regular requests email to or available via download by requester

Regular use is upon user request and shall be live within thirty (30) calendar days of summary approval.

Regular requests email to or available via download by requester

6.0 INSPECTION AND ACCEPTANCE

The COR for this contract is a Government official who has been delegated specific technical, functional and oversight responsibilities for this contract. 5.0 Deliverables Schedule and acceptance of all work performed, reports and other deliverables will be performed by the COR.

6.1 Deliverable General Acceptance Criteria:

General quality measures, as set forth below, will be applied to each work product received from the contractor under this PWS:

● Accuracy ‐ Work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.

● Clarity ‐ Work products shall be clear and concise. Any/All diagrams shall be easy to understand, relevant to the supporting narrative, and 508 compliant.

● Consistency to Requirements – All work products must satisfy the requirements of this PWS and resultant contract.

● File Editing ‐ All downloaded file text shall be editable by the Government.

● Timelines ‐ Work Products shall be submitted on or before the due date specified in this PWS or submitted in accordance with a later scheduled date determined by the Government.

● Adherence to the Performance Based PWS – How the submitted deliverables achieve the goals and expected outcomes as delineated in this PWS.

6.1.1 Deliverable Quality Assurance:

The COR will review, for completeness, preliminary or draft documentation that the Contractor submits, and may return it to the Contractor for correction. Absence of any comments by the COR will not relieve the Contractor of the responsibility for complying with the requirements of this PWS. Final approval and acceptance of documentation required herein shall be by letter of approval and acceptance by the COR. The Contractor shall not construct any letter of acknowledgment of receipt material as a waiver of review, or as an acknowledgment that the material is in conformance with this PWS. Any approval given during preparation of the documentation, or approval for shipment shall not guarantee the final acceptance of the completed documentation. All deliverables prepared by the contractor during the course of this contract are the property of the Government.

6.1.2 Deliverable Review:

The Government will have a maximum of seven (7) working days from the day the draft deliverable is received to review the document, provide comments back to the contractor, approve or disapprove the deliverable(s). The contractor shall also have a maximum of five (5) working days from the day comments are received to incorporate all changes and submit the final deliverable to the Government. All days identified below are intended to be workdays unless otherwise specified.

6.2 Ad-hoc Meetings

During the course of the project, it is anticipated that project management shall be accomplished through email, phone conversations and formal-review briefings. In order to fulfill the objectives, communication should be a two-way exchange of relevant information. The contractor shall view the interaction as a collaborative process and have an assigned PM for this contract.

7.0 PERIOD OF PERFORMANCE

The period of performance for this contract is a 12-months base period with 4 one-year option periods.

8.0 PLACE OF PERFORMANCE

The work to be performed under this contract will be performed virtually. There is no expectation for travel or on-site training.

9.0 GOVERNMENT FURNISHED PROPERTY / INFORMATION

9.1 Government Furnished Property (GFP)

None

9.2 Government Furnished Information (GFI)

FPDS Users Report from SAM will be shared after award. This is an administrator report that will help match transactions to COs when a transaction in FPDS is submitted by an administrative account. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination and destroy at close of the contract.

10.0 OTHER APPLICABLE CONDITIONS

10.1 Security

If CLIN 006 is executed, the Contractor’s personnel who will be accessing FPDS manually or executing a robotic process in the system will be required to hold Tier 2S clearances. GSA will sponsor and provide the paperwork and process if that is necessary. The contractor will be responsible to track all actions and for any errors they create in the system.

11.0 GOVERNMENT POINT OF CONTACT

GSA Contracting Officer (Primary POC):

Bonnie Impastato, bonnie.impastato@gsa.gov, 202-510-3328

GSA Contracting Officer Representative (COR):

Aaron Wilson, aaron.wilson@gsa.gov, 414-312-2489

GSA Alternate Contracting Officer Representative (ACOR):

Tihara Williams, tihara.williams@gsa.gov, 404-291-4322 image1.png