Attachment A - Scope of Services.pdf

Systems Design and Development

Attachment A

Scope of Services Executive Office of the Governor

State of Florida

Systems Design and Development

Legislative Appropriations System / Planning and Budgeting Subsystem Data Application Migration

1. Purpose _______________________________________________________________ 2

2. Background ____________________________________________________________ 2

3. Scope of Work/Deliverables _______________________________________________ 3

Database ___________________________________________________________________ 3

Non-Production Environment __________________________________________________ 4

Production Environment ______________________________________________________ 4

Application Framework _______________________________________________________ 5

Application Code Conversion ___________________________________________________ 5

LAS/PBS Hardware Environment _______________________________________________ 18

LAS/PBS Software Environment _______________________________________________ 20

4. Project Deliverables ____________________________________________________ 24

Project Initiation ____________________________________________________________ 25

Project Planning Phase _______________________________________________________ 25

Project Execution and Control Phase ___________________________________________ 30

Project Closure _____________________________________________________________ 31

One Year Post Implementation Support and Maintenance __________________________ 31

5. Location of Work _______________________________________________________ 31

6. Reports and Meetings ___________________________________________________ 31

7. Acceptance Criteria _____________________________________________________ 32

8. Constraints ____________________________________________________________ 32

9. Milestones ____________________________________________________________ 32

10. Deliverables, Performance Standards, and Financial Consequences ______________ 32

1. Purpose

The Legislative Appropriations System/Planning and Budgeting Subsystem (LAS/PBS) is a custom written and managed software application used by the State of Florida to develop and manage the annual budget for the State.

LAS/PBS is developed, maintained and supported by the Systems Design and Development unit (SDD) within the Florida Executive Office of the Governor (EOG). The application currently resides on an IBM mainframe operated by the Department of Financial Services (DFS), which will be decommissioned beginning in the summer of 2024. The LAS/PBS contract manager overseeing the operation of the LAS/PBS application has decided to take this opportunity to migrate the current application to more current technologies.

2. Background

The current LAS/PBS application is developed utilizing two distinct hardware and software platforms. For the purpose of this document, the mainframe application will be referred to as “LAS/PBS Mainframe” and the web based application will be referred to as “LAS/PBS Web.” Upon completion of this project the application will exist in a single web based application.

The LAS/PBS mainframe is developed utilizing Software AG’s (SAG) Natural programing language and ADABAS database. Parts of the mainframe application that mostly center on reporting are developed in COBOL. Application users access the application in a CICS environment with various mainframe emulation software packages.

LAS/PBS Web operates on Intel servers running the Windows 2012 R2 operating system. The web-based interface is developed and maintained with Microsoft’s VB.Net development software. A small Oracle database is used with the web-based application to store user preferences and other items not needed in the ADABAS database. LAS/PBS Web is designed to operate best in the Edge or Chrome browsers. Functionality within LAS/PBS Web also includes the ability to create PDFs from mainframe datasets, produce Word and Excel documents as well as sending emails to the user with output attachments.

Communication between LAS/PBS Mainframe and LAS/PBS Web is accomplished utilizing SAG’s EntireX enterprise application integration tool. Datasets are moved from the mainframe to the web servers via FTP/SFTP.

For the purpose of disaster recovery, LAS/PBS mainframe has the ability to run database backups at any time. Nightly jobs are scheduled to create a full backup of all system data, files and programs. Generation datasets are then created from these backups. Backups are created to provide the users with the roll back data changes and quickly return to a prior moment in time. Most backups are kept for 10 days. Major application milestones are placed on permanent retention.

LAS/PBS receives and transmits data to other State systems. These include the State accounting system (FLAIR/PALM), the State Personnel System (People First) and one of the State’s transparency systems (Transparency Florida). The data is transmitted nightly during non-peak hours using IBM JCL submitted to the job reader (NATRJE). LAS/PBS also creates on demand datasets for other supporting applications.

3. Deliverables

The LAS/PBS application as described in this section will need to be converted in stages. The LAS/PBS mainframe Adabas database and LAS/PBS Web Oracle database must be converted first.

LAS/PBS Mainframe and Web is developed with similar functions being grouped into components.

Each component contains data entry transactions, codes and titles transactions, utility transactions, and reporting transactions. Individual transaction requirements will be provided to the Contractor by SDD.

The expected conversion approach is one that will utilize proven and efficient database and source code translation process to restructure the LAS/PBS application preserving all current functionality.

The conversion should result in the LAS/PBS application residing on modern platform and software technologies that will allow the SDD team to continue to support and enhance the application.

Database

3.1.1. The Contractor should provide a converted database based on the data migration plan as approved by the LAS/PBS contract manager. The LAS/PBS data from the existing Adabas and Oracle databases shall be converted to a single Oracle relational database.

This data migration plan should include how Multi-value (MU – one field in an array) and Periodic Group (PE – many fields in an array) will be converted into the new Oracle relational design.

3.1.2. The final database solution should include environments for Sandbox, Development, Test and Production.

3.1.3. The Oracle relational design must keep the key structure from the LAS/PBS Adabas database. The key structure will maintain the unique identifier for each record in a file.

3.1.4. The Oracle relational design should be able to use the “Columns” approach as identified in the LAS/PBS Adabas database. The “Columns” approach allows data to be indexed and represents who owns the data in each column.

3.1.5. The LAS/PBS Adabas databases should be successfully converted into Oracle relational databases.

3.1.6. The LAS/PBS converted Oracle databases should be integrated with the current LAS/PBS Web Oracle databases.

3.1.7. The LAS/PBS converted data should be verified and affirmed that it matches the LAS/PBS Adabas data.

