DLA-2022.03 Addendum 1.pdf

STATE OF FLORIDA

DEPARTMENT OF LEGAL AFFAIRS

OFFICE OF THE ATTORNEY GENERAL

REQUEST FOR PROPOSAL

RFP DLA-2022.03

PRICE GOUGING APPLICATION

ADDENDUM NO. 1

Questions and Answers

December 20, 2022

Contained herein are the responses to the questions submitted to the Department of Legal Affairs, Office of the Attorney General

(Department) with regard to RFP DLA-2022.03, Price Gouging Application. This Addendum amends the RFP. In the event of a conflict between previously released information and the information contained in this Addendum, the information herein will control. The information included in this Addendum incorporated and made part of this solicitation.

FAILURE TO FILE A PROTEST WITHIN THE TIME PRESCRIBED IN SECTION 120.57(3), FLORIDA STATUTES, OR

FAILURE TO FILE A BOND OR OTHER SECURITYWITHIN THE TIME ALLOWED FOR FILING A BOND SHALL

CONSTITUTE A WAIVER OF PROCEEDINGS UNDER CHAPTER 120, FLORIDA STATUTES.

Note: This Addendum No. 1 does not need to be returned with the Reply.

The Department has received the following questions from the contractor community and answers are provided in the following table:

# QUESTION ANSWER

1. Whether companies from Outside USA can apply for this?

(like, from India or Canada)

Yes, but respondents must be in compliance at all times with Section 2.13 of the RFP and Attachment A, Section 12.

2. Whether we need to come over there for meetings? In person meetings are not required.

3. Can we perform the tasks (related to RFP) outside USA?

(like, from India or Canada)

No, see answer to question number 1.

4. Can we submit the proposals via email? See RFP Section 1.5.

5. Why is the state not renewing with the current vendor? The contract expires on May 31, 2023, and there are no renewals remaining.

6. What date does the application need to go live to replace the current app?

The go-live date is no later than May 1, 2023. See Section 4.2 of the

RFP.

7. What functionality is missing from the current application you wish to have?

All requested functionality is specified in the RFP.

8. What is the budget for the app in terms of licensing, support and maintenance?

There is no specific budget identified for this project.

9. What did the state pay the existing vendor for licensing, support, and maintenance?

$70,245 since inception.

10. Who will provide the Spanish translations of the content? Amended Section 4.2.2 in RFP, Addendum No. 2.

11. Does dynamic content, such as the emergency categories and form fields, need Spanish language support?

Currently, this is not required.

12. What type of data and analytics are expected to be reported upon?

All data but analytics are in house.

13. What type of support does the existing “OAG Web Service

Environment” have for reading, adding, and updating emergency categories, questions, and options?

Rudimentary.

14. What type of support does the existing “OAG Web Service

Environment” have for handling uploaded PDFs, photos, and location data?

Anything the customer uploads should be accessible provided it is not malicious.

15. Are end users of the application expected or required to create accounts and authenticate before submitting a complaint?

No requirement to register or authenticate to submit a complaint.

16. What type of support does the existing “OAG Web Service

Environment” have for end user account provisioning and authentication?

End users do not need to register or authenticate.

17. What manner of account provisioning and application authentication is needed?

End users do not need to register or authenticate.

18. Is this app intended to be an improvement on the current “No Scam” app or is this a new application all together?

It should contain the functionality outlined in the solicitation.

19. What data structures, IDEs are in use for the current application?

Reciprocal Microsoft SQL server and IBM Notes IDE/Structures.

20. Is there a current admin backend for this app, is one needed? There is a current admin backend for the app.

21. Does the application integrate with any other internal or external system or software?

The collected data is transferred to the OAG for further processing.

22. Is there a preference between using a single codebase (React

Native or Flutter) for both iOS and Android version or should both versions stand alone using Swift and Kotlin languages respectively?

There is no preference.

23. Does this mobile app or its backend store any reference data to compare standard pricing to determine gouging incidents? Or is it a process that is beyond the functionality of this app?

That is beyond the requested functionality outlined in this solicitation.

24. After submissions are made, how do the app administrators interact with the data?

The OAG collects all data submitted to the mobile app from the provider.

a. In what format (excel, pdf, on screen table,etc) is data displayed to the admins.

Currently, data arrives in json format, then loaded in house to other formats.

b. How will admins be alerted of submissions? (email, backend notification?)

The mobile app data is checked every 15 minutes for any new submissions.

c. Is the data capture process intended to be static? Or will image recognition be required ? (image to text be required)

Static.

25. Section 4.2.3.a Technical Requirements, page 21 of the RFP, states the need for integration with OAG Web Service Environment using REST Architecture or hosted SQL solution using a base64 authentication method. What type or types of data exchanges are needed?

Whatever will allow the data collected to be transferrable into the

OAG environment. Those listed are what are currently usable choices.

