Technical assistance includes site set-up, training for CBP admin users, and troubleshooting system issues.

(3 - Customizable homepage) Would that be for the general application or is it for each registrant portfolio? Answer - General application for each event, not reach registrant. (4- # of Registrants) Is that the number of registrants the application can take or for each admin to have that number? Answer- 3,000 allowable registrants per event. (14 - Waitlist) Would that be a waitlist button for the registrant, or would it be an input field? Answer - Waitlist activation once 3,000 capacity is reached for a specific event. Waitlisted registrants auto-moved to confirmed list upon other cancellations. Admin team may also manually move someone out of a waitlist.

For this required registration portal, we do NOT require pay.gov since we won't be charging a fee for these events.

1. What is the approximate number of events anticipated annually? Answer - 100-200 2. Is there a need to support more than one event's registration simultaneously (with some overlapping dates)? Answer - Yes 3. Are the nature of services required identical for base year, option 1 and option 2? Answer - Yes 4. Will the government consider an 8 - 12 week on-ramp to allow fine tuning of various configurations/defaults, conduct training, allow the government sufficient time to test drive the solution, and eventually rollout the solution for full implementation? Answer - 2 weeks is the approximate time allotted for training, set-up, and testing. 5. How many "CBP/OTR administrator" accounts are required to set up events/set up registrations/run reports/etc.? Answer - 5-10 6. Is a mobile responsive solution (for use on devices such as smartphones and tablets) registration form necessary? Answer - No 7. Are any other event maintenance services required beyond event setup and management of registrations? Answer - Troubleshooting issues with system for admin users and registrants 8. Is there in incumbent? If yes, please provide name and value of current/previous contract. Answer - Currently using internal agency system with limited capabilities. 9. Can the government confirm format/length of proposal response? Answer - No Format or Length restrictions. Preferred that Technical proposals are attached in PDF format 10. Can the government clarify the reverse auction process with respect to submission of pricing? i.e. Should we submit pricing with the technical submission via Unison Marketplace? Will we then have the ability/option to re-submit pricing through Unison after the submission deadline? Answer - The pricing should be submitted using the Unison System. Seperately, you are required to attach a Technical quote(Non-Price proposal) in your submission to be considered for award. You will not be able to submit pricing or proposals, once the submission deadline closes. 11. What is the estimated average number of registrants per event? i.e. Is the 3000 number in the SOW a total for all events, or can any event have up to 3000 registrations? Answer - Each event varies and may host up to 3,000 participants. 12. Given this solution will contain government data, is it safe to assume this solution must be hosted on a cloud service provider with FedRAMP authorization? Answer - No. Our Office of Information and Technology will complete a vendor assessment with the selected vendor. 13. Would the government consider extending the submission deadline to June 16? Answer - No

1. Do you have a reporting system today? Yes – internal to CBP. Would you consider a proposal that leverages your enterprise tool for faster adoption? No, it will no longer be in use. 2. What sections within the home page is Customizable i.e. - The event details, logo & the contact information etc. for the event sponsors is the only information that varies ? Event details, logo, contact information, event webpage link, resource links may all vary per event. 3. In other words, the information collected for each event from the registrant is it static as specified in the requirement specs? It depends on the needs of the hosting office within CBP. I.e., they may want to know which registrants have previously participated in a CBP webinar. We would then need to add that as a new field for that particular event. 4. How many events have you conducted in the last year? 100 5. Would you be able to share few event forms to perform a high-level analysis ? Our event form only asks for name, company, email address, and entity which no longer suffices. We do not have a form to share. 5. Do you anticipate data migration from your internal systems into the new system? if yes, do you require the vendor to perform this or will it be performed by the admin No/No

1. Is the registration form open to public or is accessible only by the 3k users ? - 3,000 public users 2. Is the customization / logo for each event or for OTS Entity ? - Each event 3. What system do you currently use ? - Internal agency system 4. If you do use a system currently , what is the pain points faced ? - Uncustomizable 5. Do you anticipate the system to determine how many folks can register to an event ? - Yes 5a. What determines the capacity for the event, who is confirmed and who is put on a wait list ? - CBP host will determine capacity per event, not to exceed 3,000 registrants. Waitlist shall be activated upon reaching 3,000 registrants. 6. Will the solution need to be hosted in your private cloud or are you expecting the vendor to host it for you ? - Vendor-hosted 7. What is expected when an event registration is cancelled ? Does the system need to send a mass communication to attendees ? - CBP will notify registrants of the cancellation by exporting registration excel lists for the applicable event. 8. How many admin users do you anticipate ? - 5-10 admin users 9. Are you looking for the system to deduplicate redundant registration to avoid manual data cleaning exercise ? - Yes