3.1.8. The LAS/PBS converted database should allow the ability to monitor and manage database users and activity in real-time.

3.1.9. The LAS/PBS converted database should allow the ability to design, create, test and deploy new database fields and files.

3.1.10. The LAS/PBS converted database should have the ability to leverage caching performance benefits.

3.1.11. The LAS/PBS converted database should provide the current level of performance and efficiency as the existing database.

3.1.12. The hardware chosen by the Contractor and agreed upon by the LAS/PBS contract manager to house the LAS/PBS converted databases should meet current size requirements as well as allow data storage growth of up to 5% per year.

3.1.13. The LAS/PBS converted database should have the ability to backup individual files and tables as well as entire database on a schedule and on demand should be available.

3.1.14. The LAS/PBS converted database should have the ability to restore individual files or tables as well as entire database must be available.

3.1.15. For conversion of the LAS/PBS database, the Contractor may include creating an interim excel file of raw data if that is determined by the Contractor and agreed upon by the LAS/PBS contract manager to be the best solution for specific files/tables.

Non-Production Environment

3.2.1. The Contractor should provide a separate environment(s) for development and testing that should mirror the production environment with databases and software/application.

3.2.2. The Contractor should provide separate environments for application development (maintenance, integration, testing and deployment) of converted programs and objects.

3.2.3. The application development and test environments should mirror the production environment.

3.2.4. The Contractor should provide a Disaster Recovery environment that mirrors the production environment along with a written plan to initiate the failover process. This plan will include any changes required on application servers, database servers, routers and domain name servers to successfully complete the failover. The Contractor’s plan should coincide with the Agency’s Strategic Cybersecurity plan.

3.2.5. A cloud based application should be delivered to SDD for sandbox, development and testing environments. Pursuant to 60GG-2.006 F.A.C, external service providers must adhere to the Agency’s security policies.

Production Environment

3.3.1. The Contractor should provide to the LAS/PBS contract manager an approved LAS/PBS application cloud estimate and solution detailing the number of application and database servers required to maintain current application response time.

3.3.2. The Contractor should provide a load balancing solution for the LAS/PBS cloud solution.

3.3.3. The Contractor should provide and submit to the LAS/PBS contract manager a scalability plan and solution based on LAS/PBS system usage and load.

Application Framework

3.4.1. Converted code should coexist with the existing LAS/PBS Web VB.Net code.

3.4.2. Converted code should incorporate Microsoft Web Forms used in the LAS/PBS Web application.

3.4.3. The LAS/PBS framework should mimic the Tabs and Framework of the current LAS/PBS

Web. Each transaction in LAS/PBS has been given a designated position within the framework.

3.4.4. The LAS/PBS framework should provide integration with FLAIR/PALM, People First, AMTRK, SUS and BAPS.

3.4.5. The LAS/PBS framework should integrate with LAS/PBS Web services including email, uploads, downloads, creation of PDFs, spreadsheets, and Word documents.

Application Code Conversion The LAS/PBS application components should be converted in the order that is outlined in the Application Code Conversion section: Security, Codes and Titles and remaining components within this section. Conversion of the LAS/PBS application is not meant to be a rewrite. The approach to source code conversion should be to utilize a process that will restructure the existing code to an improved platform and software technologies. All code conversion must occur after the approved and successful conversion of the LAS/PBS Adabas database.

All changes made by SDD during the project to the existing version of the LAS/PBS application should be remediated into each converted LAS/PBS component as part of the Change Management Plan. This should include incorporating changes made during any code freeze of the converted LAS/PBS application.

This section describes transactions for each component and identifies the development software utilized to develop the existing code. This information is intended to be used as a tool to aid the Contractor in determining the level of work. SDD has detailed requirements for each of the transactions outlined that should be provided to the Contractor during project initiation.

Tables are provided to identify the software platform.

• Natural – program logic is written in Natural and resides on the mainframe

• Cobol - program logic is written in Cobol and resides on the mainframe

• Mainframe Map – program display logic is written in Natural and resides on the mainframe

• Web – program display logic is written in VB.Net and resides on the Windows web servers

3.5.1. Application Security

LAS/PBS has three levels of security: Operator (role), Column, and Budget Entity. These security levels function within the application and are used in conjunction with each other throughout the application.

The following application security data entry transactions should be converted to establish the foundation of the application.

Operator (role) – Establishes the user’s roles within the application and grants access through various switches needed in the programs.

Column and Budget Entity Security - provides the ability to define the access to columns in LAS/PBS by budget entity or group. The column security modules must perform security checks for:

• Display and update access for data within the columns.

• All online transactions and action types – inquiry, correct, add and request.

• All batch programs initiated by JCL.

• All columns types: Budget Entity Narrative, Issue Narrative, Budget Detail, Historical, Personnel, Certifications Forward, and Nonoperating.

Budget Entity Validation – all data entry transactions and report request transactions that have a budget entity field are validated against the Budget Entity Validation Module.

A combination of all three security modules are used at time of signing into the application. Operator security is used to gain access to transactions and budget entities and columns requested in the transaction are protected by a combination of the three security modules.

Security Tables, Transactions and Requests

Tran-ID Description Natural Cobol Mainframe

Map Web OSDx Operator Security X X CSDx Column Security X X

CHDx Column Heading Security X X

TSDx Text Set Security X X x = A (Add), C (Change), I (Inquire), R (Request)

Map Web

CSSR

Column Security Status Request X X

TSSR

Text Set Security Status X X n/a LBR Column Security X X n/a User Preferences X X

3.5.2. Codes and Titles

