1 / 26

GSA ASSIST User Account Registration

GSA ASSIST User Account Registration. For GSA Employees: Changes in TOS, ITSS, GWAC MM coordinated with the Consolidated Registration Project Data Migration and other Data Information. April 15, 2014. Topics. TOS Changes ITSS Changes GWAC Changes

Download Presentation

GSA ASSIST User Account Registration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. GSA ASSIST User Account Registration • For GSA Employees: • Changes in TOS, ITSS, GWAC MM coordinated with the Consolidated Registration Project • Data Migration and other Data Information April 15, 2014

  2. Topics • TOS Changes • ITSS Changes • GWAC Changes • Data Migration and Other Data Information

  3. Changes in TOS • TOS Customer Document (PM function) • New method to select the customer (client) on the order • TOS Industry Partner Document (CS/CO function) • New selection method

  4. TOS Customer Document – Choose Agency (existing)

  5. TOS Customer Document - Select Agency and Client POCs (new) The new form requires selection of Agency and Bureau PLUS a Primary Client User

  6. Why is a Primary Client User Required? • To Support Future Functionality • The up-coming Central Invoice Service will have a role for the Primary Client User (and/or their alternates) to approve invoices. • This role necessitates identifying at least one client user per TOS order.

  7. How to work with this Change • Existing orders where Agency is already selected • In the near term: you do not need to do anything. Since the agency is already selected, it will be left as is. • For the next mod after ASSIST Registration is implemented: it will be necessary to select the Primary Client User and optionally, Alternate Client Users • New orders where Agency is not yet selected • You will be required to select the Agency / Bureau and the Primary Client User • The AASBS Helpdesk will be registering Client Users pre-deployment so that these people are selectable on your orders. • Post-deployment: New Client users may self-register, you may register them on their behalf, or the AASBS Helpdesk can help. • Note: there will be no functionality for TOS Client Users until the Central Invoice Service is deployed.

  8. How to use the new form Search for the user’s name. The user must be associated to an organization with the same agency and bureau code as selected above in order to show up in the search results.. Once you select the Agency and Bureau code, click on Lookup Primary Client User If you do not know the Client User name, use the View Account Profiles pagesin the My Profile section to find a useror contact the AASBS Helpdesk for assistance to identify the name.

  9. TOS Industry Partner Document- Select Industry Partner (existing)

  10. TOS Industry Partner Document- Select Industry Partner (new) Depending on the contractselected, you may need to select the Remittance Address.

  11. Changes in ITSS • ITSS Client Order Information (COI) • Territory selections • ITSS Award Document • Reseller Contract – reseller remittance information on the award • Teaming Agreement – teaming agreement company remittance information on the award

  12. ITSS COI • The Territory field will be populated with options associated with the selected Region for the order.

  13. ITSS Award Document • If the winning contractor utilizes a Reseller contract for their winning bid, the remittance information will reflect the Reseller contractor address on the Award Document. • If the winning contractor utilizes a Teaming Agreement contract for their winning bid, the remittance information will reflect the contract’s originating contractor remittance information.

  14. Changes in GWAC • GWAC Order Data form • CAF Payment Data form • Manage Peer Access form • Request Delegation form

  15. GWAC Order Data form changes • Order Data form • The Contract Number dropdown list will include the Company name next to the Contract Number • Reason for change: a Contract maybe associated to multiple companies in Reseller or Teaming Agreements.

  16. GWAC CAF Payment Data form changes • CAF Payment Data form • A new dropdown list for the contractor user to select their company. • Reason for change: a contractor may be associated to more than one company.

  17. GWAC Request Delegation form changesGWAC Manage Peer Access form changes • Request Delegation form / Manage Peer Access form • A new dropdown list for the agency user to select their organization. • Reason for change: an agency user may be associated to more than one organization.

  18. Data Migration and Other Data Information • Data will be migrated and consolidated from ITSS and TOS to the new ASSIST database • Post deployment data updates from source systems • SAM / CCR • eLibrary

  19. Data Information – Contractor Data (1 of 3) • With deployment: NBA (TOS) Contractor Company data and RBA (ITSS, GWAC, ITOMS) Contractor Company data will be migrated and consolidated by DUNS number, DUNS+4 and CCR / SAM data into the ASSIST database so that there is one Contractor Company record per DUNS & DUNS+4. • Associated contracts, orders, etc. will be linked to the new single company record. • In-process Award Documents not affected unless the SAM company name and address differ from the Company name and address on the Award Document, in which case an update to the award is needed. • Signed Award Documents are not affected.

  20. Data Information – Contractor Data (2 of 3) • With deployment: RBA (ITSS & GWAC) Contractor user accounts and NBA (TOS) Contractor user accounts will be migrated and consolidated to the ASSIST database. • Consolidation is done on perfect match of first name, last name and email address. If these three elements match, the system will automatically consolidate the separate user accounts into one. • User permissions, alternates, peers, associated company records, contracts, orders, action items, etc. will be linked to the new single user account. Specific names identified on in-process and signed Award Documents are not affected. • For Company data migrated from ITSS, the Company POC will be set to the person(s) currently set as editors for Company data.

  21. Data Information – Contractor Data (3 of 3) • With deployment: Email Notifications • All contractor users that had two or more user accounts that are consolidated to one will receive an automated email notification with their new user account name. • All contractor users will receive an email notification to reset their password in the ASSIST system. • Post-deployment: Contractor Company data will be updated nightly from the System for Award Management (SAM / CCR). • Company names will be replaced with the SAM company name based on a match on DUNS & DUNS+4 number.

  22. Data Information – Contract Data • With deployment: NBA (TOS) Contract data and RBA (ITSS, GWAC) Contract data will be migrated and consolidated by Contract Number into the ASSIST database. • Existing ITSS Contracts that are identified as Reseller or Teaming Agreement contracts are labeled as Reseller and Teaming Agreements in ASSIST. • Post-deployment: For contracts in eLibrary, Contract data will be updated nightly from eLibrary (FSS-19)

  23. Data Information – Client Data (1 of 2) • With deployment: NBA (TOS & OMIS) and RBA (ITSS) Agency and Bureau codes are migrated and consolidated into the ASSIST database. • With deployment: NBA (TOS) Client Organization and Client user data for active TOS orders will be loaded into ASSIST. • With deployment: RBA (ITSS & GWAC) Client user accounts will be migrated and consolidated to the ASSIST database. • Consolidation is done on perfect match of first name, last name and email address for Approved user accounts. If these three elements match, the system will automatically consolidate the separate user accounts into one. • User permissions, alternates (peers), associated organization records, orders, action items, etc. will be linked to the new single user account. In-process and signed Award Documents are not affected.

  24. Data Information – Client Data (2 of 2) • With deployment: Email Notifications • All RBA client users that had two or more user accounts that are consolidated to one will receive an automated email notification with their new user account name. • All RBA client users will receive an email notification to reset their password in the ASSIST system. • Note: NBA client users loaded into ASSIST Registration with deployment will not receive these email notifications.

  25. Data Information – GSA Employee Data • With deployment: RBA GSA user accounts and NBA GSA user accounts will be migrated and consolidated to the ASSIST database. • Consolidation is done on perfect match of first name, last name and email address. If these three elements match, the system will automatically consolidate the separate user accounts into one. • Exception for NBA DOI/NBC user accounts. These accounts remain separate and unchanged. • Usernames are updated to the ENT Username; login with your ENT password. • User permissions, orders, action items, etc. will be linked to the new single user account. In-process and signed Award Documents are not affected.

  26. Questions / ANSWERS

More Related