Statement_of_Work_(SOW)_Attachment_A.pdf

Attachment A

Statement of Work (SOW)

Acquisition & Grants Office

Federal Procurement Data System – Next Generation: Automated Data

Validation Services

Background

As required by Federal Acquisition Regulation (FAR) 4.6, National Institute of Standards and

Technology (NIST) reports all procurement actions that are valued above the micro-purchase threshold to the Federal Procurement Data System – Next Generation (FPDS-NG). FPDS-NG is an automated system used to collect and report on federal procurement spending and serves as the U.S. Government’s single authoritative repository for federal procurement award data for all contracts valued over the micro-purchase threshold. FPDS-NG provides the following benefits:

Transparency and visibility into government contracting

Contracting information across the federal spectrum in real time, down to the contract action

Powerful business decision-making tool for the contracting community

Ability to analyze data so as to identify contract management and market trends

Serves as a foundation for standardizing contracting processes

Reinforces procurement-related policy changes by means of standardized data fields that are utilized across the federal enterprise

Reduces system redundancies and costs

Fulfillment of near-real time data requests by means of the self-service data retrieval capability

Data is available within 24 hours of award and can be viewed by congress, press, state government officials, IG & auditors, FOIA offices, GAO, etc.

The data that is available in FPDS-NG can be reviewed by the public via the outward facing Web site located at https://www.fpds.gov/fpdsng_cms/index.php/en/.

Scope of Work

As the U.S. Government’s official repository for acquisition-related data, it is imperative that the data contained in FPDS-NG is valid and accurate. The purpose of this requirement is procure automated data validation services (ADVS) & Competitive One-Bid Analysis that can identify suspected or known

FPDS-NG errors so as to ensure that the entered FPDS-NG data is valid and accurate. NIST also requires a strategic sourcing solution that will track contract usage and leakage of its strategically sourced vehicles. The Period of Performance shall be for one 12-month period starting with one option period.

https://www.fpds.gov/fpdsng_cms/index.php/en/

Requirements

Task 1 – Kickoff Meeting: By no later than 1 business day after award, the contractor shall provide a draft version of training/user materials for review. Within 5 business days of award, the Contractor shall meet with the assigned CO, Point of Contact (POC), and other departmental employees that will be involved with the implementation of the proposed and accepted ADVS solution. The purpose of this meeting is to ensure that all parties involved have a common understanding of the solution and decide on any of the associated attributes that can be tailored or configured. As may be necessary, the Contractor shall provide a demonstration of the proposed and accepted ADVS solution during the meeting.

Task 2 – Automated Data Validation: Within three business days of the award, the Contractor shall provide an ADVS solution that detects and reports known or suspected data errors or anomalies for all possible data fields within FPDS-NG. The solution shall be completed without interface to NIST’s procurement writing system, C.Suite. Within two business days of a FPDS-NG contract action report

(CAR) being finalized, the ADVS solution shall provide automated data alerts outlining the known or suspected data errors or anomalies to the individual who prepared the FPDS-NG CAR, which tends to be a contract specialist (CS), as well as the individual who last modified the FPDS-NG CAR, which is typically the assigned contracting officer (CO). The automated feedback alerts shall be intuitive and clearly identify the CAR number, the known or suspected data error or anomaly, and supporting rationale that provides insight into the reason(s) that the data is or appears to be in error. In order to reduce the likelihood of future errors, it is imperative that the supporting alerts provide clear and concise rationale, and include the details that are necessary to understand why the known or suspected error was detected.

For those identified data anomalies that are confirmed as being a “false-positive” error, the ADVS solution shall allow NIST to tag the error accordingly and ensure that the error is not registered again for that specific FPDS-NG CAR. Based on the organization of NIST’s acquisition workforce, the Contractor shall assume that NIST will have no more than three administrators/technical points of contact. Specific metrics include:

Automate the monitoring of FPDS-NG data quality checks for potential errors for all possible data fields

Provide automated feedback via email to the FPDS-NG data submitter in a timely fashion (within two business days of FPDS-NG CAR approval).

Promote supervisory oversight in a time sensitive manner through automated notifications and a dashboard.

Provide a means by which contracting officers can comment on or explain ostensible data quality problems

Provide a means by which NIST contracting officers and acquisition oversight personnel can introduce new data quality checks

Track data quality metrics/improvement over time

Task 3 – ADVS Operation: The Contractor shall operate the ADVS solution services and ensure that the data error checks are maintained in accordance with any changes to FPDS-NG, to include data check creation, enhancement, or deletion.

Task 4 – Competition Analysis: The purpose of this analysis is to decrease the number of competitively awarded contracts that received only one bid. Within three business days of the award, the Contractor shall provide a solution that detects and reports competitive one bids (one-bid) that are above the simplified acquisition threshold, are for base awards only, and are not orders/calls against IDVs within