LAS/PBS is now and should remain a code-driven application. Codes and Titles should be available in tables for use in all reports and on-line transactions.

Budget Tables, Transactions and Requests

Map Web

DFTx Agency / Fund Compatibility X X

ATCx Allocation Transaction Code X X

ACTx Appropriation Category X X

ACGx Appropriation Category Group X X

BETx Budget Entity X X

BGDx Budget Entity Group X X

BGRx

Budget Entity Standard Report Grouping X X

BPTx

Budget Entity / Program Compatibility X X

CFTx

Catalog of Federal Domestic Assistance X X

ECTx EOG Code X X FCTx Fund X X FGSx Fund Group Set X X

FSTx Funding Source Identifier X X

ICTx Issue X X ICGx Issue Group X X

IETx Itemization of Expenditure X X

OCTx Object X X

Tran-ID Description Natural Cobol Mainframe

Map Web

PCTx Program Component X X

RCTx Revenue Code X X SNTx Section X X TABR Table List X X

Personnel Tables, Transactions and Requests

Mainframe

Map Web BBTx Broad Band X X

CBTx Collective Bargaining Unit X X

CLTx DPTx Class Code X X CGTx Class Grouping Code X X

CADx Competitive Area Differential X X

CCTx County Code X X

CPLx

Current Position Standard Lapse Percent X X

HCTx Health Plan X X

LFPx Lapse and Fund Percent X X

OGTx Occupational Group X X DOTx Organization X X PBTx Pay Band X X PGTx Pay Grade X X PPTx Pay Plan X X PSTx Personnel Set X X RPTx Retirement X X

3.5.3. Budget Development

Budget Development provides and should continue to provide the functions necessary to view, and update data required to produce the Agency’s Legislative Budget Request, Governor’s Budget Recommendations, House and Senate Appropriation bills, and the General Appropriations Act.

Data Entry

Map Web

AINx Activity Issue Narrative X X

BNDx Budget Entity Narrative X X

BTDx Bill Text X X BDDx Budget Detail X X

CFPx

Certifications Forward Fixed Capital Outlay Project X X

CFDx

Certifications Forward for C, F Types A, B, C or D X X

CFTx Catalog of Federal Domestic Assistance X X

CPDx Current Position Data X X

HDDx Historical Expenditure Detail X X

INDx Issue Narrative X X

NOPx Nonoperating Budget Detail X X

OADx Other Salary Amount X X

PADx Position Adjustment Detail X X

PINx Priority Issue Narrative X X

PNDx Program Component Narrative X X

Tran-ID Description Natural Cobol Mainframe

Map Web

TFRx

Trust Funds Available Section I – Detail of Revenues X X

TFNx

Trust Funds Available Section II – Detail of Nonoperating Expenditures X X

TFAx

Trust Funds Available Section III – Adjustments X X

TFSx Trust Funds Available X X

TFBx

Trust Funds Available Schedule IB – Detail of Unreserved Fund Balance X X

VBPx Valid Fiscal Year X X

Utilities - Copy, Delete, Move Data

Map Web

ACCR

Activity Column Creation X X

BOIR Backout Issues X X

BNDR

Budget Entity Narrative Copy, Delete, Move X X

BTDR

Bill Text Copy, Delete, Move X X

BDDR

Budget Detail Data Copy, Delete, Move, Reverse X X

BSTR

Budget Detail Source to Target X X

CAFR Calculate and Float X X

CFDR

Certifications Forward Float X X

CPDR

Current Position Data Float X X

Tran-ID Description Natural Cobol Mainframe

Map Web

CPTR

Current Position Table Float X X

CTLR

Comparison Issue Tracking Load X X

FLDR File Load X X

HDDR

Historical Column Float X X

INDR

Issue Narrative Copy, Delete, Move X X

LFFR

Lapse and Fund Percent Float X X

MAFR Merge and Float X X

MCFR

Multi-File Column Float X X

NOFR

Nonoperating Budget Column Copy Move, Delete X X

PCRR

Program Component Reorganization X X

RAFR Roll and Float X X

PGSR

Pay Step Increase Float X X

PLFR

Price Level Index Set Float X X

Downloads and Uploads

Downloads

Map Web

BTSR

Bill Text Download X X

CPRR

Current Position Spreadsheet X X

GENR

Custom Spreadsheet X X

DINR

Issue Narrative Download X X

Tran-ID Description Natural Cobol Mainframe

Map Web

PADR

Position Adjustment Spreadsheet X X

UCSS

Schedule XI- Agency Level Unity Cost Summary Spreadsheet X X x = A (Add), C (Change), I (Inquire), R=Request

Uploads

Map Web n/a Budget Detail Data Upload X X n/a Current Position Data Upload X X n/a Narrative Upload X X n/a Position Adjustment Data Upload X X n/a Statewide Issue Narrative Upload X X n/a

Trust Funds Available – Section I: Detail of Revenues Upload X X n/a

Trust Fund Available – Section II: Detail of Nonoperating Expenditures Data Upload X X x = A (Add), C (Change), I (Inquire), R=Request

Reports

Map Web STAM Saved Reports - Statewide X X

DEPM

Saved Reports - Department X X

EBRR E-Budget Report Request X X USEM Saved Reports - User X X CONM Saved Reports - Conference X X APPR Appropriations Bill X X X GOVR Governor’s Report X X X BTCR Bill Text Comparison X X BPRR Bill Text Project X X GMSR House Bill/Senate Form X X ADRR Activity Detail Report X X EADR Exhibit A, D, and D-3A X X X EXBR Exhibit B X X X ED1R Exhibit D-1 X X X ED3R Exhibit D-3 X X X GENR2 Generic Report X X LBRR Legislative Budget Report X X NARR Narrative List X X NOPR Nonoperating Budget X X OADR Other Salary Report X X X PSCR Personnel Schedule X X X

