ADDENDUM 4.pdf

Legislative Appropriations System/Planning and Budgeting Subsystem (LAS/PBS) Data Application Migration

RFP No. EOG-RFP-23-02

Addendum No. 4 Questions and Answers and RFP Revisions

Questions and Answers

The EOG has received the following questions through email, and the Agency’s answers are provided in the table listed below:

No. Question Answer

1. We submitted a bid for this very project in July 2022.

Did the selected vendor fail to deliver?

Are there differences between

RFP EOG #EOG-RFP-23-02

vs RFP EOG #EOG-RFP-23- 01 (from last year)?

It was in the best interest of the Agency to reject all proposals submitted for EOG-RFP-23-01.

There are differences between EOG-RFP-23-01 and EOG-RFP- 23-02. Please refer to the solicitation documents, including all attachments for differences:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

2. I want work with you hand to hand for this project.

Please send to me the application form.

Please refer to the solicitation documents, including all attachments, for further information:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

3. I am writing to enquire if there will be a virtual-attendance option for the Pre-Proposal Meeting planned for this RFP on May 9, 2023?

Please refer to the solicitation documents, including Addendums, for further information regarding the Pre-Proposal Meeting.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

4. Will there be a zoom set up for the proposal meeting for remote attendees?

Please refer to the solicitation documents, including Addendums, for further information regarding the Pre-Proposal Meeting.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

5. I was not able to find Exhibit B – Technical Overview, is that something that will be provided later?

Please refer to Section 2.25, Non-Disclosure Agreement and Intent to Reply, of the RFP.

6. Please advise if there is a virtual option to attend the pre-proposal meeting on May 9th, Please refer to the solicitation documents, including Addendums, for further information regarding the Pre-Proposal Meeting.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004 https://vendor.myfloridamarketplace.com/search/bids/detail/5004 https://vendor.myfloridamarketplace.com/search/bids/detail/5004 https://vendor.myfloridamarketplace.com/search/bids/detail/5004 https://vendor.myfloridamarketplace.com/search/bids/detail/5004 and if attendance is mandatory for vendors who intend to respond.

7. I’m reaching out to ask for help with the Exhibit B Technical Overview, referenced in the Attachment A Scope of Services in section 5. This document is missing from the listed document in My Florida Marketplace. Would you be able to send me Exhibit B Technical Overview or post it on My Florida Marketplace so we can access it?

8. My team and I are reviewing the EOG-RFP-23-02 material. We would like to complete a NDA according to Section 11 on the scope of services attachment A to obtain Exhibit B – Technical Overview. Could you assist us with this process?

9. In the RFP on Page 15 of 16, The Additional Attachments section references an: Exhibit B, Technical Overview .

However, we do not see that attachment anywhere in the solicitation materials.

Can you please advise if and when Exhibit B, Technical Overview will be made available.

10. Can we receive a copy of Exhibit B as referenced in the Scope of Services?

11. How many online programs and how many batch programs (including any subroutines) by language, e.g., Natural, COBOL, assembler, etc.

Please refer to Exhibit B Technical Overview.

12. How many online programs and how many batch programs (including any subroutines) by lines of code, including copy books counted once.

Please refer to Exhibit B Technical Overview.

13. How many discrete data tables in the Adabas database?

14. Approximately how many records (or rows) are in each Adabas data table?

15. Approximately how many online queries and/or update transactions are processed per second, average and peak?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

16. The statement "The resultant application database shall replicate with the existing ADABAS database to ensure a failover method should the cloud application not perform once moved to production."

can be interpreted multiple ways. Do you mean that all updates to the Windows based database should also update Adabas on the mainframe? Or do you mean that the application has to be able to operate against a Windows based database or Adabas or both, selectively? Or do you mean something else?

We need a software solution that will replicate data directly between the ADABAS and Oracle outside of the converted application.

17. We would request a copy of Exhibit B as referenced in the Scope of Services.

18. I was wondering if you would be able to send me a copy of a bid you accepted for an older (different) project, or maybe point me to where I can see them myself, just so I can see the format and make sure I submit things correctly?

In accordance with Section 119.071, Florida Statutes, the proposals are exempt from the public record law until “such time as the agency provides notice of an intended decision concerning the reissued competitive solicitation or until the agency withdraws the reissued competitive solicitation.”

19. We noticed ‘Exhibit B – Technical Requirements’ missing from the list of attachments uploaded on my Florida marketplace portal. We would appreciate it if you could please upload the missing Exhibit B on the portal.

20. In reviewing the RFP, it appears that the documentation is missing: Exhibit B, Technical Overview. If I may ask as well – Today I saw that all dates pertinent to the RFP are now TBD – does that mean delayed and revised in the short term or is there an elongated hold being put on this project?

Please refer to Section 2.25, Non-Disclosure Agreement and Intent to Reply, of the RFP.

