PDF of 2017-2019 Budget Guidelines for Toolset Upgrades

The ITD Software Development Division supports many software development tools and languages.  ITD upgrades to new versions of our tools and languages on a regular basis.  This maintains a strong security posture and prevents obsolescence of customer applications.  Upgrades generally involve re-compiling applications using the newest version of the tool or language, then unit testing the application.  The time required to upgrade varies, depending on the tool being upgraded and the severity of the upgrade.

Following is a list of software components that will likely need upgrades in the 2017-2019 biennium.  We’ve provided a budgeting estimate of the average time required to upgrade each tool and language.  We ask that customers budget for the anticipated number of upgrades per biennium.  Please contact your Software Development team leader to determine which of these technologies you may use.

Software Component

Anticipated Number of Upgrades in 2017-2019 Biennium

Number of Hours per Upgrade

PowerBuilder

1

32 hours per Application

DB2

1

32 hours per Application

Adabas

1

32 hours per Application

Oracle

1

12 hours per Application

SQL Server

1

12 hours per Application

InfoSphere Change Data Capture

1

40 hours per Application

WebSphere

1

40 hours per Application

.Net

1

16 hours per Application

Ionic Framework (mobile development)

1

24 hours per Application

Cobol

1

16 hours per Agency per upgrade

Natural

1

16 hours per Agency per upgrade

Drupal

8

4 hours per Website

Address Verification Tools

24

2

1 hours per Upgrade – Files

8 hours per Upgrade – Version

AEM (Adobe Experience Manager)

2

2 hours per published form

ILINX Capture

2

2 hours per profile

Software Component

Anticipated Number of Upgrades in 2017-2019 Biennium

Number of Hours per Upgrade

ILINX Email Import

2

2 hours per profile

ILINX Automated Report Management (ARM)

2

2 hours per profile

FileNet Case Foundation (BPM)

4

Effects estimated to be minimal

FileNet Content Foundation (Content Manager)

4

Effects estimated to be minimal

FileNet eForms

0

eForms are being phased out

FileNet Department Applications

4

2 hours per .net Application

FileNet Department Applications

4

2 hours per Java application

CONNX

1

12 hours per Application

Crystal Reports

1

2 hours per Report

Crystal Reports Enterprise

1

24 hours per Application

Cognos Reports

4

4 hours per Report (fix packs included)

Cognos Transformer

4

4 hours per cube (fix packs included)

DataStage (ETL)

1

16 hours per Application

SSIS (ETL)

4

 4 hours per Application (fix packs included)

Informatica

1

16 hours per Application

Master Client Index (Initiate)

1

80 hours per Application

Job Scheduler (UC4)

1

8 hours per Agency

Security Vulnerability Discovery

2

32 hours per Application

Security Vulnerability Remediation

2

Requires estimate - dependent on vulnerabilities