SC1R

Schedule I – Trust Funds Available X X X

UCSR Unit Cost Summary X X BRAR Base Rate Audit X X BCAR Budget Comparison Audit X X

CHAR

Current Position / Historical FTE Audit X X

PTBR

Position and Rate Ledger Summary Data to BDF Load X X

PPAR

Pay Package Competitive Pay Adjustment X X

GARR Generic Audit Report X X

Tran-ID Description Natural Cobol Mainframe

Map Web

NACR

Negative Appropriation Category X X X

RPAR Requested Position Audit X X CFRR Certifications Forward X X X CFFR C.F. Fixed Capital Outlay X X X CFOR C.F. Operations Detail X X X ATFR Annual Trust Fund Report X X FDAR CFDA Summary X X

TFBR

Detail of Unreserved Trust Fund Balance X X X

RCRR Revenue Cap Report X X TFAR Trust Fund Adjustment X X X TFDR Trust Fund Expenditures X X X

Audit / Update

Map Web ANNR Annualization X X BRAR Base Rate Audit X X

CPFR

Current Position Forced Recalculation X X

CSIR Calculate Salary Increase X X CTCR Calculate Cost to Continue X X NAAR Narrative Audit X X

NACR

Negative Appropriation Category X X

NRIR Nonrecurring Issues Load X X

PAFR

Position Adjustment Forced Recalculation X X

PAYR Pay Package Transactions X X RALR Rate Alignment X X RPAR Requested Position Audit X X

Other Functions

Map Web

BISR

Budget Information System Load X X

BPMR

Budget Preparation File Maintenance X X

CFLR

Carry/Certifications Forward and Expenditures Data Load X X

COPx Current Position Load File Status X X

COPR

People First / SUS / Legislative File Edit and Load X X

COTR

People First / SUS File Load Tables X X

DUPR Duplicate Titles Table List X X FBRR File Backup Restore X X FBUI System Control File Status X X FBUR File Backup X X INRR Issue Narrative Replication X X LIFR Line Item File X X LTRR Lock Table Processing X X MESx Message Explanation X X

NBRR

Nightly Backup Restore Request X X

NEWx News X X NQTx Narrative Queue X X

PFBx Personnel File Backup and Status X X

PFRR Personnel File Restore X X PLIR Price Level Increase X X PLLx Price Level Index Lock X X DCDR Download Column Data X X SEFx Serious Error File X X

TD1R

Training Database Codes and Titles X X

TD2R

Create and Load Training Data X X

TD3R Maintain Training Data X X

TFVx Transparency Florida Variables X X

TQTC Bill Text Queue X X TRNx Transaction Status and List X X X

Tran-ID Description Natural Cobol Mainframe

Map Web

TYSR

Ten Year Summary Spreadsheet Download X X

UFFR

Unreserved Fund Balances Load X X

UPDR Upload Data File X X WHSR LAS/PBS Warehouse Load X X WIRR Warehouse Information X X

3.5.4. Budget Allocation

The Budget Allocation Component provides and shall continue to provide the functions to view, update and report data in the Appropriations Ledger and the Position and Salary Rate Ledger. The ledgers are used and shall continue to be used to maintain and execute the budget, including positions and salary rate.

Data Entry

Map Web

ALDx Appropriation Ledger Detail X X

ALSx Appropriation Ledger Summary X X

PLDx Position and Rate Ledger Detail X X

PLSx Position and Rate Ledger Summary X X

QRDx Quarterly Release X X

QRXC

Special Quarterly Release X X

VFYx Valid Fiscal year X X

Reports

Map Web

ALRR

Appropriation Ledger Summary X X

PLRR

Position and Salary Rate Ledger X X

QRRR Quarterly Release Plan X X

Downloads and Upload

Downloads

Map Web

AL2R

Appropriation Ledger Spreadsheet X X

PL2R

Position and Rate Ledger Spreadsheet X X

Uploads

Map Web

N/A Appropriations Ledger Detail Data Upload X X

3.5.5. Special Functions

Map Web

ALDR

Appropriation Ledger Detail Update X X

ALGR

Appropriation Ledger Generic Batch Input X X

ALPR

Appropriation Ledger Posting X X

ALBR

Appropriation Ledger Reconciliation X X

Tran-ID Description Natural Cobol Mainframe

Map Web

ALTR

Appropriation Ledger Transfer X X

ATBR

Appropriation Ledger Summary Data To Budget Detail X X

BAAR Budget Allocation Audit X X

BAMR

Budget Allocation File Maintenance X X

QRDR

Quarterly Release and Post Data X X

3.5.6. Other Processes

The following processes and functions are used in the current application. These functions will need to be converted and available in the new solution.

• Real-time visibility and monitoring of users

• Session Admin functionality

• XML Validator functionality

• Nightly/Daily Backup jobs (databases, files, libraries and objects)

• Nightly/Daily Transparency Florida Load

• Nightly/Daily Codes and Titles for FLAIR/PALM

• Nightly/Daily Appropriation Ledger Reconciliation Request

• Nightly/Daily file clean up and reports

• Weekly and Monthly jobs (People First, Warehouse, Auditor General)

• Restore database, individual files and specific columns

• Transparency Florida (F*)

• Warehouse Load

• People First / SUS Legislative File Edit and Load

LAS/PBS Hardware Environment

The following information is intended to describe the current working environment for the LAS/PBS application. This information can be used by the Contractor when determining the hardware needs of the new application.