Please refer to the solicitation documents, including Addendums, for further information regarding the Solicitation Timeline.

21. We’d love the opportunity to participate if this initiative is still active. We did see some of the requirements to take part, but please do let us know if there’s any other info we should make note of, as well as next steps if applicable.

Please refer to the solicitation documents, including all attachments, for requirements:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

22. Is the Pre-Proposal meeting for EOG-RFP-23-02 cancelled for

Please refer to the solicitation documents, including Addendums, for further information regarding the Solicitation Timeline.

May 9th? I see in the new amendment it is currently

TBD.

23. The scope of services indicates we need to sign a NDA to get Exhibit B, Technical Overview and the SDD software and Code. How do we go about doing this?

24. I was wondering if the pre-meeting on May 9th had a way to attend remotely? If so can you please provide the link?

Please refer to the solicitation documents, including Addendums, for further information regarding the Pre-Proposal Meeting.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

25. We were wondering if you are planning to make a videoconference call so we can join and participate on the meeting? Also, are you so kind as to clarify to us if your are planning to release a new addendum with the new timeline?

Please refer to the solicitation documents, including Addendums, for further information regarding the Pre-Proposal Meeting.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

26. We could be missing it, but we’re not seeing the Exhibit B

– technical Overview document on the portal website. Would you mind forwarding to me if you get a moment?

27. If the system that you are proposing is developed using Microsoft C or .Net language, the functionality will change and business processes will slightly be adjusted due to the way the front-end application handles data and the calls that are being made to an external database (Oracle, version is needed). We are curious as to why Microsoft SQL Server is not being used since it has

The solution will use Oracle as the database as that is the preferred solution.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004 more seamless integration with the front-end application?

28. If someone from Florida requests the report be changed due to compliance reasons, then is that a major change to the contract or can we write code that gives the end-user the ability to make changes to the reports as necessary?

No changes to the functionality of the current application.

29. During our rollout phase, can the webserver (front-end processing) be one in the same where all of the processing can be done without transmitting the data to a webserver, it is encapsulated on the same front-end or is that a hard requirement?

The business and presentation layer may reside on the same server.

30. Reside in the Amazon cloud environment- Do you prefer server less computing standards, utilize Kubernetes/Containers or utilize Virtual Cluster servers that replicate data across between where we have the ability to invoke Elasticity (expand and contract) from a server standpoint (design considerations)?

We do not have a preferred cloud vendor. The solution must be able to scale database and web servers to accommodate for varying workload demands.

31. Use modern programming technologies? Are we able to use an assortment of languages (Go, .NodeJS, Angular, Python or Java) or is this limited to Microsoft .Net/C# coding language?

The preference is for all migrated code to be in C#.

32. Use modern database for data storage? As mentioned earlier, are we able to migrate the data from Oracle (or whatever backend DB) to Microsoft Clustered SQL Servers or are we limited to Oracle Servers (please provide the version of

The solution will use Oracle as the database as that is the preferred solution. Current Oracle version is 19c. Currently, NoSQL is not an option.

Oracle). Also, can we utilize No-SQL in the front-end processing allowing the data to be flushed to the backend database for long-term storage or is there a set standard the organization would like to remain as part of their de-facto-standard

33. Easily add/remove hardware resources allowing SDD to increase resources during peak usage and remove resources when they are not needed? I take it that SDD means System Design and Development policy. From the statement, about resources, this referred to as Elasticity (expand and contract), so if that is the case, do you know the amount of resources being consumed or utilized during peak utilization periods (memory, CPU, storage, etc) based upon past charts graphics (analysis), this is referred to as Benchmarking or Sizing of the application (this will help in determining the right size of the servers to build based on anticipated requirements)?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

34. Perform bi-directional replication between the converted database and the existing mainframe database?

If we are performing bi-directional database replication, I assume the Mainframe (MFr) Database (DB) (Oracle) will remain onsite, for how long will the MFrDB remain on site until we are ready to roll everything over or will the mainframe be part of the on-premise design?

The mainframe database will remain onsite and operational for a minimum of 1 year.

35. Provide increased security with two factor authentication (2FA)? So will AWS provide the MFA from an application standpoint or will we utilize an existing MFA tool provided by Florida or do we provide a third-party solution that integrates with AD or some onsite authentication mechanism

This is a new requirement for the LAS/PBS application. There is not a preferred method or tool. We are looking for a proposed solution from the vendor.

36. Meet or exceed the current web application performance measures - Can the contract group provide metrics of how the existing system is performing?

Yes.

37. Maintain the look and feel of the current LAS/PBS Web environment (user interface)?

There maybe certain aspects of the application that will be enhanced because of the improved programming capability due to slight changes in how the front-end processes data, would this be acceptable?

