ITN 22-23-33 Round 1 Q and As.pdf

PDF 104 KB Posted

Attached to
General Tax Administration eServices System
Solicitation number
ITN-04686
Issued by
Leon County, Florida

About this file

The document is an Invitation to Negotiate (ITN) issued by the Florida Department of Revenue (FDOR) for a General Tax Administration eServices System. The FDOR is seeking a contractor with experience in developing, implementing, hosting, and maintaining an eServices system that allows users to file and pay multiple taxes, fees, and perform account updates. The new system will replace the FDOR's existing eServices contract. The ITN provides details on the system requirements, including user concurrency, data validation, prepopulation of user data, and search functionality. The anticipated contract start date will be negotiated with the selected vendor.

The ITN does not specify any pricing terms, set-asides, or funding requirements. It does indicate that the FDOR's current eServices vendor is eligible to bid on this opportunity. The ITN also includes two rounds of questions and answers, as well as two addenda, providing clarification on various aspects of the solicitation.

View the file

Other files

File Type Posted
ITN 22-23-33 Addendum 2.pdf PDF
ITN 22-23-33 Addendum 1.pdf PDF
ITN 22-23-33 Round 2 Q and As.pdf PDF
DOR ITN 22-23-33 FINAL.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ITN # 22/23‐33 General Tax Administration eServices System Round 1 Questions and Answers

# QUESTION

Applicable to which section?

(Solicitation Page Number and Paragraph)

DEPARTMENT's RESPONSE/ANSWER

Is there any middleware system being used to integrate eServices and SAP Accounting system and can Department provide the current system landscape including integration points with eServices? General

There is no middleware. All integrations are conducted via file transfers.

Is there Federal Data involved in features dealing with eServices? General There is no Federal Tax Information.

Approximately how many users would be accessing this System concurrently during peak period/load? General

Up to 15,000 concurrent users could be expected during peak usage.

Are there any restrictions to store/replicate data in eServices? Ex: Tax payer information, Tax returns information General

There are restrictions listed in section 6.4 Hosting.

Will the new eServices portal be utilized for submission of all the types of forms listed on Florida revenue website?

(https://floridarevenue.com/taxes/eservices/Pages/ filepay.aspx)? 6.3.1

No. Required tax forms for the new eServices portal can be found in the procurement library.

Does current eServices utilize backend for Tax return calculations or calculations are performed in eServices before submitting data to backend? 6.3.2

Calculations are performed in eServices before submitting data to backend.

ITIN 6.3.2 ‐ Point 9 refers to the ability to link single user ID with multiple accounts/users and alternate log on credentials. It is typical to have one user ID manage multiple business accounts but it is uncommon to have one user manage other users. Is this referring to delegation functionality. Can this be described in more detail with example use cases? 6.3.2

Updated 6.3.2 #9 to "Have the ability to link a single user ID to multiple tax accounts, as a taxpayer, or to multiple entities' tax accounts, as a representative/agent."

See addendum.

Applicable to which section?

(Solicitation Page Number and Paragraph)

DEPARTMENT's RESPONSE/ANSWER

ITIN Section 6.3.3, Point 7 refers to the search functionality required in eServices. Does this refer to a general content search in the website or is department looking for any specific search functionalities? Can this be described with few examples? 6.3.3

This does not refer to general content search.

Example 1: Reemployment Tax ‐ The ability to search for specific employees rather than manually scrolling or moving from page list to page list Example 2: Alcoholic Beverage and Tobacco ‐ The ability to search for a retailer Example 3: Sales Tax ‐ The ability to search for a location within a consolidated return

Is there a preference for On‐prem vs Cloud hosting solution? 6.4.6.5

There is no preference since the solution will be hosted by the Vendor.

ITIN section 6.5 states that all the code needs to be built using .Net/C# language.

Are there any limitations in proposing solutions which are built using languages like Java, HTML, JS, JS frameworks, etc. 6.5

All code must be built using language currently utilized by FDOR. Only C#, HTML, CSS, Javascript, or SQL will be accepted. See the addendum to the ITN.

Does the state envision implementation of a new IAM solution as part of eServices or utilize existing solution and integrate with eServices via SSO using SAML/OAUTH, etc.? 8.4.3

FDOR is not opposed to an Identity and Access Management solution provided the solution does not require interfacing with FDOR's back‐ end. The current requirement is the existing authentication method which is login ID and password. See section 6.5.6 System Administration.

The ITN indicates 'The existing eServices applications and services included in this solicitation are supported by FDOR’s current contracted vendor’ Is FDOR's current contracted vendor for eServices eligible to bid on this ITN? 6 ‐ Scope of Work Yes

(Solicitation Page Number and Paragraph)

DEPARTMENT's RESPONSE/ANSWER

Business rules validation Your ITN sets out data validation requirements, including, “Data perfection utilizing various edits and business rules provided by FDOR,” and “Invoke FDOR business rules to analyze and/or perform calculations on user’s data.” Could you please describe the relationship between the business rules and edits you anticipate being part of the eServices versus those that would occur within your backend processing system(s)? Specifically:

•Do you anticipate a tiered validation approach, whereby eServices would enforce identity and data structure, and the backend system would perform the full tax calculations and line‐item edits?

• Alternatively, would you expect all detailed calculations and edits to be performed in eServices and visible to an end user? If so, do you have a preferred architectural approach to make this happen (e.g., calls through APIs to the SAP back end)?

6.3 Design Requirements

Validation and calculations will be performed by the eServices system and separately by FDOR's backend system. The eServices system will apply certain data validation and business rules, including calculations, as provided by FDOR. Application Programming Interface calls to the SAP backend system are not used.

(Solicitation Page Number and Paragraph)

DEPARTMENT's RESPONSE/ANSWER

Pre‐population Your ITN sets out a requirement for pre‐population of user account data. Can you please specify what type of user account data is currently available via pre‐population and what data you expect to be available through your new eServices solution? Is this identity specific data or would it extend to tax, account, and financial data? Does the data you wish to pre‐populate come from within FDOR systems or from third parties (e.g., financial institutions, and/or other departments of government)? 6.3 Design Requirements

FDOR will provide profile information via nightly batch files which includes user credentials, entity name, address, form type expected, filing frequency, chosen payment method, banking information, and other pertinent account information.

Given that we are the current vendor for DOR GTA eServices system, can we send our current FDOR contract manager the reference form to complete for this ITN? General Yes

What is the anticipated start date for the contract?

General This will be negotiated with the selected Vendor.

Is the Vendor Responsibility Disclosure submitted with Volume 1 Administrative Reply Tab B or Tab C? Page 83 of the ITN states that it should be included in Tab B, but page 133 of the ITN says Tab C. General Tab B. See the addendum to the ITN.

(Solicitation Page Number and Paragraph)

DEPARTMENT's RESPONSE/ANSWER

Can you please elaborate on the search functionality within the application, section 6.3.3 Web Application(s) found on page 44? What is the purpose of the search?

6.3.3 Web Application(s)

The purpose of the search is to provide functionality for the user to locate information for assistance in filing and paying.

Example 1: Reemployment Tax ‐ The ability to search for specific employees rather than manually scrolling or moving from page list to page list Example 2: Alcoholic Beverage and Tobacco ‐ The ability to search for a retailer Example 3: Sales Tax ‐ The ability to search for a location within a consolidated return

File details come from the government source that posted it. Updated .