Mainframe Physical Hardware The mainframe hardware consists of 4 boxes including the Production CPU, Disaster Recovery CPU, Disk Store Drive and Virtual Tape Storage Drive. Below is the list of the hardware and the description of each. The Department of Financial Services houses and maintains all hardware that runs the mainframe environment for LASPBS.

Make Model Description IBM 2965-M04 Mainframe/CPU

MIPS Rating = 148SUs / 1193

MIPS

IBM 2965-M04 Disaster Recovery Mainframe/CPU

IBM 3390-M27 Disk Storage Drive IBM 3390-M27 Virtual Tape Storage Drive

LAS/PBS Mainframe Physical Storage The amount of physical storage currently required for LAS/PBS databases and supporting files and libraries is outlined below. These databases, supporting files and libraries are all stored on the mainframe hardware and represented as disk storage.

LAS/PBS Database Disk Space

• Adabas data for the LAS/PBS application requires a total of 56GB of disk storage evenly divided into four environments

• Database environments have been created for Production, Test, Development and a Sandbox

• Each database environment contains three components o Data storage contains the raw data in compressed format and is allocated approximately 8.5GB of disk storage o Associator contains information about data relationships and is allocated approximately 4.5GB of disk storage o Work Area contains a data protection area and temporary storage for intermediate results during complex operations and is allocated approximately 850MB of disk storage

Load Libraries, Program Libraries and JCL Libraries

• Adabas Database load libraries – 68MB

• Natural load library – 298MB

• Program library (batch & online) - 85MB

• Miscellaneous load libraries – 425MB

• Job Control Libraries (JCL) libraries – 85MB

• Cobol Libraries – 255MB

Backups, File FTP and Spreadsheet processing

• Adabas Database Backups – 4 database backups each at 5GB, 10 daily backups kept and 70 weekly backups kept. Session backups are permanent;

• Space for backups of files and libraries (single database files, Natural objects) –

850MB

• File FTP - 1.2GB of compressed data

• Spreadsheet processing – 1.7GB

• Cobol libraries backup – 255MB

• Miscellaneous disk storage (temp files for batch, sort space, files received/send via ftp) - 4.3GB

LAS/PBS Software Environment

Software solution proposed by the Contractor to replace the existing products will require approval in writing from the LAS/PBS contract manager.

This section describes the software used to maintain and operate the LAS/PBS mainframe application. Included are the mainframe systems software as well as SoftwareAG and Treehouse proprietary software as follows:

• Mainframe Operating System Software and software used to support all functions of developing, maintaining and executing the LAS/PBS application and services on the mainframe; and

• Mainframe LAS/PBS Software and Services (by SoftwareAG and Treehouse) which are used to develop, maintain, integrate and execute the LAS/PBS application on the mainframe.

Mainframe Operating System Software (and Software supporting necessary functions for the LAS/PBS application)

The following IBM software is used by DFS on the IBM mainframe. DFS data center staff manage and support this software.

Name Version Purpose z/OS Operating System z/OS 2.4 Mainframe Operating System SDSF Included in the OS System Display and Search Facility.

Utility that allows you to monitor, control, and view output of jobs.

DFSORT Included in the OS High performance sort, merge, copy analysis and reporting.

ACF/VTAM Included in the OS Advanced Communications for Virtual Access allowing programs to read/write data to/from external devices.

ISPF/PDF Included in the OS Interactive System Productivity Facility (ISPF) and Program Development Facility (PDF). Includes text editor and browser, functions for locating and listing files and performing other utility functions after logging on to TSO.

JES2 Included in the OS Job Entry Subsystem. Provides supplementary job management, data

Name Version Purpose management and task management functions such as scheduling, control of job flow and spooling.

LE Included in the OS Language Environment for z/OS.

System of constructs and interfaces that provides a common runtime environment and runtime services.

RMF Included in the OS Resource Measurement Facility.

Gathers data about z/OS resource usage and provides reports for performance management.

TCP/IP Included in the OS Transmission Control Protocol/Internet Protocol. Communication facility that permits bidirectional communication between mainframe software and software running on other TCP/IP platforms.

TSO Include in the OS Time Sharing Option. Provides single-user logon for interactive session and command prompts through the menu-driven interface ISPF.

Quick Reference (MVS) 8.4 Provides rapid descriptions of the meanings of messages issued by z/OS-based products.

EOS360 / RDSJOBS 1.6 EOG360 (terminal version) and EOSAccess (web version). Report Management and Distribution System.

Printing, storing and distributing large quantities of data.

VPS – VTAM Printer Support

2.2 VTAM Printer Support. Retrieve JES

spool files for processing.

VRA / RACF 2.3 Resource Access Control Facility.

Provides the tools to manage user access to critical resources.

CA1 – Tape Management System

14.0 Provides tape library management, automation and protection.

CA11 – Job Tracking 11.0 Automated rerun and tracking system.

CA11 is designed to perform as a Run Handler and as a Job Tracking System or combination of both.

CA7 – Job Scheduler 11.3 Production control system. Online, real-time, interactive system which automatically controls, schedules jobs

Name Version Purpose based on the date and time, job dependencies and available resources.

CICS TS 5.5 Customer Information Control System Transaction Server. Mixed-language application servers that provide online transaction management and connectivity for applications on IBM mainframe.

COBOL 3.3 Enterprise Common Business Oriented Language (Cobol) compiler.

CA Disk 12.5 Data / Storage / Hierarchical Management. Automatic way of managing and distributing data between the different storage layers and facilitates accessing data.

FOCUS 770 Functional Coverage Unified Solution.