The functionality of the application must stay the same. If there are improvements in performance and processing, that is acceptable.

38. Cause no change in functionality between current transactions and converted transactions - certain changes will occur due to the coding variations, but the end result will remain the same from a processing standpoint, will this be acceptable?

The functionality of the application must stay the same. If there are improvements in performance and processing, that is acceptable.

39. Convert transactions without web interface to reside within the web application? Not sure if we understand the logic at this point, we are looking to webify this application allowing the web-based application to to process data using a modular/function

The solution will use Oracle as the database as that is the preferred solution. If the vendor wishes to provide detailed solution for improved processing and handling large amounts of data, that is acceptable.

approach, some of the processing of data can be performed in the front-end using stored procedures and in certain regards implementing caching to performance (load-balance the load across multiple servers or utilize serverless computing environment or No-SQL process (large amount of data at the front-end while eventually flushing the results for storage to a relational DB), is this an acceptable design or are you looking at classic computing design scheme using AWS as the datacenter to provide the server compute environment?

40. Does the system have to be Windows Server/Oracle or can we implement a Serverless (Linux) environment with No- SQL/SQL database processing in the frontend and backend of the application (allowing for .Net, .NodeJS, Python or Java) or is this a definitive requirement (Windows Server/Oracle) that will not be allowed to change?

The solution will use Windows/Oracle as the preferred technology.

41. I'm writing to you to take an update on the above referenced RFP. As the timeline has been revised to TBD as per Addendum 1, can you please let us know if this RFP is currently kept on hold or is it going to get cancelled on the whole?

Please refer to the solicitation documents, including Addendums,

42. When does the EOG anticipate releasing the new bid Solicitation Timeline?

43. Does the EOG want vendors to send our project-specific questions now or at a later date when the project dates are known?

for further information regarding the question submittal deadline.

44. Attachment A mentions “Exhibit B—Technical Overview.” We aren’t able to find Exhibit B in the documents available from the Florida marketplace. Please direct us to Exhibit B or email a copy.

45. Any updates on when this opportunity will have new deadlines?

Please refer to the solicitation documents, including Addendums, for further information regarding the Solicitation Timeline.

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

46. Per the RFP EOG-RFP-23-02 looking to get the NDA to sign for the source code.

47. Good morning. I wanted to alert you that it appears the link to the addendum that was posted on Government Navigator, links to the bid document, not the addendum. The bid document and specification links work correctly, the addendum link looks to be incorrectly pulling up the bid document.

Please refer to the solicitation documents, including all attachments and addendums, for further information:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

48. We understand that the State requests back a completed and signed Attachment K - Confidentiality and Non- Disclosure Agreement with no changes. Would we also be able to include a copy of our NDA to the State for redlines as it would be mutually beneficial for all parties?

49. I don’t see the "Exhibit B - Technical Overview" on MFMP. Are you able to share it or update the link?

50. Do we know when we will receive the technical documents

51. When can we expect to receive the link to access exhibit B

52. We wanted to clarify a question regarding pt. 7.0 ‘Location of Work’. We have a strong migration team in Canada. Is Canada considered “offshore” and will we be able to leverage them on this project?

Please refer to Section 7.0, Location of Work, in Attachment A, Scope of Services. Canada is considered offshore.

53. In case we are planning to subcontract. Can the Subcontractor comply with all the minimum requirements stated in the AOC's RFP?

All Respondents must supply written proof of subcontractor commitments for this solicitation. The subcontractor commitment must be on the subcontractor’s letterhead, stating the entity’s agreement to provide the specified services to the Respondent’s organization. In addition, subcontractor qualifications must be provided.

54. Is there a preferred font size type for RFP responses?

No. The proposal must be reader friendly text.

55. Technical Proposal, Tab C, Respondent's Management Plan, Identification and Qualifications of Key Personnel: Is there a page limit for Key Personnel Resumes?

Tab C has a page limit. Please see RFP Revision #2 below for the revised Tab C page limit.

56. Technical Proposal, Tab B, References: Is the State going to favor public references over private references?

No.

57. Technical Proposal: Are there any format margins that we need to consider when writing our proposal?

No. The proposal must be reader friendly.

58. Is it required to provide the COI alongside the proposal response?

Need more clarification.

59. Does the agency have a mandatory goal percentage established for

MBE/VSBE/DBE/LBE?

No.

60. If we are using a subcontractor, can the subcontractor meet the

MBE/VSBE/DBE/LBE

participation?

EOG does not track subcontracting spend with certified business enterprises.

61. Could the agency accept an electronic proposal response?

No.

62. In case as a prime we cannot comply with the references requested, does the agency allows to use of a subcontractor to comply with those references?

The prime and subcontractor must comply with all requirements of the RFP.

63. A. Technical Proposal - d.

Professional Licensing: Is it required for us to submit the proof of licensing with the proposal or can we submit it post-ward?

Documentation must be provided to the Agency prior to finalizing any contract resulting from this solicitation.

64. A. Technical Proposal - d.

Professional Licensing: If the licensing is currently under progress, can we submit documentation proving it is under process?

Documentation must be provided to the Agency prior to finalizing any contract resulting from this solicitation.

65. Is there any established performance bond in this project?

Please refer to Section 2.20, Performance Bond, of the RFP for performance bond details.

66. Could the agency please grant an extension on the due date?

Please refer to the solicitation documents, including all attachments and addendums, for further information regarding the RFP’s timeline:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

67. What is the estimated budget for this contract?

11 million dollars.

68. Does the agency allow using of subcontractors in this project?

Yes.

69. Does the agency accept remote resources to work on the project?

Please refer to Section 7.0, Location of Work, in Attachment A, Scope of Services.

70. Does the agency prefer on-site resources to execute the project?

Please refer to Section 7.0, Location of Work, in Attachment A, Scope of Services.

71. Is there any incumbent associated with this project? If so, please disclose the name.

No.

72. Does the agency require wet ink signatures?

No.

73. Is it allowed to use digital signatures?

Yes.

74. We understand that the State requests back a completed and signed Attachment K - Confidentiality and Non- Disclosure Agreement with no changes. Would we also be able to include a copy of our NDA to the State for redlines as it would be mutually beneficial for all parties?

75. We are intending to respond to the RFP # as noted in the subject line and understand the deadline has been extended to 07/12/2023. We unfortunately missed the question deadline and were curious if there were a similar extension on submitting questions?

Please refer to the solicitation documents, including all attachments and addendums, for further information:

76. Noticed this RFP was paused and we’re curious if there is a plan to keep this opportunity going? We’re putting together our response now and we’re just hoping to get a sense of timeline.

Please refer to the solicitation documents, including all attachments and addendums, for further information:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

77. As per Addendum 1, all the dates are marked as 'TBD.' Could you please confirm the submission timeline. Are we anticipating any changes in the

RFP.

Please refer to the solicitation documents, including all attachments and addendums, for further information:

https://vendor.myfloridamarketplace.com/search/bids/detail/5004

78. Java and C# are both strongly-typed object-oriented programming languages, sharing a similar programming syntax. However, The Java programming language is more flexible, versatile, and secure than C#. For most cloud-based apps and mobile apps, the underlying language is Java. Java is also processor independent, which means that in addition to x86, new architectures such as the highly performant & cost-effective arm64 processor can be seamlessly utilized. Java also provides a massive array of 3rd party libraries, frameworks & tools. Thus, please let us know if the State of Florida will accept a Java-based solution for the Mainframe migration project?

The preference is for all migrated code to be in C#.

79. Can you provide application source code metrics including lines of Natural code; number of Adabas FDTs; and breakdown of Natural source code by module type?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

80. Can you advise whether the application contains any Natural CONSTRUCT code?

If yes does the state have the license right to re-engineer the Software AG licensed components of this code?

The current application does not contain/use any CONSTRUCT code.

81. How many rows does an ADAREP report show are in the production database? Can you provide the ADAREP report that created these row counts by

FDT?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

82. Does the application use any HATS screens?

No.

83. Does the application use any other screen scraped interfaces or technologies?

No.

84. Does the application have any other languages such as Cobol, PL1 etc for accessing Adabas?

Or that interface with the Natural applications whether in on-line or batch operations?

Please refer to Exhibit B Technical Overview.

85. How many batch jobs are there accessing Adabas?

Please refer to Exhibit B Technical Overview.

86. Can modernization tasks be completed in Canada provided that the new systems are accessed, maintained and operated in production within the United States?

Please refer to Revised Attachment A, Scope of Services.

87. Does the state have a non-confidential Natural / Adabas test environment available that can be accessed externally via VPN connection for unit and system testing?

Yes.

88. Does the state have test scripts and test results against the test database?

Yes, but not extensive.

89. Who maintains the application

- the state or a third party? If a third party can you provide contact details?

System Design and Development (SDD), Governor’s Office, State of Florida.

90. The requirements in the Attachment A - Scope of Services (Revised Section 1.0) says in part - "..the application be developed using the Microsoft’s C#...", which if an unwaivable condition/design requirement might preclude us from bidding or providing a cost effective solution.

Java and C# are each object oriented programming language. However, our experience is that Java is more flexible and has a wider user community for resourcing change implementation and for Cloud based open source design features.

Will the state technically accept a Java based solution and amend the RFP accordingly?

The C# language is preferred.

91. Does the application contain any Report Mode code?

Yes, both Structured and Report Mode.

92. Will the Natural and Adabas source code artifacts be made available for detailed analysis?

If not would the state consider running a simple Java utility to extract detailed architectural information from the source code artifacts?

The Natural and Adabas code are on the SharePoint site available to vendors who have completed the non-disclosure form.

93. Attachment A - 2.0 Current Production Implementation -this states that 30 transactions are only available on the web -are those web-only transactions processed on the

Yes, all web transactions run Natural and/or Cobol on the mainframe.

mainframe? Do the Mainframe and Web front-ends access transactions running only on the Mainframe?

94. Attachment A - 7.0 Location of Work - this stipulates work can not be done offshore. Our Natural conversion migration team is based in Spain - is this acceptable?

Please refer to Section 7.0, Location of Work, in Attachment A, Scope of Services.

95. Attachment A - there are several references to "Azure DevOps" - are DevOps toolchains on non-Azure environments acceptable?

Azure dev ops is preferred.

96. Exhibit B mentions the total MIPS as 1193 - what is the MIPS consumption split between the applications and Adabas for each of the production, technical, development, and test environments?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

97. Exhibit B - other than EntireX, are there any other mechanisms that the Web app uses to invoke transactions on the mainframe?

Software AG EntireX is the only mechanism used to communicate with the mainframe.

98. Exhibit B - you specify that the current Web application is written in Visual Basic - is it an essential requirement that this Web front-end application be migrated to a modern language (such as C# or Java)?

An alternative lower-risk option would be a 2-phased approach, where Phase 1 retains the existing Web application (which would invoke transactions in the replatformed mainframe application).

The C# language is preferred.

99. Exhibit B - you identify 1002 JCL members - do you expect these jobs to execute "as is"

The proposed solution for JCL / jobs must conform to the current functionality. The technical proposal is up to the vendor.

(i.e. via execution of the JCL itself), or are you expecting the JCL to be transformed into something else? Would either approach be acceptable?

100. Exhibit B - you identify CA7 as the current mainframe scheduler - do you expect these schedules to be migrated to an off-mainframe scheduling solution? If so, do you have a preference, or is it acceptable for us to specify an alternative?

There is no preference except that it run on Windows servers.

101.

The second paragraph of Article 3.0 of the Attachment A (Scope of Services) says in part:

"Upon project completion, SSD will be given all source code and documentation created by the Vendor for application maintenance and enhancements."

a. We believe that under copyright law generally any source code, whether C## or Java or other languages) created by a vendor by processing or reverse engineering a LAS/PBS module or artifact is technically a "derivative work" and therefor intellectual property ("IP") ownership would be exclusive to SSD. Does the state agree with this foundation principal?

b. Under the same copyright principal, the IP ownership rights for source code created independently by a vendor without use of LAS/PBS

Per Attachment A Scope of Services, all code developed as part of project and supports the operation of LAS/PBS is property of

SDD.

modules or artifacts is the exclusive to the vendor. Does the state agree with this foundation principal?

c. Our technical solution creates derivative works from the LAS/PBS source code which will be owned by SDD but for runtime execution of these derivative works they must be compiled in conjunction with certain vendor proprietary components. We likely will propose to provide a source code license to SDD for these vendor components to enable the state to perform potential application maintenance and enhancements in the future with or without support from us. The technical terms for such a license would typically be - perpetual with full rights to create derivative works for SDD production usage. Would such a license be acceptable and satisfy the requirements of this above note introductory paragraph?

102. Will the state provide the Cloud environment and associated security infrastructure or do we need to include these technical details / costs in our proposal?

SDD will provide the cloud and security infrastructure.

103. Is a technical solution which maintains the Natural source as is, but re compiles/transpiles that source to a C## runtime environment be acceptable or must the Natural source code be transformed to C## code for ongoing source maintenance?

No. The goal of this transformation project is to have all the current aspects of the LASPBS application (web and mainframe) running using same software and on same platform (eliminating disparate software and platforms).

104. Is acceptable for certain proprietary C## runtime components be delivered only in object code with an ongoing contract for operations and maintenance with the vendor?

No.

105. Will the state be calculating a total cost of ownership ("TCO") for this project including the future (say 5 or 10 year) license costs to compare present value of competitive proposals? If so do we need to provide a cost estimate for future software annual license costs for any licensed components of our solutions?

A proposed TCO for 5 to 10 years is preferred.

106. Does the state run the current application on an in-house mainframe or is it outsourced?

Will the state continue to provide all costs associated with this infrastructure including all hardware and software licenses necessary to support application operations and maintenance for the year period post MS16 that it must be maintained as backup in the event of the new Cloud system failing for an unacceptable period?

LAS/PBS is a legacy application that resides on the Department of Financial Services (DFS) IBM mainframe. The Executive Office of the Governor, SDD will continue to financially support the LASPBS maintenance.

107. We have examined the DDM source items and they appear to be in display format. Is it possible to provide them in SYSOBJ format to enable detailed analysis before proposal submission?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

108. Would the state prefer a subscription model pricing for any licensed components including those used in conversion but not necessarily

The vendor shall provide a proposal for the total cost of the project.

a deliverable for future maintenance?

109. Must the converted application be delivered in a Docker container or equivalent to enable deployment to multiple Commercial Clouds?

The preferred tool is Azure.

110. Is it acceptable to use a runtime Java interpreter to consume existing JCL without change to execute batch jobs in the new Java environment if Java is an acceptable language for conversion?

The preferred language is C#. The vendor shall propose a solution and details on how JCL will be converted.

111. In the project preplanning presentation it was stated that SDD wanted to convert the existing legacy application to modern technologies and have the production application reside on the cloud. In the Attachment A Scope of Services it stated that SDD requires the application be developed using the Microsoft’s C# language.

Which of these requirements takes precedence.

The preplanning presentation does include new application architecture with Oracle and Microsoft C#. Microsoft C# is the preferred language.

112. Is your preferred migration target C# of Java?

Microsoft C# is the preferred language.

113. Is there more than one (1) ADABAS Logical Structure?

No.

114. Is ADABAS Accessed from

COBOL?

Yes. It is called using ADAUSER.

115. What is the percent (or count) of Natural Code in Reporting Model?

There are approximately 1,584 Natural objects written in reporting mode.

116. What is the percent (or count) of Natural Code in Structured Mode?

There are approximately 4,480 Natural objects written in structure mode.

117. What is the percent (or count) of Natural Code Online?

There is approximately 70% Natural online programs.

118. What is the percent (or count) of Natural Code Batch?

There is approximately 30% Natural batch programs.

119. Are code generators in use for JCL, Natural, or COBOL?

No code generator. Some Natural programs do generate JCL.

120. Is there significant generation of JCL, Natural, or COBOL at runtime? (This includes use of NATRJE that was mentioned, Natural RUN, …)

Yes.

121. Can you confirm the Natural library count being 337?

Yes.

122. ADABAS: Are there MU and/or PE fields with more than 191 occurrences?

No.

123. ADABAS: Are occurring super descriptors being used?

No.

124. ADABAS: Are phonetic or hyper descriptors being used?

No.

125. Does the application actively make use of uncommitted reads (aka dirty reads)?

No.

126. Is there actual intent to do replication in a bi-directional way (implies a need to be able to simultaneous use both the old system and new system), as opposed to in one direction only?

Yes. The intent is to replicate the databases (existing ADABAS and the new Oracle) real time. This is part of the year long post implementation support and risk mitigation plan.

127. The VB.NET is not present in the target architecture, will this access method be discontinued?

For the LASPBS target architecture, VB.NET is not needed.

However, SDD have other applications that will still use

VB.NET.

128. Is all functionality offered by the VB.NET + EntireX access method also available through the existing Natural screen access method?

No.

129. What are the current measures on application performance?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

130. What is the target type of the ADABAS database for the migration?

The goal of project is to convert ADABAS to Oracle.

131. Has a cloud ecosystem been defined for the cloud migration?

No.

132. Are Change Data Capture features in scope to keep old and migrated systems in sync?

The only CDC is to replicate existing ADABAS and new Oracle databases. We are looking for vendor to propose a tool/process for this.

133. Is FedRAMP certification a requirement to leverage cloud solutions?

The project will adhere to rules under the State of Florida.

134. Outside of ADABAS, are there other relational database systems used by the application?

Yes. Please see Exhibit B Technical Overview.

135. Are there other mainframe systems being used?

LASPBS is the only mainframe application supported, however, there is a separate/additional mainframe data center utilized for disaster recovery.

136. In place of a performance bond, would the state consider a retainage arrangement wherein any amounts due for work completed have a percentage of total payment retained until completion and final acceptance by the State?

No.

137. The section 3.0 outlines the list of requirements for the proposed solution, including "meet or exceed the current web application performance measures". Please share current web application performance measures that are to be considered and their target values (to be met or exceeded).

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

138. The Term section states that "The Initial Contract term will be for three (3) years". Please confirm that this 3-year period includes the 1-year Post Implementation Support and Maintenance phase.

Yes.

139. Volume of data in ADABAS database?

Please see ADAREP document in the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

140. Number of objects in ADABAS database?

Please see document in the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

141. Is there any transactional data being stored in the mainframe or elsewhere outside of the ADABAS database? If so, please provide details.

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

142. Please provide maximum transaction volume during peak period.

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

143. How many transactions per day?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

144. Can we assume the ADABAS data model relational-like? Are there any significant referential integrity issues to resolve? If so, please provide details.

ADABAS is not relational-like and there are no integrity issues to be resolved.

145. Are there master data and reference data quality/issues/cleanup required? If so, please provide details.

No.

146. Is there data integration required from other systems?

In and/or outgoing for operational or reporting requirements? If so, please provide details.

Refer to Exhibit B Technical Overview as well as Exhibit A Business Requirements.

Is there any manual data management that we must be aware of? If so, please provide details.

No.

147. Is there an existing reporting/BI/Analytics framework that can/will be leveraged by new architecture?

If so, please provide details.

Please refer to Exhibit B Technical Overview. An example is TRIM for ADABAS monitoring and statistics.

148. Is there a data integration platform that is already in use and preferred? If so, please provide details.

No.

149. Do you have all the source code for the applications in the languages list above? If not, please provide details on

All source code is available. Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

which applications for which Source code is not available.

150. How many batch jobs are scheduled using your current batch scheduler? Please provide your answer in terms of # of jobs and frequency (e.g., daily, on demand, weekly, monthly, quarterly, annually, etc.)

There are approximately 30 scheduled batch jobs, most are run daily and few are run weekly and monthly.

151. Are there other applications that will not be migrated off the mainframe that share data with this application, and how is that data shared? Can we have information regarding when these applications will be moved off of the mainframe?

Please refer to Exhibit B Technical Overview to understand the current integration points and method.

152. Does there exist any other architectural diagrams of your environment(s) or other documentation that hasn’t already been provided? If so, please provide details.

No.

153. Please provide details on Source Code Control Used

Currently use Visual Studio Source Control. Azure DevOps solution is the target.

154. Are there any specific data or security compliance requirements for the application (e.g., SOX). If so, please provide details.

No.

155. Please provide details on the data classification of the data managed by the application

N/A

156. Is there a Single Sign On (SSO) / Multifactor Authentication (MFA) integrated with the application? If so, please provide details.

No.

157. Is there a copy of Anonymized data that the development team will have access to? If so, please provide details.

We do not anonymize the data, however, there is functionality to protect or not display sensitive data.

158. Does this application require High Availability? If so, please provide details.

Yes, specifically during peak times throughout the budget cycle.

159. (If you know the approximate number of lines of code AND their complexity for each type of the application modules, please specify)

[ ] COBOL

[ ] CICS (Online and Batch)

[ ] JCL

[ ] Natural Programs and Subprograms [ ] Help Routines [ ] Help Maps [ ] Maps [ ] Copy Code [ ] VB.net [ ] Functions Listed in Section

9.6 - Other Processes in the Technical Overview Document Please specify language, lines of code, and complexity for each process / function [ ] Other, please specify ____

Yes. Please see Exhibit B Technical Overview.

160. The provided COBOL code (250+ files) uses standard IBM file I/O with no stated

ORGANIZATION

phrase. We assume these are all sequential files. Having this many files that do sequential only Input/Ouput seems very unusual. Please confirm.

Please see Exhibit B Technical Overview. There are 265 COBOL objects (programs). The files that are processed by the COBOL objects are sequential.

161. The COBOL code does not appear otherwise to use Adabas. Please confirm.

(Perhaps the missing copylibs do this).

a. BNSC1ECD is a good example: it mentions "ADABASE" in an error message, but it contains no visible ADABAS I/O.

Many of the COBOL programs do read the ADABAS database.

162. Does the application do magnetic tape I/O anywhere? For what purpose?

No.

163. The COBOL code uses "CRD- FILE" as a source. Is that intended to be an actual card deck? If not, what is it?

No.

164. Identifications and Qualifications of Key Personnel specifies including the resume for each proposed individual in addition to their qualifications and their functions and responsibilities, could the resumes be provided in an appendix which doesn’t count against the 40 page limit of the Management Plan?

No. Please see RFP Revision #2 below for the revised Tab C page limit.

165. Are we to provide 11 copies of the Cost Sheet, or just one cost sheet per proposal?

One copy.

166. In 2.10.C, it states “The Respondent objects to and should not consider any additional terms or conditions submitted by a respondent, including any appearing in documents attached as part of a Respondent’s response.”

Should it be amended to “The Agency objects to and…”?

Yes. Please see RFP Revision #3 below.

167. Is SDD using any defect tracking tools, if so which ones and would the vendor be able to leverage and how many licenses are available? If not, is there a preference for a defect tracking tool?

The preference is Azure.

168. Is SDD using any automation Testing tools, if so which ones and would the vendor be able to leverage, how many licenses are available? If not, is there a preference for an automation Testing tool?

No.

169. Is SDD ok with having a Project Manager who does not have a PMP who has led these types of projects and has practical experience in delivering like for like systems.

SDD prefers to have a Project Manager with a PMP but it’s not a mandatory requirement.

170. Is the current system 508 compliant? If not, how is the vendor to make changes to make the screen compliant as this will result in a change in functionality?

SDD strives to produces applications that adhere to 508 standards. Any issues with 508 compliance will be addressed during development.

171. Does SDD have all of the functional and non-functional business requirements documented with traceability to test cases as well as Technical requirements?

No. This is a project deliverable by the vendor in collaboration with SDD.

172. Does SDD have in place full regression test cases, test scripts and use cases? If not full regression, what % of the application functionality is covered by established regression tests?

No. This is a project deliverable by the vendor in collaboration with SDD.

173. Are there documented System Performance requirements for transaction processing times, batch times and system responses?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form. However, it is expected to have baseline performance measures completed by the vendor.

174. What are the documented performance metrics being collected for the current web application?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form. However, it is expected to have baseline performance measures completed by the vendor.

175. Are there documented SLAs?

Is the current system under stakeholder SLA requirements?

Yes.

176. Are there currently any known defects in the system for which SDD has implemented manual processes as workarounds? If so, please provide a listing and any documentation of the workarounds.

177. Vendor is expected to migrate legacy Adabas data to new relational DB. Does that data need cleansing?

No cleansing needed.

178. Are there any Adhoc reports not provided in the technical documentation portal? If so, how many and could we get access to the code for them?

No.

179. In the Pre-Proposal meeting it was stated that SDD would be procuring all hardware and software as well as the Cloud Hosting environment. Is SDD setting up and configuring the Cloud environment or will the selected vendor configure and setup the Cloud environment?

SDD will procure and set up environment. However, it is expected that the vendor will assist in set up and configuration to meet requirements.

180. The LAS/PBS Mainframe application production environment has performance levels and space capacity that must be maintained or improved with transformation.

Can SDD provide the performance levels and space capacity?

Please refer to Exhibit B Technical Overview as well as the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

181. The LAS/PBS Web application production environment has performance levels and space capacity that must be maintained or improved with transformation.

Can SDD provide the performance levels and space capacity?

Please refer to the Exhibit B Technical Overview for space requirements. Performance measures will be provided in the LASPBS SharePoint site available to vendors who have completed the non-disclosure form.

182. The LAS/PBS application has load balancing technology that must be maintained or improved with transformation.

Can SDD provide the load balancing criteria or performance characteristics?

Our load balancers use a weighted round robin algorithm that measures the connections count.

183. It is our understanding from the Pre-Proposal meeting that only labor is to be in the Cost Sheet. All hardware and software purchases would be purchased by SDD based on the vendors recommendations and requirements.

The Agency is only requesting services that are listed in Attachment B, Cost Sheet. Any software or hardware purchases will be separate from this RFP.

184. Attachment G makes reference to “Technical Approach - Questions Responses” however this doesn’t appear to be connected to any of the RFP response instructions for the Tab D Technical Plan Sections A-E. Please advise as to what content evaluators might expect to see for scoring.

Please see Revised Attachment G, Technical Proposal Instructions and Evaluation Criteria.

185. May we include an acronym list outside of the 90 page limitation?

Yes.

186. Please clarify / confirm the requirements for original documents with original signature. Would electronic signatures created with tools such as Docusign be acceptable?

Yes, digital signatures are acceptable.

187. Is the current web application in the desired end state location? (i.e. – AWS, Azure) If so, where does it reside?

No. Current web application resides in an on-premise windows environment.

188. Is the user preferences database already in an Oracle

DB?

Yes.

189. Is CI/CD in place for current web application environments?

What toolsets are being used?

No.

190. What is the preferred Authentication method? (Okta, AzureB2B/B2C, etc.)

No preference.

191. Is there an Agency preferred IDAM solution that would be leveraged for authentication and function-by-function permissioning?

No preference.

192. Several of the Financial Consequences entries have a mismatch between the written amount vs the numeric amount, for example “…assessed two hundred dollars ($100) for each …”.

Please clarify.

Please see Scope of Services Revision #5 below.

193. Are there API integrations available for these systems?

(Flair, People First, etc.)

Please refer to the Exhibit B Technical Overview for all integration systems and file processing methods.

194. What is the current size of the data set that needs to be migrated/converted?

Please refer to the Exhibit B Technical Overview for space requirements.

195. Does the data set in its entirety need to be migrated and converted?

Yes.

196. Would the state consider electronic submission for delivery of the final proposal, instead of paper copies and a flash drive?

No.

197. Is your preferred migration target language C# or Java?

Preferred language is C#.

198. Is there more than 1 ADABAS Logical Structure?

Please refer to the Exhibit B Technical Overview for space requirements. There are 4 ADABAS databases for each environment (sandbox, development, test and production).

199. Is ADABAS Accessed from

COBOL?

Yes.

200. Percent (or count) of Natural Code in Reporting Mode?

There are approximately 1,584 Natural objects written in reporting mode.

201. Percent (or count) of Natural Code in Structured Mode?

There are approximately 4,480 Natural objects written in…