FPDS-NG. Within two business days of an FPDS-NG contract action report (CAR) being approved matching the above metrics, the contractor shall provide automated data alerts via email notifying the CS or CO of the action being coded as a one-bid within FPDS-NG and provide the CS/CO with options for correction or confirmation of the CAR. The automated feedback alerts shall be intuitive and clearly identify the award number of the one-bid CAR. Specific metrics include:

Via a web-based interface, compare the rate of competitive one bids across bureaus, and via the

Department of Commerce as a whole

Distinguish between awards where more than one bid was expected versus not expected (the latter involving delivery orders and BPA calls against single award indefinite delivery vehicles)

Provide an alerting mechanism to contracting officials and supervisory personnel when a competed award receives one bid

Provide a data collection input form for contracting officials to complete regarding why a competitive one bid occurred

Graphically display via a web-based interface the aggregated result of the data collection input form, with drill down capability to display each individual form submitted by contracting officials regarding competitive one bids

Provide a list of potential errors in FPDS-NG reporting whereby a competitive one bid is incorrectly reported either due to an incorrect number of offers being reported, or an error in the competition coding

Provide a list of awards that were: 1) competitively awarded, 2) received one bid, and 3) are about to expire. The goal being to increase the number of offers on potential, re-competed awards

Track the competitive one bid rate over time

Task 5 – Strategic Sourcing: The contractor’s solution shall provide information in the analysis of strategic sourcing vehicles in accordance with this section. The purpose of this analysis is to increase the usage of NIST’s strategic sourcing vehicles and identify awards that are made outside of the vehicles.

The Government will provide information regarding the strategic sourcing contracts. Specific metrics include:

Via a web-based interface, compare the strategic sourcing utilization rate across bureaus, and against the Department of Commerce (department) as a whole

Compare the strategic sourcing leakage rate across bureaus, and via the department as a whole

Provide ad-hoc reporting capability to analyzing strategic sourcing metrics

Provide automated feedback to strategic sourcing vehicle managers regarding awards reported in

FPDS-NG that represent leakage (within two business days of FPDS-NG data entry).

Promote supervisory oversight regarding leakage in a time sensitive manner through automated notifications and a dashboard

Analyze strategic sourcing utilization metrics by: contracting officer business size determination, bureau, office, strategic sourcing vehicle, and award size

Provide a list of the top vendors associated with each strategic sourcing vehicle

Provide a list of vendors who have been terminated for cause or default, and are associated with a strategic sourcing vehicle

Provide an online, data input form to update strategic sourcing information, to include the PIIDs and PSC Codes tied to a vehicle

Synchronize the NIST strategic sourcing vehicle data (e.g. PIIDs) with FPDS-NG award data

Track the strategic sourcing utilization rate over time

Task 6 – Helpdesk Support Services: The Contractor shall provide helpdesk support services to NIST’s identified administrators/technical points of contact. The helpdesk support services shall cover all issues, regardless of assigned severity level, and be available from 8:30 am to 4:30pm EST, Monday through

Friday, less Federal Holidays. All helpdesk tickets shall be resolved within 2 business days.

Task 7 – Reporting: The proposed and accepted solutions above shall include reporting capabilities that allow for NIST’s leadership/decision makers to view and easily understand the number of known or suspected errors, one-bid, and strategic sourcing initiatives that occurred during a given time period. The reporting capabilities shall be flexible enough to provide a high-level, dashboard view that can be drilled down for more granular detail surrounding each of the known or suspected errors, one-bids, or strategic sourcing analysis, as well as the disposition of each requirement.

Task 8 – Training: The Contractor shall deliver a final version of the training material(s) and user manual(s) that is comprehensive and details how the ADVS, Competitive One-Bid, and Strategic

Sourcing solutions operate and the actions that are required by a recipient of a known or suspect data error alert, as well as the materials that are required of the administrators/technical points of contact. In addition, the Contractor shall provide quick and easy desk reference guides that synopsize the steps or actions required of a recipient and administrator/technical points of contact. NIST reserves the right to copy and distribute the training materials and quick reference guides for use within the government.

The Contractor shall provide up to four training sessions for NIST’s COs and CSs and two training sessions for the administrators/technical points of contact, schedule of training will be determined at the kickoff meeting.

Constraints

NIST will not host the Contractor’s ADVS, Competitive One-Bid, or Strategic Sourcing solutions

NIST is currently using Outlook for its email

The dashboard and reporting capabilities must be available by means of a web portal that complies with Google Chrome or Microsoft Internet Explorer.

Place of Performance

The place of performance will be at the contractor’s location, less any meetings/training sessions that may occur onsite at NIST’s facilities located in Gaithersburg, MD. However, if so elected by the Contractor, training may occur virtually.

Period of Performance

The period of performance shall be for a base year plus one option year. Period of performance shall begin on the date of purchase order award.