Advanced test planning tool for improving the testing of an application.

IOF 8G Interactive Output Facility.

Management of JES2 resources (jobs, devices, syslog, data indexing).

Bluezone FTP 10 Used for FTP to and from the mainframe.

Attachemate / TN3270 9.3 Users and IT staff utilize to for application use as well as develop and maintain the application. Used for FTP to and from mainframe.

Mainframe LAS/PBS Software

SoftwareAG (and Treehouse) software is used for the development and maintenance of the LASPBS application.

Name Version Purpose

ADABAS 8.4.2 SoftwareAG Adaptable Data Base System running on IBM mainframe. The non-relational LASPBS database made up of tables which can have multiple data relationships within a table (rows represent data records and columns represent fields and separate files can be linked logically by a common field).

AOS 8.4.2 SoftwareAG Adabas Online System. Interactive menu-driven analysis and control facility for Adabas and related

Name Version Purpose environments. Provides many features including ability to display/monitor/modify/control access for Adabas users, fields and files.

PREDICT 8.4.2 SoftwareAG Predict. Is an active data dictionary system for storing and maintaining what data is stored and where, reflects the information structure, which processing objects work with the data and who creates data and/or objects that process the data.

ACF 8.4.3 SoftwareAG Adabas Caching Facility. Helps improve system performance and make full use of ESA functions by augmenting the Adabas buffer pool in extended memory, data space, hyperspace and, 64-bit virtual storage.

NATURAL 8.2.8 SoftwareAG 4GL Natural programming language.

Applications developed using Natural are modular, which contributes to its success as a tool for Rapid Application Development. In general, each module is created, maintained and stored independently of any others.

Utilities we use that are included with Natural are EDIT/Natural Editor (edit/save/stow Natural objects), SYSMAIN (object transfer), SYSBPM (buffer pool management), SYSCP (code page maintenance), NATRJE (remote job entry), SYSEDT (editor buffer pool), SYSERR (error message management), SYSNCP (direct commands

– maintenance and runtime), SYSPARM (maintain Natural profile parameters), SYSTP (Natural cics monitor and details), NATPAGE (capture screen output data), SYSOBJH (object handler).

NCI 8.3.5 SoftwareAG Natural CICS Interface (NCI). The Natural CICS Interface controls session initialization, roll-in restart (in pseudo-conversational mode), terminal I/O, database access, ABEND processing, Natural local buffer pool calls and the loading, linking to and releasing of external subroutines. In addition, all roll I/O operations are made from the Natural CICS Interface.

NDV 9.1.1 SoftwareAG Natural Development Server. Natural Development Server enables the use of NaturalONE development environment provided by Natural for Windows to develop and test Natural applications in a remote Natural mainframe. NaturalONE is a SoftwareAG software meant to be a single point of development on the client side.

Entire System Server / NPR

3.6.3 SoftwareAG Entire System Server / NPR. The Entire

System Server makes operating system information and

Name Version Purpose system services available to an application developer.

We use this primarily for report output creation and display (e.g. READ-FILE, WRITE-FILE, SPOOL-QUEUE).

EntireX 10.5 SoftwareAG EntireX. This is an application integration software to enable integration of Windows clients with mainframe system, packaged systems (Software AG products) and also with Web services. This supports our existing LASPBS web application.

TRIM 8.4.2 TRIM by Treehouse. Performance monitor for Adabas and Natural developed by Treehouse Software, Inc. (TSI).

Provides on-line and batch statistics about Adabas and Natural use and performance. TRIM has a Real-Time Monitor (RTM) that provides more than 300 on-line performance statistics showing Adabas activity by user, minute, job, and program; and a batch facility that provides total resource utilization statistics from summary or detail log data.

Following are the counts of existing databases and objects:

• Total of four (4) Adabas databases with 102 – 120 files each;

• Total of 2,196 Natural programs;

• Total of 740 Natural subprograms;

• Total of 237 Help Routines;

• Total of 1,240 Help Maps;

• Total of 876 Maps;

• Total of 23 Local Data Areas and 3 Global Data Areas;

• Total of 269 Copy Codes;

• Total of 337 Natural Libraries;

• Total of 265 Cobol objects;

• Total of 166 Copy Books;

• Total of 1,002 production JCL members;

• Total of 86 User Libraries;

• Total of 1,126 datasets;

• Total of 1,377 production datasets;

• Total of 1,987 temporary datasets; and

• Total of 3,477 GDG datasets.

4. Project Deliverables

The following sections identify the deliverables by each phase of this project. The deliverables listed must be required under this proposal. The Contractor’s proposed deliverables must include the LAS/PBS deliverables listed herein Attachment A, Scope of Services. Each deliverable must be tested and accepted by the EOG. Payment for each deliverable will be completed when all items are successfully tested and accepted by LAS/PBS.

Project Initiation

4.1.1. LAS/PBS Responsibilities

The application is currently maintained by SDD. SDD will provide the awarded Contractor with the following:

• Access to its technical resources, as needed, to explain code and answer technical questions.

• Requirements documentation.

• All data contained in the system.

• All source code (Natural, CICS, Cobol, VB.Net, Services) currently utilized by the application.

• LAS/PBS Web current coding conventions and standards.

• Database design documentation detailing the structure of the database within

Adabas and Oracle.

• Complete set of test data to allow development of conversion strategies.

• Access to conduct the LAS/PBS application assessment and a baseline performance assessment.

4.1.2. Contractor’s Responsibilities

The awarded Contractor should provide a project kickoff presentation within 30 days of contract execution. The presentation should include the following elements:

• Introduction – Contractor explanation of the project purpose, scope, assumptions, constraints, schedule, resources, and risks to insure they align with the Statement of Work.

• Proposed Timeline – Start dates, end dates, tasks, dependencies and critical path.

• Project Delivery Methodology – Design-build, fast track, scrum or agile.

• Project Management Tool Access – Contractor’s proposed tools and access for reporting, documentation and collaboration. Contractor will be responsible for providing SDD project staff with access to the tools and documentation.

4.1.3. The Contractor should conduct and present the LAS/PBS application assessment and baseline performance assessment.

4.1.4. The Contractor should provide a certified Project Management Professional (PMP) to lead the project. The Contractor and Agency should notify the other party of any requests to replace the PMP within 30 days of replacement. The Agency’s Contract Manager must approve all changes before the replacement is final.

4.1.5. The Contractor should provide proof of insurance and process for virus and rasomware prevention and protection.

Project Planning Phase

The following items within the Project Planning Phase section must be delivered by the

Contractor and approved by LAS/PBS contract manager during the planning phase of the project.

4.2.1. Project Management Plan

• Scope of Work – What is in-scope and what is out-of-scope.

• Assumptions and Constraints – Detail assumptions and limitations.

• Approved Timeline - The approved timeline will include scope of work, tasks, effort, resources, begin and end dates, dependencies and critical path. Any proposed changes to the approved timeline must be authorized by the LAS/PBS contract manager.

• Work Breakdown Structure – Identify the hierarchical and incremental decomposition of the tasks to deliver each milestone of the project. The LAS/PBS milestones listed in Section 9, Milestones, should be included in the Contractor’s Work Breakdown Structure.

• Project Performance Measures – Measures to be monitored and reported throughout the project and will be used to determine if the project objectives have been met.

• List of Project Deliverables – Includes both project management and application specific deliverables.

• Communications – Documenting the responsibility, frequency, type and audience for ongoing project communications. This will include a repository for all project documents, approvals and communications throughout the life of the project.

• Project Status Report – Details the structure, information, format, frequency and location for all status reports.

• Project Meetings – Details the types, frequency, facilitator, participants, responsibilities, documentation/minutes and follow up action items.

• Change Management – How change requests between approved Contractor and LAS/PBS contract manager will be initiated, documented, assessed, escalated, approved, tracked and executed.

• Quality Management – How quality will be managed, deliverables produced and what elements define quality in the deliverables and project execution.

• Risk and Issues Management – How risks and issues will be reported to the LAS/PBS contract manager and subsequently monitored, maintained and acted upon throughout the project.

4.2.2. Solution Design

• The solution design document should reflect the conversion of the LAS/PBS application from the current environment to the desired newer technologies making no changes to functionality or screen design.

• The solution design document should include the following:

o System overview including a description and diagram;

o Oracle Database design (includes structure, schema, data dictionary and map);

o Migration strategy details for moving Adabas database data to Oracle;

o Replacement software list with version and proof of commercial availability and licensing;

o Replacement hardware list with version and proof of commercial availability and licensing;

o Detailed code conversion process and methodology (manual rewrite, augmentation, automated refactoring utilites).

o Requirements traceability matrix which maps the (provided) SDD requirements to the transaction code conversion tasks.

o Solution and strategy for remediating changed LAS/PBS application code occurring throughout the project timeline into the new converted LAS/PBS application;

o Solution and design for the converted LAS/PBS application and database scalability to accommodate the high and low demands of the annual budget cycle;

o Solution and design for required infrastructure security;

o Include in the Solution Design plan the disclosure and commitment by the

Contractor that all materials and intellectual property utilized and created by the Contractor to convert the LAS/PBS application and infrastructure will remain the sole and exclusive property of the State of Florida.

o Include in the Solution Design plan the disclosure and commitment by the Contractor that the final LAS/PBS product inclusive of all materials and services as the result of this conversion will remain the sole and exclusive property of the State of Florida.

o Solution and strategy for disposition of all LAS/PBS data, programs, scripts and other items developed by the Contractor for this project after transition to SDD;

o System organization;

o System integration plan;

o Assumptions; and o Constraints.

4.2.3. Disaster Recovery and Failover Plan

• The disaster recovery and failover plan should include the infrastructure solution for restoring the system to operation and must be reviewed and approved by the LAS/PBS contract manager.

• The disaster recovery and failover plan should include the steps required to restore the system to operation and must be reviewed and approved by the LAS/PBS contract manager.

• The disaster recovery and failover plan should describe data loss prevention and data recovery methods used to meet current capabilities (recover database, individual files and individual columns) and shall be reviewed and approved by the LAS/PBS contract manager.

• The disaster recovery and failover plan should include the comprehensive test plan and procedures that will be used and validated on an annual basis.

4.2.4. Test and Validation Plan

• The project test plan document should include the plans and timelines for the following tests and shall be reviewed and approved by the LAS/PBS contract manager:

o Data Verification and Validation;

o Contractor Unit and System Testing (Contractor shall test and correct all converted data and code prior to releasing to SDD for testing);

o Unit Testing;

o Functional Testing (includes requirements traceability matrix);

o Integration Testing;

o System Testing;

o Security Testing;

o Business Cycle (end to end) Testing;

o User Acceptance Testing;

o Load and Performance Testing;

o Defect Management (Tracking and Resolution of issues found); and o Disaster Recovery and Failover Testing.

• The project test plans must outline Contractor and SDD staff who are responsible for testing the application.

• The project test plan should include a process used to report errors discovered during SDD system testing and Contractor’s resolution response.

• Final testing shall include the confirmation that requirements have been fulfilled using the requirements traceablility matrix.