26. Are other systems pulling data from the solution or does the solution need to accept data from other systems?

Data only moves one way from the mobile app to the OAG.

27. If other systems are pulling data from the solution or the solution does need to accept data from other systems, how frequently?

The OAG currently runs a pull every 15 minutes but may vary depending on the emergency.

28. If the application receives or shares data with external entities, can you provide further detail regarding the complexity of the datasets?

Layouts will be provided as needed once a Contractor is selected.

29. What are the requirements regarding frequency of data exchanges? (Real-time, daily batch, etc.)

The OAG currently runs a pull every 15 minutes, but this may vary depending on the emergency.

30. What does the the current volume of reports submitted by users of the application look like, in numbers or an estimation?

Since implementation, we have processed 3504 transactions.

however, usage depends on the scale of the emergency.

31. Is helpdesk support required? Some provision for expedited support, especially during State of Emergencies, is expected.

32. Is customer service required? Customer support for the OAG is required. The OAG will provide

Customer support for citizens using the App.

33. Will the department provide an understanding of the current contract with the current vendor?

It is unknown what is meant by "provide an understanding of the current contract". The Contract is a public record and available for review upon request.

34. How many years has the contract been in place? The contract has been in place since June 1, 2019.

35. What is the total dollar value of the contract to date? See answer to question number 9.

36. Have there been any usability studies conducted for the app since the date of the last award?

No.

37. What key personnel are required for this project? It is up to the Respondent to determine what personnel is needed to develop, deploy, and satisfactorily maintain the Mobile App for the term of the Contract.

38. Who is the incumbent for this project? Shield Group Technologies, LLC

39. Is there currently an app in use by OAG to fulfill this requirement?

Yes. See Section 4.1.

40. Is it the Government’s expectation that hosting will be provided via cloud or on-prem server?

Hosting will be provided via Cloud or on the Contractors on-prem server. The OAG will not be hosting on-prem.

41. Can the Government provide points allocated and the Total Points achievable within the Price Proposal Scoring tables in

Section 6.2.2?

No further detail will be provided beyond what is specified in section 6.2

42. Can proposals be submitted electronically via email? See answer to question number 4.

43. How many users are expected to use the system? There is no upper limit. In practice, to date, we have had 3,504 since July 2019.

44. Has a budget been finalized for this project? If so, what is the budget?

See answer to question number 8.

45. Can the Government provide a list of all systems with which the Price Gouging App will integrate?

The OAG only needs the data collected by the mobile app. The further processing will happen in house.

46. Section 4.2.1 states: “The first-year pricing will include up to 80 hours for the contractor to provide system modifications/enhancements including necessary upgrades and future developments.” Is this determination including any bug fixes and/or system breaks that require maintenance?

No. Bug fixes and system breaks as part of the initial development will be included in the original pricing.

47. What is the Place of Performance for this contract? The United States. See answer to question number 1.

48. Should the contractor propose a project manager or will project management be performed by the Government?

Any required project management for this project will be performed by the Contractor.

49. How many releases per year does the Government expect for the Price Gouging Application?

The OAG does not expect continuous releases other than necessary to maintain compliance with the Mobile App stores on both platforms, or to implement any new changes or fixes.

50. Do REST APIs exist to integrate the Price Gouging App solution with existing systems?

Yes

51. Will REST APIs require development as part of the scope of this project?

Yes

52. What specific programming languages, application frameworks, or other web technologies is the Government requiring for the development of the Price Gouging

Application?

Contractor's prerogative.

53. What are the payment terms for the quote? Is payment per deliverable or on a monthly cadence?

See Standard Contract, Attachment A, Sections 4.1, 4.2, 4.4 and Attachment B, revised Price Sheet.

54. Have design requirements been finalized for this project, or does the Government anticipate requiring Joint Application Design sessions and other to-be planning sessions as part of the scope of this project?

The existing mobile app functionality can be used as a guide for design, or if the Contractor prefers, they may choose to include planning sessions or other design elements as part of their scope.

55. Why are you redeveloping the app? The contract with the current Contractor expires and there are no renewals remaining.

56. What are the current usage statics/load? See answer to question number 43.

57. What are the reporting requirements and format? The OAG is flexible, currently provided in json.

58. What is the preferred method of updating the categories/questions?

Back end user interface.

59. Will any existing data need to be migrated? No

60. For what purpose would we need to integrate with OAG’s Web

Service Environment?

No interface with the OAG Web Service environment directly.

Data collected by the mobile app will be pulled into the OAG environment.

61. What is the backup retention policy? Backup/retention of data sufficient to cover any DR needs.

Anything subject to State of Florida public records will follow the State's retention policies outlined in GS1-SL.

62. Please provide updated IT Security Policies, the items listed at https://www.flrules.org/gateway/ChapterHome.asp?Chapter=7 1A-1 are labeled repealed

The rule has migrated under the Department of Management

Services and is now known as 60 GG-2.