Multi Multi Multi

Come December 8th, a few notable changes will be implemented by the Federal Service Desk (FSD.gov):

  • Multifactor Authentication (MFA) will go into effect for those who have an account with FSD.gov. (Note, you do not need an account to receive help from FSD.gov)
  • FSD is renovating their entire site, therefore it will not only look different but also have a different “feel.”

If you already have a login.gov account that matches the email address associated with your FSD.gov account you are ready for MFA. If your login.gov email address is different from that associated with your FSD.gov account, simply update your FSD email address to match your login.gov email address. This allows FSD.gov to link the two accounts to your profile.

The FSD site renovation is an update implementing current U.S. Web Design System (USWDS) standards.  The updated site has the same functionality however the user experience should be much better. You may obtain login.gov assistance from the help section of login.gov.

Have questions concerning your accounts with FSD.gov and login.gov? Give us a call.

 

 

Update Update Update!

On 17 October 2020, the contract data reports function in FPDS.gov will retire. The reports function is moving to beta.SAM.gov. GSA highly recommends that all users become familiar with contract data reports in beta.SAM.gov as the move on 17 October is permanent. (GSA Interact, August 3, 2020)

Currently, reports are available in both places in an effort to ease into the change. GSA suggests that new users acclimate themselves through the following user guides and video:

  • Static Reports Reference Guide
  • Standard Reports Reference Guide
  • Ad Hoc Reports Reference Guide
  • Standard, Static, and Admin Reports Video Basic Ad Hoc Reports Video

Experienced users may find these resources helpful:

  • Contract Data Reports Before and After Transition from FPDS.gov to beta.SAM.gov
  • Quick Start Guide for Static, Standard, and Administrative Reports
  • Quick Start Guide for Ad Hoc Reports (ibid)

Feedback will be used to determine time frames and functionality, giving stakeholders a voice in beta.SAM.gov outcomes. One example is the search capability to assist in finding more applicable search results. Multiple words or phrases may be searched and beta.SAM.gov will prioritize the search by relevance. Use the feedback button in beta.SAM.gov to give GSA your thoughts on the reports function. (ibid)

Have questions about the new functionality of beta.SAM.gov? Give us a call.

GSA Extends Contract Data Reports Transition

GSA is extending the transition period for Contract Data reports in beta.SAM.gov. We don’t have a final transition date yet, although it’s expected later this year. This applies only to the reports function of FPDS.gov; everything else will remain as is. (GSA Interact, May 12, 2020)

GSA wants users to familiarize themselves with beta.SAM.gov while reports are available on both platforms. Furthermore, they want users to provide input on running reports. GSA is providing videos, FAQs, and reference guides to assist with the transition. (ibid)

GSA sees the following benefits to beta.SAM.gov:

  • Increased maximum number of rows returned from 30,000 to 150,000 rows in each report
  • Increased maximum number of years of reportable data from five years to 12 years
  • Additional data fields available for creating ad hoc reports
  • Tools for sharing ad hoc report structure with others, such as attributes and filters
  • Report Builder, a “wizard” that helps create new ad hoc reports
  • Intuitive tools to build, save, and share reports (ibid)

GSA used earlier feedback to determine the need for additional time before making the final transition to beta.SAM.gov. They will continue to take all feedback into consideration while transitioning. Any user can still use the feedback button to participate.

Trying to figure out if your reports will change and if you can retrieve them on the new platform? Give us a call.

 

beta.sam.gov Hiccup Hiccup

When FedBizOpps (FBO) migrated to beta.sam.gov, everyone expected a few hiccups. Now three months in, it’s fair to say government contractors have been experiencing more than just a few hiccups. GSA says the number of help desk calls they get is no more than they got with FBO. However, the frustration over beta.sam.gov runs deep.

Last week contractor discouragement came to a head when the Professional Services Council sent GSA a letter airing not only their complaints but also their concerns. The 22-page letter outlined the four areas of greatest concern:

  • Access Challenges;
  • Search Parameters;
  • Capability to receive contract information;
  • Difficulties in how the site displays information. (Federal News Network, February 17, 2020)

At EZGSA, we have found problems with data organization, standardization, and even saving information. GSA seems ready to add new capabilities next month, but should they? Many feel the backend structure should be fixed before the next phase, moving the Federal Procurement Data System-Next Generation (FPDS-NG) reporting capabilities to beta.sam.gov in March. (ibid)

Large companies are better able to handle the costs associated with down time or lost data. Small businesses that must  spend thousands of dollars on software, just to get what they got before the FBO migration, are at a great disadvantage.

Need help navigating beta.sam.gov? We will do our best to help and take away some of the frustration. Give us a call.

You Are an Unique Entity!

You’ve heard (ad nauseum, probably) about replacing your DUNS number with the unique entity identifier (UEI) by  December 2020. Contractors will request and be assigned the new identifiers through SAM.gov. (To learn more about the transition, click here.) (GSA Interact, December 10, 2019)

Contractor award data, including UEI data, interfaces with many systems outside of the government interface. To assist contractors as well as other agencies, GSA published a first and second set of UEI/EVS specifications. For instance, Group 1 includes:

  • beta.SAM Entity Management. APE has updated schemas for a second version of the API. The second version allows  systems to pull information automatically. Differences between versions are marked as v1 (current version) or v2 (future version). Specs may be found here.
  • New EVS and UEI changes will not be updated to SAM Entity Management Web Services. Users of this web service should migrate to beta.SAM Entity Management API to retrieve UEI and new EVS information. 
  • The SAM public RESTful API will not be updated to incorporate UEI or new EVS changes. Users of RESTful API should migrate to beta.SAM Entity Management API to retrieve new EVS and UEI information.

Group 2 includes:

  • The beta.SAM Exclusions. API has updated schemas for version 2, which allows interfacing systems to pull information about the exclusions automatically.  Differences between the versions are marked as v1 for the current version and v2 for the future version. Specs may be found here.
  • The SAM Exclusions Search Web Services will not be updated to incorporate UEI or new EVS changes. Users of this web service should move to the beta.SAM Exclusions API in order to retrieve UEI and new EVS information concerning exclusions via interface.

The public will continue to receive UEI/EVS specifications as they are updated. IAE will release its testing plan by 30 December 2019. Additionally, IAE will complete the issuance of updated technical specifications interfacing systems. Contractors should start developing plans to allow for the interface changes and begin development for testing with IAE. (ibid)

Users with questions specific to interface testing should contact newsamtesting@gsa.gov. Users with questions specific to the SAM-generated UEI or entity validation services should contact entityvalidation@gsa.gov. (ibid)