• Final testing sign off and approvals are to be completed by the LAS/PBS contract manager.

• The Contractor at this stage, must provide the cloud environment where SDD will perform acceptance testing.

4.2.5. Code Review and Approval Plan

• Should include that requirements have been fulfilled most likely utilizing the requirements traceablility matrix.

• Should provide an Operations and Maintenance Plan that documents the process for the operation and maintenance of the LAS/PBS application and services and must be reviewed and approved by the LAS/PBS contract manager.

• Should provide the details for a training plan and associated operations guide and training documentation for SDD staff.

• The code review and approval plan should include the details for handing over the new application and infrastructure to SDD and must be reviewed and approved by the LAS/PBS contract manager.

• The code review plan should include the timelines and resources.

4.2.6. Go Live and Rollback Plan

• Should include the detailed implementation plan with schedule, tasks, resources, predecessors and dependencies for both go live and rollback plans.

• Should include the process and criteria for evaluating the “Go or No-Go” decision.

• Should include the production readiness process for go live.

• Should provide a plan that includes a valid rollback and mitigation if go live implementation fails that must be reviewed and approved by the LAS/PBS contract manager.

4.2.7. Non-Production Environment for Development and Testing Plan. All plans must be reviewed and approved by the LAS/PBS contract manager.

• Should provide a plan that outlines establishing and maintaining a development and test environment that mimics a true projection of the production environment.

• Should provide the strategy for a development and test environment populated with the LAS/PBS application framework and converted Oracle database.

• Should provide a plan for SDD staff accessibility to the development and test environments to review code, database data and design and documentation to effectively manage the project.

• Should provide a plan that outlines the use of on premise Azure DevOps for the requirements repository.

• Should provide a plan that outlines the use of on premise Azure DevOps for the test scripts repository.

• Should provide a plan that outlines the use of on premise Azure DevOps for the code repository for development and test environments.

4.2.8. LAS/PBS Adabas to Oracle Database Conversion Plan. All plans must be reviewed and approved by the LAS/PBS contract manager.

• Should provide a database conversion plan that includes the current LAS/PBS

Web Oracle design using the Adabas Column approach.

• Should provide a plan that bases the new LAS/PBS Oracle database table structure on the Adabas database structure and concepts.

• Should provide a plan that involves all LAS/PBS Adabas data being converted and migrated to the new Oracle database.

• Should provide a plan that includes all data converted and migrated to the new

Oracle database to be validated and verified against the current LAS/PBS Adabas data.

• Should provide a plan that includes the converted database in development and test environments to be a true projection of the production environment.

• Should provide a plan that outlines SDD’s ability to administer converted databases in the production, test and development environments.

• Should provide a plan that details the approach to confirm that the converted database has been tuned for performance equal to or better than the current LAS/PBS Adabas database.

Project Execution and Control Phase

4.3.1. Should conduct and deliver project meetings, agendas, minutes and status reports as agreed in the Project Management Plan.

4.3.2. Should implement all project deliverables as per the Project Management Plan (Scope, WBS, Performance, Communications, Change Management, Schedule, Quality, Resource, Procurement, Risks and Issues).

4.3.3. Should implement all project deliverables based on the Project Schedule and Timeline Plan.

4.3.4. Should implement all project deliverables following the requirements in the Non- Production Environment for Development and Testing Plan.

4.3.5. Should deliver replacement software as defined by the Solution Design document.

4.3.6. Should deliver replacement hardware as defined by the Solution Design document.

4.3.7. Should deliver converted database as defined by the Solution Design document and

Database Conversion Plan.

4.3.8. Should deliver converted code, application and services as defined by the Solution

Design document and the Code Review and Approval Plan.

4.3.9. Should deliver converted code, application and services as per scope outlined in section 3 (Scope of Work). Each deliverable as indicated below must be handed over to SDD in a sequential manner for testing and acceptance. Only when the individual deliverable is approved by the LAS/PBS contract manager, may the Contractor proceed to handing over the next one. The individual deliverables are:

i. Non-Production Environment (3.2);

ii. Database Conversion (3.1);

iii. Application Framework (3.4);

iv. Application Security, Codes and Titles and Budget Development

Downloads (3.5.1, 3.5.2, 3.5.3.3);

v. Budget Development Data Entry (3.5.3.1);

vi. Budget Development Utilities (3.5.3.2);

vii. Budget Development Uploads (3.5.3.3) and Reports (3.5.3.3, 3.5.3.4);

viii. Budget Development Audit/Update (3.5.3.5);

ix. Budget Development Other Functions (3.5.3.6);

x. Budget Allocation Data Entry (3.5.4.1);

xi. Budget Allocation Reports (3.5.4.2);

xii. Budget Allocation Downloads and Uploads (3.5.4.3);

xiii. Special Functions (3.5.5);

xiv. Other Processes (3.5.6).

4.3.10. Should deliver converted code, application and services in the order and approach as agreed in the Project Schedule and Timeline Plan.

4.3.11. Should deliver converted code, application and services integration as defined by the Solution Design document.

4.3.12. Should deliver converted code, application and services for SDD testing and acceptance as per the agreed Test and Validation Plan.

4.3.13. Should deliver a tested and proven Disaster Recovery and Failover process as defined by the Disaster Recovery and Failover Plan.

4.3.14. Should implement a successful Go Live of the LAS/PBS application and services with a tested and proven Rollback as defined by the Go Live and Rollback Plan.

4.3.15. Should implement a successful Go Live of the converted LAS/PBS application and services in a cloud infrastructure as defined by the Solution Design document.

4.3.16. Should monitor, manage and update the Azure…