IAE Technical and Interface Community February 21, 2019 10:00 AM (ET)

1. Adobe Connect: https://meet.gsa.gov/iaetic/ Use Agency/Company, First and Last Name format (e.g., GSA – Katherine Rollins) US (Toll): 1-719-325-2013 US (Toll Free): 1-866-928-2008 Participant Code: 353877 IAE Technical and Interface Community February 21, 2019 10:00 AM (ET) PLEASE MUTE YOUR PHONE UNLESS SPEAKING Do not use the “hold” feature on your phone

2. AGENDA Legacy Systems • SAM Updates Modernization • Updates to Modernization Timelines • WDOL • FBO • Login.gov • beta.SAM.gov Interface Authentication • Modernization of Contract Data and Entity Data Interfaces • Entity Extracts • Entity SOAP Services and Public API • Contract Data SOAP Services • Modernized Contract Opportunities Services • PSC API • FH API Closing • TIC Member Open Discussion & Closing • Opportunities SOAP Services Office Hours

3. INTRODUCTIONS Today’s Presenters • Salomeh Ghorbani, Moderator and Test/Transition Manager • Marci Eaton - SAM.gov Product Owner • Zack Sionakides, Interface and Extract Product Owner

4. Legacy: System for Award Management Update Marci Eaton

5. SAM IE11 VALIDATION MAY REQUIRE AGENCY CHANGES • SAM implemented a validation for Internet Explorer version 10 (IE10) and below as of 01/12/19. • Based on FSD tickets, we know that VA, DOJ, and DLA are affected. • SAM has lifted the validation until 04/01/19, to allow Agencies to implement necessary technical changes. Agency Actions: • If your Agency web services have experienced undiagnosed SAM connectivity issues between January 12th - February 4th, you may be affected by this change. • This IE validation affects all HTTP traffic (all visitors to the SAM.gov website and anyone who hits the web services). • If your Agency downloads data extracts via the SAM website, it affects you. • If your Agency uses SFTP, it does not affect you. • Know that SAM will restrict traffic originating from Internet Explorer version 10 (IE10) and below effective April 1, 2019. • Review your Agency web service client configuration. • Ensure IE11compatibility by March 31, 2019.

6. SAM IMPLEMENTATION OF REPS & CERTS FOR FINANCIAL ASSISTANCE REGISTRANTS CREATES NEW EXPECTED DATA ELEMENT IN EXTRACTS & INTERFACES Effective: 02/02/19 Impacts to Web Service - Extracts - Interface: • Added a data element to the Entity Management Web Service to reflect the new Financial Assistance Reps & Certs requirement. • The new element will be within the <repsAndCerts> section of the Response Schema and tagged as <financialAssistanceCertifications>. • All non-federal registrants in SAM will be required to provide a Yes/No response and certify to the new Financial Assistance Reps & Certs as part of their registration.

7. SAM Release (02/01/19) Major Release Items: • Implement Read Only Certs & Reps for Federal Assistance Community • Email notifications to Financial Assistance only registrants to alert them of change • Implement edits based on FAR Case 2015-005: System for Award Management Registration • Modify SAM Public Data Sharing via Search, API, Web Services, and Extracts • Modify SAM Public Data Sharing via API • Modify SAM Public Data Sharing via Search (does not apply to “Check Status”) • Modify SAM Public Data Sharing via Web Service • Only Post Extracts Monthly • Restore Advanced Search Entity functionality - TIN and DODAAC Fields are Not Displaying for FOUO Users • Update DUNS Info Page - Congressional District Error Message text • Restore functionality - Incorrectly clearing out Mandatory POCs Country and Phone Number when user deletes optional POCs • System Deactivate/Reactivate Confirmation page does not refresh • Restore red asterisks on the POC page zip code fields (currently missing) • Improve Hierarchy Registration Request Page Navigation

8. Questions/Comments SAM UPDATE

9. Modernization: Updates to Modernization Timelines Salomeh Ghorbani

10. Revisions to Modernization timelines: Wage Determinations (WDOL): Opportunities (FBO):

11. Login.gov GSA has decided to utilize login.gov for beta.SAM.gov: • Beta.SAM.gov will migrate first. • FBO users will go directly to login.gov at migration. • If entities and government users have an account in SAM.gov they will not need to create a new one. New Improved Sign-In Feature • Improved user experience • No OTP for government users with CAC/PIV • SMS only for security code • Easier initial account setup process

12. Modernization: System API Access Into beta.SAM.gov Zack Sionakides

13. API Access • Initial version 1.0 Opportunities REST APIs, Contract Data, and Entity Data will authenticate via API key and authorize actions based on user roles • v1.0 will be available as part of the FBO decommissioning package of data services • A version 2.0 will be developed that uses OAUTH2 standard to authorize actions • The end user will be authorizing their system account to act on their behalf within beta.SAM.gov • Versions 1.0 and 2.0 will be available concurrently to allow a migration time from both REST APIs v1.0 and SOAP services to REST APIs v2.0

