Appendix_A_Current_Environment_.pdf

PDF 77 KB Posted

Attached to
Request for Proposal for Hosting Services
Solicitation number
2023-RFP-058
Issued by
Cuyahoga County, Ohio

About this file

This document is Appendix A: Current Environment, detailing the existing infrastructure for the Cleveland Water Department's (CWD) Oracle Customer Care and Billing (CC&B) system. The document provides a comprehensive overview of the current technology environment, including user counts, system configurations, and technical specifications for the billing platform. DPU currently has approximately 339 total users across Water, Wastewater, and CPP services, with multiple environments including Development, Testing, Production, Training, and Disaster Recovery.

The current CC&B infrastructure is hosted off-site by Utilities Solution Partners LLC, utilizing Oracle Enterprise Linux, Oracle Database 19.18, and WebLogic, with a total of 16TB of data storage. The production environment consists of 6 CC&B instances spread across 4 servers, with high availability using Oracle Real Application Cluster (RAC) and a disaster recovery setup in active-passive mode. The system supports monthly billing processes, operates primarily during business hours of 7:30 AM - 6:30 PM, and uses TCP/IP network protocol with SFTP for data transmission. The servers are hosted on OCI cloud, with varying memory configurations ranging from 46GB to 190GB and total core counts between 3-7 OCPUs across production, non-production, and disaster recovery environments.

View the file

Other files

On GovTribe

Work with this file

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

Text version

APPENDIX A: CURRENT ENVIRONMENT

Scoping Parameters

Parameter Description Number of Primary Users, est. 300 for Water. 21 for Wastewater and 65 users for CPP.

Number of Total Users, est. 339 for Water. 21 for Wastewater and 65 users for CPP.

Number of Environments to be Supported

• Development 1

• Development 2

• Testing 1

• Testing 2

• Production

• Training

• Disaster Recovery

Billing History We currently have approximately 15 years of history in CC&B. Over time, DPU plans to keep a minimum of 10 years of history in

CC&B

Billing Frequency We currently bill customers monthly. Bills are produced every business day.

Business Hours 7:30 AM - 6:30 PM for customer service. A small number of users will need 24 x 7 access.

Network Protocol TCP/IP Data file transmission method SFTP or similar secured method Client Desktop environment Windows 7and 10. Edge and Google

Chrome (Browsers need to be supported with latest versions applicable)

DPU will provide:

• Communication link to the hosting provider’s router and management of the communication link between the hosting provider’s router and the DPU router.

• Network gateway hardware located at DPU

• Client side hardware and software

• DPU LAN

Oracle Customer Care and Billing (CC&B) Currently on version 2.7.0.3.0, DPU implemented CC&B version 2.1.0 in 2009.

CC&B is CWD’s billing system and handles most aspects of customer billing information which includes billing, payments, rates, collections, field service, meter reads, and meter management.

The CC&B infrastructure, application, and databases are hosted off-site currently by a managed hosting vendor. Currently the managed services for this application are provided by Utilties solution Partners LLC. They provide mainly on-site support with some off-site support.

DPU uses the following CC&B software stack:

• CC&B version V2.7.0.3.0.

• Operating System: Oracle Enterprise Linux version 7.9

• Oracle Database 19.18.0.0.0 with mulittentant.

• Web Application: Web Logic version 12.2.1.4.0

• Batch Scheduler: Tivoli Workload Scheduler version 9.5

• Java JDK 1.8.0

• Windows 2019 (64-bit)

Environments:

• Production o DPU has 6 Instances of CC&B in prod from which 4 are online and

2 are batch. Production environments are spread across 4 servers 2 for batch and 2 for online. We have high availability using Oracle Real application cluster (RAC) with two nodes cluster. In the case of production database server crash the Oracle datagaurd solution that will fail over to DR site. It is an active passive mode.

• Non-Production Environments o DPU CC&B non production environment consists of two online server, Two batch server, and two database servers , databases are hosted in Oracle RAC with 2 nodes for high availability. It also includes the batch scheduler IBM TWS 9.5 single instance installed on the development batch server 4 Testing Environments 1 Development Environment 1 Training Environment o Disaster Recovery - The DR setup has one online server with 2 CC&B instances, one batch server with one instance, and one database server

• Storage o CC&B currently utilizes 16TB of data across all environments

• Servers - CC&B hosted at OCI cloud

• Billing Frequency: Customers are billed monthly. Bills are produced every business day

• Business Hours: Primary business hours for customer service are 7:30 AM

- 6:30 PM Monday through Friday. A small number of users will need 24x7 access.

• Network Protocol: TCP/IP

• Data file transmission method: SFTP or similar secured method

• Current Infrastructure environment:

Product Name Server Type Memory (in

GB)

Total Core

(OCPU)

Total Storage (in

GB)

DB1 - RAC Prod 96 6 500

DB2 - RAC Prod 96 6 500

Web Application Server 1 Prod 64 6 310 & 64

Web Application Server 2 Prod 64 6 310 & 64

Batch 1/TWS Server Prod 64 3 409 & 64

Batch 2 Server Prod 64 3 409 & 64

Dev DB RAC 1 Non - Prod 46 3 500

Dev DB RAC 2 Non - Prod 46 3 500

Dev Web Server Non - Prod 64 4 310 & 64

TEST DB RAC 1 Non - Prod 46 3 500

TEST DB RAC 2 Non - Prod 46 3 500

TEST Web Server Non - Prod 64 3 309 & 64

TEST Batch TWS Server Non - Prod 64 3 409 & 64

DR DB Server Disaster Recovery 190 7 5100 & 64

DR Web Server Disaster Recovery 64 6 160 & 64

DR Batch TWS Disaster Recovery 64 3 160 & 64

APPENDIX A: CURRENT ENVIRONMENT
Oracle Customer Care and Billing (CC&B)

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