14. Modernization: Modernization of Contract Data and Entity Data Interfaces in Beta.SAM.gov Zack Sionakides

15. Interface Integration • Legacy FPDS and Legacy SAM interfaces are being integrated and modernized into beta.SAM.gov as part of overall modernization • As with FBO, we seek to minimize changes and impacts on interfacing systems where prudent, however changes will occur • IAE is currently working on modernized specifications for each legacy FPDS and SAM interface that will be distributed shortly • Distribution will occur over Open GSA • Milestone Events: • Design Technical Architecture - Complete • Publish Technical Specification Architecture and Draft Connection Information - In Progress • Endpoints and Detailed Authentication Information - Q3/Q4 FY19

16. Contract Data (FPDS) Interface Modernization

17. Atom Feed Survey Question For any consumer of the atom feed, which version are you using (1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.5.0)? Please respond to the POLL in the meet.gsa.gov window.

18. Contract Data SOAP Services Architecture • Requests come through beta.SAM.gov • Once authenticated, the requests are re-directed to legacy FPDS SOAP services

19. Contract Data SOAP Services Authentication/Authorization • Initial authentication conducted in beta.SAM.gov • Legacy FPDS conducts identity management and role management through beta.SAM.gov services • All user profiles and roles must be present in beta.SAM.gov for a successful transaction. • Roles will be migrated, but they must be claimed by the user in beta.SAM.gov to work. Roles are not migrated sans users claiming them.

20. Contract Data SOAP Services Endpoints The following are the prospective endpoints for services in beta.SAM.gov. They are not available at this time for testing. • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/Award • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/IDV • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/OtherTransactionAward • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/OtherTransactionIDV • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/ContractSummary • https://www.api.sam.gov/prod/FPDS/BusinessServices/DataCollection/contracts/1.5/Contract

21. Entity/Exclusions Interface Modernization

22. Entity / Exclusions API • Legacy SAM SOAP services and public API for entities and exclusions are being consolidated into modernized REST API and will be deprecated at legacy SAM retirement. • API access and responses will be role based (Public, FOUO, Sensitive) • Schemas will largely include data elements that exist in both the legacy SOAP service and public API. In process of designing new schemas • Please provide and comments or suggestions on data formats, request parameters, or schema changes to newsamtesting@gsa.gov

23. Entity / Exclusions Extract Architecture • Requests come through beta.SAM.gov via UI or API • Once authenticated, the requests allow access to the S3 bucket to retrieve the file

24. Modernization: Modernized Contract Opportunities Data Services Zack Sionakides

25. FBO System Interfaces Transition and Decommissioning

26. Opportunities REST APIs Build Summary

27. Opportunities SOAP Services Build Summary

28. Opportunities SOAP Services Changes (1 of 2) • Global schema updates • Interfacing systems will need to submit the FH Organization ID or Office Code (AAC) within their web service requests to establish roles for the submitter • Legacy schemas will have this update for all applicable operations • Deprecating Fair Opps and Foreign Government operation • All Fair Opps notices will need to use submitJA operation • IVL will be auto-populated as "no" and COs will need to go in to beta.SAM.gov to populate manually. No interfacing system changes needed. • Map all POC details incoming data to POC name regardless of content. POC email mandatory in web services. • Make solicitation ID mandatory on applicable notice types in alignment with front-end.

29. Opportunities SOAP Services Changes (2 of 2) If archive date provided, beta.SAM.gov will use that date. If blank, then it will populate as ‘auto 30’ or ‘auto 15’ based on solicitation type. Additional reporting will default to false on web services if submitted blank Response date will have default response date added in logic when unarchiving (auto 30 from posted date). COs will need to alter on the front end. Archived or unarchived operations will have a default reason entered as “No Reason Provided”. COs will need to alter on the front end. 'DocumentFile Complex Type Definition' will add two non-required fields: 'export_controlled' 'explicit_access' Both with values true or false

30. Modernization: PSC API Zack Sionakides

31. PSC API Update • PSC API v1 and v2 are currently available in beta.SAM.gov production environment • API v1 contains all current PSC information and hierarchy of groups • PSC API v2 adds category alignment • PSC API is public and only requires an API key to access • System accounts will need to go through the application process to obtain a system account API key

32. Modernization: Federal Hierarchy API Zack Sionakides

33. FH API Update • FOUO API version includes office information. Only available to government users. • Contains contracting, funding, and grants office data. All other office types are currently unavailable and are filtered out. • Available in production (beta.SAM.gov). • System accounts must go through application process with security to obtain an API key for their system account. • System account applicants will need to request FH FOUO access. • No individual access will be granted to the FH FOUO API • Public API in alpha environment. Does not contain office information. • Open to anyone with an API key.

34. Questions/Comments Interface Modernization

35. Office Hours: Contract Opportunities SOAP Services Dev Team

36. Office Hours: Opportunities SOAP Services • Please submit questions into the chat or raise your hand

37. Next Meeting May 2019 To Get Involved: https://interact.gsa.gov/group/integrated-award-environment-iae-industry-community For Developers to Stay Involved: http://gsa.github.io/openIAE