STATE OF FLORIDA · 2012. 2. 28. · STATE OF FLORIDA – DEPARTMENT OF CHILDREN AND FAMILIES...

STATE OF FLORIDA DEPARTMENT OF CHILDREN AND FAMILIES

FAMILY AND COMMUNITY SERVICES

CURRENT TECHNICAL ARCHITECTURE FOR

FLORIDA SAFE FAMILIES NETWORK APPLICATION SERVICES

ITN# - 01U12AP1

STATE OF FLORIDA – DEPARTMENT OF CHILDREN AND FAMILIES 1/31/2012

ITN #01U12AP1 – FLORIDA SAFE FAMILIES NETWORK APPLICATION SERVICES Page ii

TABLE OF CONTENTS SECTION 1. BACKGROUND AND FUNCTIONAL OVERVIEW .................................................................................. 1

1.1 Background ............................................................................................................................................................. 1

1.2 Program or Service Specific Terms............................................................................................................... 1

1.3 Functional Overview ........................................................................................................................................... 2

SECTION 2. FSFN ARCHITECTURE ................................................................................................................................... 4

2.1 Application Framework ..................................................................................................................................... 4

2.2 Architecture Layers ............................................................................................................................................. 5

2.3 Mobile Architecture .......................................................................................................................................... 13

2.4 FSFN Hardware and Software Configuration ......................................................................................... 17

2.5 FSFN – DCF Network Diagram ..................................................................................................................... 19

SECTION 3. REPORTING AND DATA WAREHOUSE ARCHITECTURE .............................................................. 20

3.1 FSFN Data Warehouse Design Overview .................................................................................................. 21

3.2 Software and Tools ............................................................................................................................................ 25

SECTION 4. PERFORMANCE TESTING .......................................................................................................................... 27

SECTION 5. BATCH JOBS ..................................................................................................................................................... 28

5.1 Batch Framework ............................................................................................................................................... 28

5.2 Back up routines ................................................................................................................................................. 29

SECTION 6. INTERFACES .................................................................................................................................................... 30

6.1 Adoption and Foster Care Analysis and Reporting System (AFCARS) Interface ..................... 31

6.2 Adoption Exchange System (AES) Interface ........................................................................................... 31

6.3 Community Based Care (CBC) Fiscal Agency Accounting System Interface .............................. 31

6.4 Child Support Enforcement (CSE) Interface ........................................................................................... 31

6.5 Department of Health (DOH) Interface ..................................................................................................... 31

6.6 Florida Online Recipient Integrated Data Access (FLORIDA) System Interface ...................... 32

6.7 Hotline Phoenix System Interface ............................................................................................................... 32

6.8 National Child Abuse and Neglect Data System (NCANDS) Interface .......................................... 32

6.9 National Youth and Transition Database (NYTD) Interface ............................................................. 32

6.10 RDC - Mobility Applications ........................................................................................................................... 32

6.11 Checkprint/Checkwrite – Financials.......................................................................................................... 33

EXHIBIT A – Key Statistics ................................................................................................................................................. 35

EXHIBIT B – Desktop Configurations ............................................................................................................................ 38

EXHIBIT C – FSFN Batches ................................................................................................................................................. 40


ITN #01U12AP1 – FLORIDA SAFE FAMILIES NETWORK APPLICATION SERVICES Page 1

SECTION 1. BACKGROUND AND FUNCTIONAL OVERVIEW

1.1 Background The Florida Safe Families Network (FSFN) application is designed and developed to meet the State of Florida’s requirements for a child welfare system and meet Federal reporting requirements for child protection, foster care and adoption. The FSFN application automates casework practice and integrates client, service, financial, and provider data to provide workers, supervisors, and administrators with the information they need to protect children, help families, and manage child welfare programs. The FSFN application preceded and completed functionality that was in the Florida’s Home Safe Net (Hsn) application.

1.2 Program or Service Specific Terms

Term Definition

AES Adoption Exchange System

AFCARS Adoption and Foster Care Analysis and Reporting System

API Application Programming Interface

APS Adult Protective Services

ASA Adult Safety Assessment

BO Business Objects

BOE Business Objects Enterprise

CBC Community Based Care

CIC Child in Care

CPS Child Protective Services

CSA Child Safety Assessment

CSE Child Support Enforcement

DB Database

DBA Database Administrator

DCF Department of Children and Families

ETL Extract, Transform and Load

FDLE Florida Department of Law Enforcement

FLORIDA Florida Online Recipient Integrated Data Access System

FTP File Transfer Protocol

GUI Graphical User Interface

Hsn Florida’s Home Safe Net

HTML Hyper Text Markup Language

HTTP Hypertext Transfer Protocol

J2EE Java 2 Platform, Enterprise Edition

JDBC Java Database Connectivity

JDK Java Development Kit

JMS Java Message Service

JSP Java Server Page



Term Definition

LDAP Lightweight Directory Access Protocol

MCTS Missing Children Tracking System

MVC Model View Controller

NYTD National Youth Transition Database

OLAP Online Analytical Processing

OLTP Online Transaction Processing

PDF Adobe Portable Document Format

RAID Redundant Array of Independent Disk

RDC Remote Data Capture

SAN Storage Area Network

TDS Tivoli Directory Server

VPN Virtual Private Network

XML Extensible Markup Language Table 1 – Definitions

1.3 Functional Overview FSFN application comprises of four core modules that correspond to four fundamental business processes of child welfare and a common application functions module that supports shared system functionality.

1.3.1 Service Management This module encompasses individual and family demographics, family assessments (including family dynamics and safety and risk concerns), and the planning, arrangement, delivery, and monitoring of services.

1.3.2 Finance Management This module includes payment, disbursements, budgeting, trust account maintenance, client eligibility tracking, and reimbursement activities.

1.3.3 Staff Management This module supports the assignment of work, tracks worker-supervisor relationships, and documents staff training.

1.3.4 Provider Management This module includes the registration, training, contracting, and relationship maintenance activities undertaken with service vendors.

1.3.5 Common Application Functions This module supports the shared system functionality. These five components make up the application infrastructure.



Figure 1 – Functional Modules of FSFN



SECTION 2. FSFN ARCHITECTURE

2.1 Application Framework The FSFN application implements the Model-View-Controller (MVC) design pattern using Java 2 Platform Enterprise Edition. MVC is an industry standard design pattern used to construct applications with a graphical user interface. The framework facilitates the implementation of the chosen n- tier architecture as shown below.

Figure 2 – Application Architecture

The FSFN Application Framework is non-proprietary, and is based on the Apache Jakarta Struts Framework (Struts). FSFN has added on to the component architecture that is provided by Jakarta Struts, supplying fundamental Framework Services that are critical to the operation of enterprise systems. Model View Controller and Struts The FSFN MVC architecture separates core data access functionality from the presentation and control logic that uses this functionality. Such separation allows multiple views to share the same enterprise data model, which makes supporting multiple clients easier to implement, test and maintain. It also supports robust security measures, promotes reuse of code for multiple functions, and enables tuning for optimal performance. The model represents enterprise data and the business rules that govern access to this data. Often the model serves as a software approximation to a real-world process, so simple real-world modeling techniques apply when defining the model.

Au

the

ntic

atio

n F

açad

e

JSP_1 JSP_2 JSP_N

Presentation Layer

Web Container A

pp

licatio

n F

ram

ew

ork

BR

BR

BR

BR

BR

BR

DA

DA

DA

DA

DA

DA

Business Rule Components

Data Access Components

Application Server

intranet

JDBC

XML

Mobile Devices

DBMS

Action 1

Action 2

Action N

Co

mm

an

d F

ram

ew

ork

Stru

ts F

ram

ew

ork



A view renders the contents of a model. It accesses enterprise data through the model and specifies how that data should be presented. It is the view’s responsibility to maintain consistency in its presentation when the model changes. This can be achieved by using a “push” model, where the view registers itself with the model for change notifications, or a “pull” model, where the view is responsible for calling the model when it needs to retrieve the most current data. A controller translates the interactions with the view into actions to be performed by the model. In a stand-alone GUI client, user interactions could be button clicks or menu selections, whereas in a Web application, they appear as GET and POST HTTP requests. The actions performed by the model include activating business processes or changing the state of the model. Based on the user interactions and the outcome of the model actions, the controller responds by selecting an appropriate view. The figure below displays the FSFN implementation of the MVC architecture.

Figure 3 – MVC Architecture

Every functional component of the FSFN application follows the above architectural pattern. The Framework provides the components that are surrounded by a solid line in the above figure. The components that are surrounded by dotted lines in the above figure need to be developed by an application developer. These items include:

A Java Server Page (JSP) that provides the user view of the functionality. An Action Class that provides the controller functionality for a functional set of

transactions. An Action Form Class that acts as the data container for a functional set of

transactions. The Action Form Class also provides User Interface Validation Logic. A Business Logic Class that controls and manages the complex business rules for a

functional set of transactions. A Data Access Class that provides database access and a persistence mechanism for

a functional set of transactions.

2.2 Architecture Layers The architecture consists of distinct layers as described below. Each layer represents a logical partition of the application processing in the system. Each layer has a unique responsibility or



purpose in the system and is logically separated from, and loosely coupled with the adjacent layer. The following layers make up the technical architecture:

2.2.1 Presentation Layer The presentation layer runs on the client workstation and is typically a browser (Microsoft Internet Explorer) but in certain scenarios where word processing is needed (letters and notices), the client is Microsoft Word. All remaining layers, used for business rules enforcement, data validation, data access and process control are implemented on the server. The process control is also partly implemented in the user interface by means of a navigational design. The overall picture of various underlying technologies is as shown in the figure below.

Figure 4 – Presentation Layer

2.2.1.1 Core Technologies Involved J2EE FSFN uses J2EE specifications as the development standard for the server side layers. This allows for platform independence, high scalability, high security, multi-vendor support and most important - open standards. J2EE is a collection of various technologies and the following list is used on the project: JDK 1.4.2 – Java development toolkit for all server side layers JDBC 2.0 – Java database connectivity for data access JSP 1.1 – Java Server Pages for server side rendering of client pages Servlet 2.3 – Server side controller specifications Web Browser Microsoft Internet Explorer is the chosen browser for FSFN. The modal and modeless windows channel the FSFN user navigation on the client side by providing step-by-step data entry. iframes are used for back channel communication to save network overhead and promote ease of development. The client interface is implemented through a browser using the following technologies: JavaScript 1.2 and HTML 4.0.1 For rich browser user interface JavaScript is used as a glue to tie the user interface components together. The use of JavaScript is minimal except for setting values or obtaining data from modal windows. This improves the



performance on the client side and eliminates timing dependencies on the client workstation.

RTF 1.6/ Microsoft Word 97 or Higher and ActiveX using Visual Studio 6.0 For rendering Word documents to the user ActiveX technology is also used in conjunction to HTML and JavaScript primarily for interaction with Microsoft Word. Active X is used to internet enable the Word based office automation component of the FSFN application, providing features such as spell check and automated save of documents to the centralized FSFN document repository. The use of this technology allows transfer of data to the client by means of HTTP(s) and not putting any additional firewall holes or burden on the infrastructure. The only requirement is a licensed version of Microsoft Word 97 or higher on the client. The internet standard distribution mechanism is used to install the ActiveX control on the client workstation. The code is digitally signed and packaged along with the application archive and no additional network support is required.

2.2.1.2 Data Validation Rules Data validation rules are implemented partially in the presentation layer and partially in the web server. Data Validation Rules on the server ensure that the basic format of data input through the user interface is appropriate for further processing.

2.2.1.3 Business Rule Enforcement Business Rules implement the data validation and business policies of the enterprise; they go beyond the simple structural validation of presentation layer to ensure that data values are valid within the context of the application. Business Rule Enforcement also dictates the flow of control within the application; i.e., the specific processing to be performed against data, based upon its characteristics or value. All business rules are enforced on the server and displayed back to the user by the presentation layer.

2.2.1.4 Data Access Data Access design elements address the need for the application to store and access data from shared or non-volatile (persistent) storage locations (as opposed to transient or session data). All database access in FSFN is performed by means of Java Database Connectivity (JDBC). JDBC technology is an Application Programming Interface (API) that allows access across a wide range of databases.

2.2.1.5 Process Control Process control elements do not provide business functionality; rather they provide the programmatic framework under which the business functionality is delivered, and serve as the glue connecting the structural elements of the application.

2.2.1.6 Struts Extensions Struts is a generic open source framework and has been written for any web application using the MVC pattern. To meet the unique needs of FSFN application, additional functionality was added to the Struts framework and



some objects were extended. The HTML text tags were extended to add FSFN display styles and behaviors like field level traps.

2.2.1.7 Office Automation Office automation is the process by which Microsoft Word documents are automatically generated and pre-filled with information from FSFN, providing users with up-to-date information for printing, saving, attaching etc. Case Workers process numerous forms, letters, and notifications that are automated in FSFN. The server side components retrieve the document template, populate it with specific application data, and send it to the browser. The client side components take control and display the formatted document in Microsoft Word.

2.2.1.8 Automated Messaging Automated Messaging is an online behind the scene FSFN functionality that sends e-mails to other FSFN users or user group mailboxes.

Excepting Handling and Messaging Exception Handling is done to catch application errors (e.g. business rules violations, database exceptions, etc.) to help users and the development staff to determine application issues and fix them in a timely fashion. Exception Handling in the FSFN application is performed on both client and server side to make sure that business rules are followed and data integrity is maintained.

Logging Logging is an important component of the development cycle because it provides a precise context about a run of the application. Moreover, log output can be saved in a persistent medium to be studied at a later time. In addition to its use in the development cycle, a sufficiently rich logging package could be used as an audit tool. The FSFN Framework uses Log4J (http://jakarta.apache.org/log4j) from Apache as its logging tool. Log4J is designed to be fast and flexible. Since logging is rarely the main focus of an application, Log4j API strives to be simple and easy to use. For effective debugging of issues, FSFN application code insert debug, info, warn etc. statements where appropriate in each class method to point to the development staff where the error occurred. FSFN captures a pre-data image and post-data image, collectively known as audit detail data, for every transaction. Formatted as Extensible Markup Language (XML), the pre-data image contains parameters sent by the client to FSFN while the post-data image contains data sent by FSFN to a JSP template for rendering into a finished HTML document that is rendered to the user. Both images are passed through a filtering component that removes sensitive information such as a worker’s login password, before being sent to the Log4J-based logging infrastructure for output to flat files.

http://jakarta.apache.org/log4j



Every day, all 16 log files from the previous day are automatically combined and compressed into a single file named fsfn_audit.log.{yyyy-mm-dd}.gz. These files are moved to a separate server with 750GB of holding capacity for archival. Volume backups of this server are periodically made to prevent data loss.

Internet Explorer through the DCF VPN/Aventail FSFN is a web application hosted within Department of Children and Families’ (DCF) intranet. Outside access is controlled by connecting to the DCF Virtual Private Network (VPN) through Aventail. The application is fully functional when accessing through the VPN as long as the proper release of Internet Explorer is installed and valid licenses for Microsoft Word are available on the user’s machine.

2.2.1.9 FSFN Framework Services In addition to Struts, there are common services provided by the FSFN application framework. The framework uses a Façade pattern to hide the implementation of its services and to give users of the framework a one face “Foundation”. All requests for primary Framework services are channeled through the Façade. The Façade delegates the service request to the appropriate service provider. By hiding the actual implementation, it’s easy for the framework to enhance features or totally replace logic behind the scene.

The key framework services include:

Data Cache and relevant interfaces

Security provider interface

Exception and error handling, error substitution

Dynamic outliner

Database connection and transaction management related API’s

Encryption/Decryption API’s

Base 64 encoding/decoding API’s

Application server API

State management

Transport management

Email

Transaction statistics and

Office automation.

2.2.2 Security Layer

2.2.2.1 Authentication and Authorization Authentication and Authorization in FSFN consists of a series of interrelated components that together form the building blocks needed to provide the core capability for securing an application.



Authentication The FSFN application seamlessly authenticates users by communicating with DCF's Tivoli Directory Server (TDS) which is the Lightweight Directory Access Protocol (LDAP) server. TDS/LDAP in conjunction with Tivoli Identity Manager makes up the bulk of authentication processing in FSFN. The following steps take place during login to authenticate a user as depicted in the figure below: Worker types in their user id and password on the Login screen. FSFN application sends user authenticate request to TDS/LDAP Server. If the user information exists in TDS/LDAP, it returns a success response back to FSFN. FSFN then forwards the user to the FSFN Desktop or roles selection window (if the user has more than one role in FSFN). On failure, FSFN application stops the user and renders an error message.

Figure 5 – FSFN Authentication

Authorization After the users are authenticated, the FSFN internal security manager further verifies the user authorization based on their User Group and Security Profile.



Figure 6 – FSFN Authorization

Auditing FSFN application provides robust auditing capability. Each user interaction is captured and stored in the database by using the process described below. For every transaction submitted by the user online, FSFN application framework captures the transaction begin and end times in order to derive the transaction duration in milliseconds. The transaction duration period along with the detailed data attributes are posted using a persistent Java Message Service (JMS) queue to the FSFN event broker which records the transaction statistics along with the data details to the FSFN audit database on the DB2 UDB platform.

Figure 7 – FSFN Auditing

2.2.3 Database Layer

2.2.3.1 OLTP Database The FSFN application captures user entered data and stores it in the highly optimized and normalized Online Transaction Processing (OLTP) database.



DCF uses DB2 database management system and a high power IBM Z/OS mainframe server to house the database named FSNDPD01. A dedicated logical partition together with storage system provides the power to run this database efficiently. The FSFN production application has around 450 tables and over 1,200 indexes. The indexes have been designed to enforce uniqueness on the tables and to provide for optimal performance. FSFN application uses 2 separate user ID’s. One user ID is used for regular application transactions and the other is used for search transactions. The search user ID gets lower priority on resource allocation on the mainframe database compared to the application user ID.

2.2.3.2 Database Architecture The architecture of the database was developed with performance in mind. The database is designed to have data mart objects in the schema called DB2ADMIN and data warehouse objects in another schema called FSNDW201. The objects in these schemas are in separate tablespaces and are using their own memory (buffer pool). Based on the number of rows in the table, these tables are using appropriate bufferpool size (4K, 8K, 16K, and 32K). Multiple containers are added to the tablespaces to enable parallel I/O for data retrieval from the disk and for storing data to the disk. Proper indexing of the tables and appropriate design of the tablespaces, the high-speed storage disk, and the server memory ensure the performance of the ETL jobs, CBC file extraction, and user’s queries using Business Object Enterprise. All databases are recoverable. Active transaction logs and archived transaction logs are kept on high-speed disks. This enables the users to access the database while the database is being backed up and allows backup of individual databases. Every day at 6.00 A.M. hot backup of database FSNPD2DM is enabled. The system takes two and half hours to take this backup. Together with these backups and transaction logs, the whole database or an individual table space can be recovered to the point in time. The backups are also copied for disaster recovery.

2.2.3.3 Backup and Recovery To provide secure and reliable backups, all tablespaces are backed up nightly with DB2 image copies. These backups can be used for local recovery scenario whether the need is to recover one or more tables to a previous point in time or to recover to the current point. In order to be prepared for any Disaster Recovery scenario, dual copies of all backup tapes along with dual copies of all DB2 system archive log tapes are sent daily to the secure offsite storage location. This provides the capability in the event of disaster to recover the entire mainframe DB2 system and the entire FSFN mainframe OLTP database to the point of the last set of backups taken.



2.2.3.4 Performance Measurement To ensure continued optimal performance weekly runstats and reorgs are taken of all tablespaces and indexes. These runstats and reorgs are generated dynamically each week in order to process only the objects actually needing runstats or reorgs.

2.2.3.5 Imaging and Auditing To facilitate imaging, auditing and DOH search functionality, DCF uses DB2 LUW database management system on Linux 64 bit system. The OLTP database name is called FSNPD201. This database for OLTP is primarily used for storing large data objects like images, audit files and data that is read only. Imaging uses tables in both mainframe and UDB as the actual image is stored in the UDB and the image details are stored in the mainframe.

2.2.3.6 DB2 Universal Database (UDB) For reporting and analytical querying purpose, DCF uses DB2 LUW database management system on Linux 64 bit system. The database name is FSNPD2DM. The schema for the data mart is DB2ADMIN and the schema for data warehouse is FSNDW201. Every day at 6.00 P.M., the Extract, Transform and Load (ETL) process extracts all the changes and updates the data mart and data warehouse database tables.

2.3 Mobile Architecture FSFN is extended to support the use of mobile device technology by workers in the field to enable them to leverage FSFN data during field visits and to capture photographic and form data from the field. The following are the mobility applications developed and used by Case Managers and DCF Legal Attorneys: o RDC (Remote Data Capture) Case Management – Laptop version This application is a desktop smart application developed using Java Swing technology. The application runs on laptops, tough books and tablets running Windows XP operating system. The application is hosted on Tomcat Server for downloading to the users’ machine. Using this application, Case Managers can capture child participants’ photographs and visit details along with GPS information and upload to the FSFN application. o RDC (Remote Data Capture) Case Management – Blackberry version Blackberry version of Case Management application is developed using Java and Blackberry technologies. The application can run on blackberry running on OS 5.0 or higher. The application is hosted on Tomcat Server for downloading to the users’ blackberry device. Using this application, Case Managers can capture child participants’ photographs and visit details along with GPS information and upload to the FSFN application. o CLS (Child Legal Services) Mobility – Blackberry version Child Legal Services Mobility application is developed using Java and Blackberry technologies. The application can run on any blackberry running on OS 5.0 or higher. The application is hosted on Tomcat Server for downloading to the users’ blackberry device. Using this application DCF’s Children’s Legal Services attorneys can create and schedule legal actions.



The high level architecture for the FSFN mobility applications and server side extensions that support the use of mobile device technology are described below.

FSFN Web Services

Blackberry

Persistent store

Blackberry Enterprise Server

Case Management

Application Download

Site

Set access

permissions

Download or Update

Mobility application

Get Worker Cases,

from FSFN.

Save child visit notes, photos

to FSFN

Cell tower

Direct GPS

Assisted GPS

Figure 8 – High Level Architecture for FSFN Mobile Applications

2.3.1 Remote Data Capture (RDC) Server Side Architecture This section provides details on the following elements of the mobile device support architecture:

o Security o Web Service Implementation o Web Service Message Implementation



Figure 9 – Mobility Server Side Extensions

2.3.1.1 Security Security for the server side components of the remote data capture solution is built on the FSFN application security infrastructure. Authentication Authentication is the process for verifying the identity of the users of the remote data capture web services. Only registered FSFN users are permitted to utilize the web services that support the FSFN remote data capture systems. Just as FSFN users must have their user name and password credentials registered in the DCF LDAP directory so must the RDC users. The authentication process for the FSFN RDC web services checks the user name and password for each web service call against the DCF LDAP directory. If the user name and password combination do not match a valid active account in the DCF LDAP directory, the user is not permitted to use the RDC web services. Authentication is performed through Basic Authentication supported by the Weblogic application server. Authorization Authentication is the process for verifying that an identified user has the rights to perform the requested action. For the FSFN RDC web services the DCF LDAP repository is used to determine whether the user is an authorized FSFN user. Each FSFN user is associated with the LDAP group. This group authorizes the user to access the FSFN application as well as the FSFN RDC web services. This is implemented similar to the FSFN online authentication.



Confidentiality Confidentiality means that the data is protected from unauthorized viewing while it is in transit between the FSFN RDC client systems and the FSFN server. The FSFN server side application is accessible only within the DCF intranet. The FSFN RDC client applications access the FSFN servers through the DCF Aventail gateway which provides a secure / encrypted virtual private network to prevent sensitive information from unauthorized access while it is in transit over the internet. Data ownership In FSFN a user must have an assignment to a case in order to add or make changes to the case record. The FSFN RDC web services enforce the same data ownership constraint. Auditability All FSFN RDC web service calls are logged to the same audit log tables as on-line requests. The audit log details for FSFN RDC web services are recorded in XML format just as the on-line audit log.

2.3.1.2 Web Service Implementation The FSFN web services are defined using Java EE 5 annotations under the W3C Web Service Policy Framework, WS-Policy. There are no changes required to the FSFN network configuration to support the FSFN RDC web services. The FSFN RDC web services are deployed on the same WebLogic application servers as the FSFN application and the existing FSFN web service interfaces.

2.3.1.3 Web Service Message Implementation FSFN RDC web service data is exchanged using XML strings. The functional design specification for the FSFN RDC web services includes XML schemas defining the structure of the input and output messages for each of the web service calls supported. The XML strings are converted to and from the Java objects used in the business logic tier using JAXB with JSR 173 StAX (Streaming API for XML). With the exception of application errors the FSFN RDC web services will rely on the standard HTTP web service error messages. Application error messages will be returned as part of the standard FSFN RDC web service message structure.



2.4 FSFN Hardware and Software Configuration

Figure 10 –FSFN Hardware Configuration

2.4.1 Server and Software Specifications

Florida Safe Families Network (FSFN)

Platform Software Version

Application Java J2EE Bea Web Logic

1.5 9.2

Database IBM DB2 z/OS, IBM DB2 Universal Database (UDB) 9.1

Data Warehouse SAP Business Objects Data Services 12.2

Report Business Objects XI SP5 11.5



Florida Safe Families Network (FSFN)

Hardware Server Type

Server Name Building Operating System

Production Application Servers

FSFNPAPP1/ FSFNAPP2/ FSFNAPP3

NSRC Linux/4 Dual Core AMD Opteron Processors/32G RAM/2X100G HD

Database FLIS NSRC Z/OS 1.12

Database FSFNPUDB2/ FSFNPUDB3

NSRC Red Hat Enterprise Linux 5.4 2 Quad Core Xeon 3.0Ghz/32G RAM/2X100G HD/2 TB SAN

Batch Servers

FSFNBODI1 / FSFNBODI2

NSRC Windows Server 2003 R2 2 Intel Xeon Dual Core 3.0Ghz/16G RAM/250G HD

Report Servers

FSFNBOE1/ FSFNBOE2/ FSFNBOE3

NSRC Windows Server 2003 R2 Intel Xeon Dual Core 3.0Ghz/16G RAM/250G HD+SAN Storage

Report Servers

FSFNBOE3 NSRC Windows Server 2003 R2 Intel Xeon 5160-3.0Ghz/32RAM/250G HD + SAN Storage

UAT Test Application Server

FSFNUVER NSRC Red Hat Enterprise Linux 5.4 Intel Xeon Quad Core 3.0Ghz/16G RAM/2X100G HD

Database FLIA NSRC Z/OS 1.12

Database FSFNTUDB1 NSRC Red Hat Enterprise Linux 5.4 2 Quad Core Xeon 3.0Ghz/32G RAM/2X100G HD/2 TB SAN

Report Servers

FSFNBODIUAT/ FSFNBOETRNG

NSRC Windows Server 2003 R2 Intel Xeon 5160-3.0Ghz/16G RAM/250G HD

System Test Application Server

SCFLZD111 NSRC Red Hat Enterprise Linux 5.4 Intel Xeon 5160-3.0Ghz/4GB RAM/200GB HD/


Database FSFNTUDB1 NSRC Red Hat Enterprise Linux 5.4 2 Quad Core Xeon 3.0Ghz/32G RAM/2X100G HD/2 TB SAN

Report Servers

FSFNBODIUVER/ FSFNBOEUVER4

NSRC Windows Server 2003 R2 Intel Xeon 5160-3.0Ghz/16G RAM/250G HD

Development Application Server

Local development workstations

NSRC Windows XP Core 2 Duo/3GB RAM/250G HD


Report Server

FSFNBODIUVER NSRC Windows Server 2003 R2 Intel Xeon 5160-3.0Ghz/16G RAM/250G HD

Table 2 – Server and Software Specifications



2.5 FSFN – DCF Network Diagram

Figure 11 – High Level Network Architecture for FSFN



SECTION 3. REPORTING AND DATA WAREHOUSE ARCHITECTURE

Integrated with the FSFN application, the Reporting and Data Warehouse environments support end-user reporting, ad hoc queries against FSFN data, and interface processing for external applications.

The FSFN Data Warehouse and Reporting Architecture is comprised of multiple databases supporting ETL, scheduled reporting, and ad hoc reporting. The architecture includes the integration of the Business Objects tool suite to provide decision support systems, query and reporting, data warehousing, online analytical processing (OLAP), statistical analysis, forecasting, and data mining capabilities.

The Business Objects platform, known as Business Objects XI, includes the use of the Data Integrator tool for ETL processing to provide the business intelligence platform for FSFN. The IBM DB2 Universal Relational Database (UDB) engine is used on the database platform. The architecture is presented below.

FSFN DW Reporting

Environment

FSFN DW/DM EnvironmentFSFN DW Workspace

Environment

Production Environment

FSFN

(OLTP)

BO Data

Integrator

Extract

Process

FSFN DW

Work space

Area

BO Data

Integrator

Transform

Process

FSFN

Data Warehouse

(UDB DB2)

BO Data

Integrator

Load

Process

FSFN

Business

Objects

Universe(s)FSFN

Data Mart

(UDB DB2)

Operational Reports

Analytical Reports

Business

Objects

Reporting

Server

FSFN

Auth

Source

Dimensional data

model to support

analytical reports

Tie-in with the FSFN

authentication source

Data Repository

For

External Data

Other Data

Repositories

(outside of

FSFN OLTP)

FSFN DW Technical Architecture

Cross-Program

Enterprise Data

Warehouse

DCF

Data Warehouse

Reports

Figure 12 – Reporting and Data Warehouse Architecture The reporting architecture includes a data warehouse environment comprised of two primary databases, the data warehouse database and the data mart database. The data warehouse database houses production data in structures similar to the production OLTP database. It is refreshed on a periodic basis with production data, and is available to support both scheduled and ad hoc reporting.



The data mart is a set of database tables structured to support reporting and data analysis activities. The Data Marts support online access to data by DCF staff and Community Based Care (CBC’s). These database environments are also used to support the input and output of extract files from external systems. External systems include CBC extracts, ICWSIS, ECI, DJJ, and data used to support AFCARS reporting. In addition, when the decommissioning of HomeSafeNet (HSn) is complete it is anticipated that the UDB platform will also host a copy of the HSn data in the event access to this data is needed.

The Business Objects Data Integrator tool suite is used to perform the periodic Extract, Transform, and Load processing required to refresh the staging and data marts. Through the use of database triggers the ETL processing from the FSFN online transaction processing (OLTP) database will extract those records added, updated, or deleted since the prior update process execution. In this fashion, the processing needed to keep the reporting databases updated will be optimized from a resource utilization perspective.

3.1 FSFN Data Warehouse Design Overview The FSFN Data Warehouse is comprised of several data stores hosted on the DB2 UDB platform, with two primary data stores housing the Data Warehouse and the Data Mart. In addition, the UDB platform hosts the Business Objects Enterprise data stores supporting report execution and archive, and the FSFN Audit database capturing user actions within the application.

3.1.1 FSFN Data Warehouse The data warehouse database houses production data in structures similar to the FSFN production OLTP database. It is refreshed on a daily basis with production data, and is available to support both scheduled and ad hoc reporting. The refresh process is incremental, applying the changed data from the OLTP.

3.1.2 FSFN Data Mart The FSFN Data Mart is a repository of information designed to support reporting and data analysis. Using the existing HSn Data Mart, the FSFN OLTP data model, and FSFN reporting requirements as design requirements, the fact and dimension tables and measures incorporated into the repository are the primary data source for FSFN reporting. Primary subject areas for the Data Mart include Child Protective Services (CPS) Person Investigation, Adult Protective Services (APS) Person Investigation, Hotline, Service and accompanying Security, and Reference data subject areas. Data Mart tables also house ICWSIS extracts and the data used to construct the CBC extracts. Business Objects universes are applied to this repository and represent the semantic layer presented to the users when executing reports and ad hoc queries executed via the FSFN Reporting environment. The Business Objects tool suite, integrated with the FSFN application, is also used to provide data restricted views of this information per DCF policy.

3.1.3 HSn Historical Copy In addition to hosting the FSFN data repositories, the UDB environment will also host a copy of the HSn OLTP after implementation of FSFN. This repository will support the display of historical Child Safety Assessment (CSA)/Adult Safety Assessment (ASA)



data, and will also be available to a limited set of users that need to access this static data after HSn is shutdown. In addition to the HSn data repositories, the middle tier environment will also be used to host HSn reports. Access to these reports will be through the FSFN Reporting portal, enabling limited access to these reports for research purposes.

3.1.4 FSFN DW Workspace Environment The FSFN DW Workspace environment is provided as needed to support the ETL processing necessary to populate the data warehouse and data marts. This scratch area is not accessed by users, and provides a staging area for data between the OLTP database and target tables in the warehouse environment.

3.1.5 Cross-Program Enterprise Data Warehouse While not currently populated as part of FSFN processing this future data repository, created at the discretion of the department, would serve as a repository for enterprise-wide data for the department and state. Processing implemented as part of the FSFN Release 1. The Enterprise Client Index (ECI) interface is an example of the data that could be hosted in this environment. At present no storage allocation has been provided for this data.

3.1.6 Business Objects Enterprise and Business Objects Data Integrator Data Stores The Business Objects Enterprise and Business Objects Data Integrators tools establish databases that are used to store information needed for the execution of reporting and ETL processes. As part of the installation of these tools, these databases are constructed and linked with the installed instances of the tools. In addition, file space is used to house the report execution instances that are archived and managed by the BOE tool suite. Business Objects Enterprise utilizes two databases to support its processing, a required central management services (CMS) database and an optional audit database. The CMS database which currently reside on an Oracle 10 G instance stores the critical information used in the construction of the reporting environment, including universes, report executables including Crystal, report schedules, and security and user information. The audit database stores a record of user activity within the BO environment. Data Integrator also utilizes two databases to support its processing. The first hosts the information that comprises ETL processing, including projects, work flows, data flows, data stores (connections), and other components associated with the processes. The Central Repository database is used to support configuration and release management for the Data Integrator processes.



3.1.7 FSFN Reporting Platform Servers Numerous dedicated servers are allocated to support the FSFN data warehouse and data marts. This includes servers hosting DB2 UDB, Business Objects, Data Integrator, and a Storage Area Network (SAN).

Figure 13 – Reporting and Data Warehouse Hardware and Software

The production configuration includes the following items:

DB2 UDB Server – This Redhat Linux server hosts the DB2 UDB database engine for the Data Warehouse, Data Mart, Audit database, and the Business Objects tool suite.

Business Objects Server – Three of four CPUs of two Windows ES servers are provided to host Business Objects Enterprise (BOE). BOE provides the reporting architecture visible to the users, including the InfoView tool integrated with FSFN to display reports and other reporting features.

Business Objects Data Integrator – Two Windows ES servers are provided to host BO Data Integrator. This tool provides Extract, Transform, and Load (ETL) processing used to populate the Data Warehouse and Data Mart. The tool is also used to process interface data, including CBC Extracts, The Dashboard, ICWSIS, ECI, and DJJ.

Storage Area Network (SAN) - The Storage Area Network for FSFN provides twelve terabytes of data storage, six terabytes of storage mirrored. This space is used to house both development and production databases, and provides storage space for the Business Object Enterprise and Business Objects Data Integrator databases. The FSFN Audit database, providing a record of user actions in FSFN, is also hosted on the SAN.



The current version of DB2 LUW ESE is Version 9.5 64 bit Fixpack 6A. For the Windows servers, Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 1 is installed. For the LINUX servers Red Hat Enterprise Linux AS Release 5.2 64 bit is installed.

SAN storage is divided into 3 different tiers. Critical data stores that may need additional redundant array of independent disk (RAID) levels beyond the mirroring are the Audit Log and the BOE and BODI database instances in production. Loss of the data in these databases is not replaceable, whereas the Data Warehouse or Data Mart data could be rebuilt from the production OLTP.

SAN Storage Type SAN Space Allocated (G)

Tier 1. Consists of enterprise-class intelligent Fiber Channel-based storage systems. These disks are high performance, high RPM, cache, RAID protection (usually mirrored), and located within a Storage Area Network (SAN) infrastructure to provide high availability. This storage is usually used for business critical or high transaction volume applications which require quick response times. 550 Tier 2. Consists of Fiber Channel-based disk, with RAID protection, and either provisioned within the enterprise storage system, or virtualized into modular-class storage system. Servers could be running e-mail applications, data warehouses, or other business important transaction applications. 16,837 Tier 3. Consists of high-density Serial ATA (SATA) disk with RAID protection, could be either SAN or locally attached storage. This storage is low performance, suitable for static web pages, file shares, tape replacement or archive media. Prices may vary depending on type of connectivity required and RAID configuration. 10,216

Total 27,603 Table 3 – SAN Storage

The following table presents the DB2 LUW instances and their usage for FSFN.

RAID 10 RAID 5 RAID 5 RAID 10 RAID 5 Development

Estimated Size (all database

instances included)

FSFN Audit

Log Data Files

FSFN Data

Warehouse

FSFN Data Mart

BOE/BODI HSn Historical

Copy 500GB 500GB 500GB 700GB

Memory Allocation 256MB 1GB 2GB 2GB Production

Estimated Size

FSFN Audit Log

FSFN Data

Warehouse

FSFN Data Mart

BOE/ BODI

HSn Historical

Copy 3TB 500GB 500GB 700GB 150GB

Memory Allocation (If not managed by

UDB)

1GB 2GB 14GB 8GB 2GB

Table 4 – DB2 LUW Instances and Usage



Additional storage allocations are made on the SAN: • Development Backups – 500GB • Production Backup space - 500GB • FTP Server file space – 200GB • FSFN Application Server file space – 200GB per server (2 servers) • Business Objects Enterprise Development Server file space – 500GB • BO Data Integrator file space – 100GB per server (2 servers) In the development environment, multiple copies of the databases may be present to support development, system test, acceptance test, pilot, etc. as desired. For these, one instance of DB2 UDB is needed to support the various test databases specified for that instance. Within the BOE/BODI instance two different sets of database tables are established as part of the installation of Business Objects Enterprise and Business Objects Data Integrator. In addition, file space is needed to support the BOE storage of report execution instances. The report instances file space and the Audit Log file space, housed in RAID10 storage on the SAN, have the greatest potential for growth.

The SAN will also provide space for file systems needed to store extract files created by the ETL processes. This file space should be available to the BO Data Integrator servers, with approximately 100GB per server allocated to support this processing. Historical HSn reports are also to be housed in the SAN, with access provided through the FSFN Reporting portal.

3.2 Software and Tools

Three primary software tools namely Crystal Reports, Desktop Intelligence, and Web Intelligence (WebI) provide the processing necessary to populate the Data Warehouse and Data Mart, the CBC extracts, and the other interfaces that utilize data housed in the DB2 UDB platform.

Business Objects Crystal Reports

The Crystal Reports toolset provides a platform for designing, constructing and deploying enterprise information reports. The version used for FSFN is integrated with the Business Objects Enterprise and makes full use of the Business Objects repository and the semantic layer. It also can be used to develop reports against a broad array of data sources that need not necessarily be part of the Business Objects metadata repository.

The Crystal Reports toolset provides a feature-rich user interface for the development of reports, providing for the needs of both the inexperienced, non-technical user, as well as the experienced report developer. The user interface provides comprehensive “wizard” functionality to walk users through the process of report design and construction and provides an extensive library of report templates for reuse and extension.



Business Objects Web Intelligence via InfoView The Business Objects Web Intelligence (WebI) tool provides a flexible user interface for building and analyzing reports against department information over the web, on secured intranets and extranets. The web intelligence tool set is accessed from a browser-based client interface through the BO InfoView portal. Depending on the FSFN security profile a user can interact with the reports in documents or edit and build documents using the Web Intelligence report panel or query panel.

From the InfoView portal, users gain access to the Web Intelligence documents, can view reports, and can access reports constructed with Crystal Reports. Depending on the security access of the user, functionality runs from simple viewing of reports to a smaller set of users that have the ability to build, publish, and schedule reports. When reports are printed, the Web Intelligence tool automatically generates a copy of the report in Adobe Portable Document Format (PDF) format for optimum print quality. The web intelligence tool provides comprehensive query and reporting functionality allowing authorized users to author report content by interacting with the Business Objects metadata repository. Support is also provided for scheduling execution of the reports and for sending the reports out via email or FTP

Business Object Desktop Intelligence

Business Object Desktop Intelligence provides a tool suite for the development and execution of reports. Prior to the inclusion of Crystal Reports and WebI in Business Objects Enterprise, Desktop Intelligence provided the developer and end user toolsets to construct and publish reports. This fully featured tool suite is fully supported by Business Objects, in particular in enterprises where Crystal Reports is not utilized.

For the FSFN project, this tool suite is used to construct listing reports, which are then published and then single pass burst with the use of the Desktop Intelligence tool. Single pass bursting of reports means that the report results are generated one time, and then burst into separate report result sets. For listing reports the bursting is performed by the district and then agency dimensions, with the results moved to appropriate report folders. This processing approach supports the security model desired by DCF for the content of detailed reports.



SECTION 4. PERFORMANCE TESTING

FSFN follows a methodology for performance analysis and management that uses benchmarking for predicting performance for a given application deployment configuration. It combines the expertise of skilled architects and specialists along with a closely mirrored production environment to validate the performance of the FSFN application. Testing is conducted on production volume data using the scenarios that are commonly used by FSFN users. All new SQL transactions are required to be reviewed by the DBA prior to releasing into the higher test environments. FSFN is not currently running automated performance scripts prior to maintenance releases at this time. Areas of application that are changed are monitored throughout system test and UAT for any potential performance impacts prior to release into production.



SECTION 5. BATCH JOBS The batch programs and processes in the FSFN system are designed to run without human intervention, with the exception of on-demand batch programs. Autosys is used as the batch scheduling tool. The batch scheduler automatically runs scheduled batch runs, backup procedures and interface programs. Reports, which are part of the scheduled run, will be produced without any operator intervention.

Figure 14 – FSFN Batch Process

5.1 Batch Framework

The batch processes consist of individual Business Objects Data Integrator, COBOL and Java programs that are arranged in logical groups called run cycles and run inventories. These run cycles and run inventories are scheduled either to process information on regular intervals (daily, weekly, monthly, yearly) through the Autosys scheduler or are initiated on an “on-demand” basis. Certain dependencies may exist within the run cycles and run inventories. Therefore, in some instances the order in which the run cycles and run inventories are initiated is significant. The Autosys jobs automatically create a log or a message when they run. The BODI, JAVA, and COBOL jobs create a log file when they run. The reports create a Status Message. These logs contain program statistics and/or error messages. With the exception of 3 COBOL programs residing on the IBM Z O/S mainframe, batch jobs are written in Java. The Java batch framework consists of common library functions that handle database access, error reporting and program logging. The Java batch programs are run in a Windows 2003 server environment by creating executable .bat scripts which call the Java batch class to be executed. The same executable scripts are setup to be called in Autosys by providing the executable name.

Batch programs use control data and parameter files to control processing. Parameters must be updated before the scheduled start of a batch run and before the operator may enter an on-demand run for processing.



The operator manually submits on-demand batch runs. Re-running scheduled processes or reports will be handled in the same manner as an on-demand run.

5.2 Back up routines Back-up routines are established to prevent a loss of information and allow recovery of data. The operations staff is responsible for the backing up of data on two categories of equipment, the Oracle servers and the file servers. Backups of individual client PC’s will be the responsibility of the workers. All the FSFN batch jobs (except for the real-time ones) will run after business hours beginning after 5:00 P.M.



SECTION 6. INTERFACES FSFN Interfaces are designed to transfer data between FSFN and external entities in real-time/near real-time and in batch mode. Transfer of data is done to reduce data redundancy as well as to keep all systems up-to-date.

Following are the interfaces that are part of FSFN application and are explained in detail later:

Interface Name Description Architecture Complexity Interface Type

Agency Interface

Adoption and Foster Care Analysis and Reporting System (AFCARS)

Flat file with AFCRS data to Feds Flat File Very Complex

FSFN -> Feds Feds

Adoption Exchange System (AES)

Data to support Adoption web site Flat File Moderate

FSFN -> Adoption Website

DCF (internal)

Community Based Care (CBC) Fiscal Agency Accounting System

Daily Extracts to CBC's Flat File Very Complex

FSFN -> CBC CBC's

Child Support Enforcement (CSE)

Data extract to Child Support Flat File Very Complex

FSFN <-> CAMS DOR

Department of Health (DOH)

Data extract from DOH Flat File Moderate

DOH -> FSFN DOH

Missing Children Tracking System (MCTS) - Florida Department of Law Enforcement (FDLE) Link

Data transfer to FDLE for Missing Child System

Webservice/ Servlet Moderate

FSFN <-> FDLE FDLE

Florida Online Recipient Integrated Data Access (FLORIDA) System

Data exchange for eligibility calculation for child

FLORIDA framework Very Complex

FSFN <-> FLORIDA

DCF (internal)

Hotline Phoenix System

Data exchanges to hotline applications

Webservice/ Servlet Complex

FSFN <-> Phoenix

DCF (internal)

National Child Abuse and Neglect Data System (NCANDS)

Data extract to Feds Flat File Complex

FSFN -> Feds Feds

Department of Children and Families (DCF)

Data extract to Dashboard Data Extract Moderate

FSFN -> Dashboard

DCF (internal)

National Youth Transition Database (NYTD) Data

Data exchanges to Cby25 Flat File Complex

FSFN -> Cb25 5 Points <-> FSFN

Cby25 and 5 Points

National Youth Transition Database (NYTD)

Data extract to Feds Flat File Complex

FSFN -> Feds Feds

RDC - Mobility Applications

Data exchange to support Mobility applications Webservices Very Complex

FSFN <-> RDC

DCF (internal)

Checkprint/Checkwrite – Financials

Data exchange to CBC's for financial data

Flat file/ Webservices Moderate

FSFN <-> CBS

DCF (internal)

Table 5 – FSFN Interfaces



6.1 Adoption and Foster Care Analysis and Reporting System (AFCARS) Interface AFCARS is a federally mandated interface for SACWIS systems to submit Foster Care and Adoption statistics on a yearly basis. In FSFN, AFCARS report is broken into two processing groups - AFCARS Data Extraction and AFCARS File Generator. Both the AFCARS Data Extraction and File Generator processes are scheduled as part of the Batch Cycle using Job Control Language (JCL) to execute them.

6.2 Adoption Exchange System (AES) Interface The State of Florida has established a statewide Adoption website called Adoption Exchange System (AES) with a photo listing component. The interface has 3 distinct data transactions - Child Web Extract File, Sibling Group Web Extract File and Link Picture Photo. The first two extracts (Child Web Extract and Sibling Group Web Extract) contain the text, while the third extract (Link Picture) contains the photo. The extracts are provided to DCF IT Staff. DCF IT Staff copy the content of the folder to the Adoption website manually. The website is updated once a week. The newer data from FSFN overwrites the data on the Adoption website each time the extract is run, and is viewable by the public immediately. Manual uploads can be done outside the schedule if necessary.

6.3 Community Based Care (CBC) Fiscal Agency Accounting System Interface CBC fiscal agency accounting system interface with FSFN, is a two way interface that support the transfer of financial data between each CBC and FSFN. The CBC interface supports interfacing with multiple accounting systems based upon the CBC business model. CBC Lead Agencies can have one accounting system or can oversee sub-agencies each one with a different accounting system. FSFN is flexible enough to recognize and process invoices appropriately.

6.4 Child Support Enforcement (CSE) Interface The information sharing between CSE and FSFN is a two way interface for all children in open placement at the time of running the batch program. The Children in Care batch program selects the children who are currently in an open placement status and generates a text file. The information is generated on a weekly basis. The distribution of this file to CSE is processed through FSFN and CSE is provided with secure access to this file.

6.5 Department of Health (DOH) Interface The DOH, Vital Statistics/Birth Registration system, currently sends DCF, a weekly incremental extract of vital statistics/birth certificate data recorded in FLORIDA for the previous seven (7) days. The data is loaded to DCF’s Client Index System (CIS) system and is available for search by approved FSFN users for validating child demographic data documented in FSFN cases. An import process is utilized to load the vital statistics data to a set of defined data structures in FSFN. The FSFN on-line application provides the users with the capability to search the vital statistics data. Once the worker searches and identifies the respective birth record, the case worker manually validates the child’s person management demographic information. FSFN provides the ability to link the specific birth certificate record to the child’s person



management record for later retrieval and review. Additionally, FSFN maintains an audit trail of all searches against the birth certificate records for reporting back to DOH.

6.6 Florida Online Recipient Integrated Data Access (FLORIDA) System Interface FLORIDA is the state’s eligibility system of record for Child in Care (CIC) programs, which include Foster Care, Expedited Medicaid, Independent Living, and Adoption Subsidy. The FSFN/FLORIDA interface automates the transfer of eligibility data. The interface is responsible for passing eligibility data captured in FSFN to FLORIDA using the following distinct data transactions: o Initial Determinations: Initial submission of FSFN eligibility data to the FLORIDA system to

establish Title IV-E Determination and Medicaid eligibility. o Redeterminations: Due to a status change or annual resubmission of eligibility data from

FSFN to FLORIDA. o Close: Submission of eligibility data from FSFN to FLORIDA causing the child eligibility

record to close. The data for each transaction is standardized and modeled after the forms that are currently used to manually enter the data in FLORIDA. These automated data transactions are accomplished by using IMS Connect technology.

6.7 Hotline Phoenix System Interface The Phoenix application is a DCF system for capturing of child and adult protective services intake calls. The system supports the staff manning the Hotline and serves as a central point of contact for the State. The PhoeniX system accesses FSFN data at three distinct points in the intake business process and FSFN accesses Phoenix data at two distinct points in the intake business process.

6.8 National Child Abuse and Neglect Data System (NCANDS) Interface NCANDS is a voluntary child abuse reporting program designed in response to the Child Abuse Prevention Adoption and Family Services Act 1988. The program's purpose is to collect, compile, analyze, and make available child abuse and neglect reporting information on a state-by-state basis. The file is compiled by FSFN and uploaded to the business objects repository. Staff manually send the file to the Feds.

6.9 National Youth and Transition Database (NYTD) Interface A vendor named Five Points collects survey information for the National Youth in Transition Database (NYTD). Person information from FSFN is sent to the vendor via a batch job. Five Points administers the survey and collects answers to survey questions. A series of FSFN batch processes retrieve completed survey information from Five Points and saves this information in the FSFN OLTP database. A subsequent batch program packages the data into a XML file format suitable for transmission to the federal server.

6.10 RDC - Mobility Applications Please see the Mobile Architecture section for a description of the mobility application and interface.



6.11 Checkprint/Checkwrite – Financials The financial check write interface can be divided into 2 parts. The file that creates the actual checks and the interface that updates FSFN payment information once the checks have been printed by a CBC.

6.11.1 Create Check Write Extract File The Create Check Write Extract File (b_fm02_chk_write_file.java) process run generates ‘fm02-chk-file’ flat file that contains payments for providers. Each CBC Accounting System receives a separate file. The file is pushed (FTP-Push) from the FSFN server to the local CBC FTP servers. Archive for previous days’ files are available for download from the FSFN BOE environment. The diagram below depicts the high level process flow for generating and staging the Check Write File for distribution to the CBC financial systems. This interface collects all FSFN payments and payment adjustments that will be included in the next check run and sends them to the CBC Accounting System via the interface. The Check Write File Extract run generates ‘fm02-chk-file’ file that contains payments for providers. Each CBC Accounting System receives a separate file. For ease of separate postage processing all providers with foreign mailing addresses are appended at the end of the check write file.

Figure 15 – Check Write Process

6.11.2 Check Printed This interface updates the FSFN payment information with the checks (information) that have been generated and issued by the CBC accounting system for the FSFN generated payment. The CBC Accounting Systems invoke a web service call to update the Payment and Payment Adjustment with the Check Numbers and Check Dates into FSFN. Since the Check Numbers and Check Dates can also be manually entered into FSFN through the Check Number Recording Page. Therefore CBC Information that is sent through the interface will not override what has been manually entered in FSFN.



CBC’s Web Service call is handle by the following three java classes in FSFN: IN07_CheckPrintedInterface.java – Main Web Service Class IN07_CheckPrintedInterfaceBL.java – Web Service Business Logic Class IN07_CheckPrintedInterfaceDA.java – Web Service Database Access Class

Figure 16 – Check Printed Process



EXHIBIT A – Key Statistics

Listed below are key statistics for FSFN

General Information Counts Functional Statistics Active Case Assignments in Month of January 2011 5,345 Active Protective Investigators in Month of January 2011 1,675 Children Served in Month of January 36,471 Total Children Served in Calendar Year 2010 58,402 Total Children Served in Calendar Year 2009 60,533 Payments Generated in January $12,68,2785 Active Users Average Unique FSFN Users Per Day 5,900 Average Unique FSFN Users Per Day 9,300 Average Unique FSFN BOE Users Per Day 615

Table 6 – General Information

Technical Components Counts Web Pages Java Server Pages 1,735 Java Script Pages 832 Batches Java Batches 30 Cobol Batches 3 Autosys Jobs 500 Database and CBC Extracts OLTP Tables 445 UDB Tables 1,255 CBC Extracts 50 CBC Files 50 Reporting and Data Warehouse Reports 280 Universes 56 DB Views 67 ETLs 150 Web Services Web Services Components 20

Table 7 – Technical Components



FSFN Application Transactions: Application Usage has increased by 23 Million Transactions.

Chart 1 – System Transactions

FSFN Application Usage: Unique Users Logging in the System

Unique Users Logging/Year

10500

11000

11500

12000

12500

13000

Calendar Year

Calendar Year 11350 12190 12880

2009 2010 2011

Chart 2 – Unique Users



FSFN Children Served:

Children Served Population by Year

54000 56000 58000 60000 62000 64000

2009

2010

2011

Cale

nd

ar

Year

Children Served

Children Served

Children Served 59950 57864 62318

2009 2010 2011

Chart 3 – Children Served

Hotlines Intakes Received:

Intakes Received

0

100000

200000

300000

400000

Year

Inta

ke

s R

ec

eiv

ed

Intakes Received

Intakes

Received

248072 314884 344450

2009 2010 2011

Chart 4 – Hotlines Intakes



EXHIBIT B – Desktop Configurations

Desktop Configurations Hardware

Developer PC BA Laptop Developer PC (exception)

Manager/Supervisor

Processor Dual Core, >2.4 GH

Dual Core, >2.4 GH Quad Core, >2.4 GH Dual Core, >2.4 GH

RAM 4GB 3GB 8GB 3GB

Hard Drive 250GB 160GB >250GB 160GB

Gigabit Ethernet adapters

Yes Yes Yes Yes

MiniTower Yes N/A Yes N/A

Docking Station N/A Yes N/A Yes

Table 8– FSFN Technical Components Counts Software for All PC/Laptop Windows XP (Quote references Windows 7) Office 2007/2010 Professional CD/DVD RW Winzip 12.0 Professional or 7zip (open source equivalent) MS Visio 2007/2010 CD/DVD RW Winzip 12.0 Professional or 7zip (open source equivalent) Antivirus - DCF Standard Lotus Notes / Mail Client TextPad or Notepad (Text Editor other than Notepad) Service Center

Table 9 – Software for Desktops and Laptops

Java Developer Software Needed (FSFN) Desktop Weblogic 9.2 MP3 Yes Eclipse 4.2.x Yes Eclipse plug in JAuto Doc (source code doc) Yes Eclipse plug in Clearcase Yes Java 6 Yes Squirrel SQL Client Yes IBM Rational Clear Case Yes

IBM Rational Clear Quest Yes

Java/DBA Developer Software Needed (FSFN) Desktop Weblogic 9.2 MP3 Yes IBM DB2 (DBA) Yes Eclipse 4.2.x Yes Eclipse plug in JAuto Doc (source code doc) Yes Eclipse plug in Clearcase Yes Java 6 Yes Squirrel SQL Client Yes IBM Rational Clear Case Yes

IBM Rational Clear Quest Yes



BA Software Needed Laptop Squirrel SQL Client Yes IBM Rational Clear Case Yes IBM Rational Clear Quest Yes Snag It or equivalent for Image Copy/Manipulation Yes

Aventail Client Yes

Manager/Supervisor Software Needed Laptop Squirrel SQL Client Yes IBM Rational Clear Case Yes IBM Rational Clear Quest Yes Snag It or equivalent for Image Copy/Manipulation Yes MS-Project 2007 Yes

Aventail Client Yes

BOE Developer Software Needed (FSFN) Desktop Weblogic 9.2 MP3 Yes Eclipse 4.2.x Yes Eclipse plug in JAuto Doc (source code documentation) Yes Eclipse plug in Clearcase Yes Java 6 less than build 20 Yes Squirrel SQL Client Yes IBM Rational Clear Case Yes IBM Rational Clear Quest Yes IBM DB2 V9.7 Yes Crystal Reports XI Rel 2 Yes Business Objects XI / Business Objects Enterprise Release 2 and 3.1 Yes Adobe Acrobat Yes MS SQL Server Management Studio Express Yes Aventail - for people with a laptop Yes BlueZone Yes WinSCP Yes CutePDF Yes Oracle Client Yes

Table 10 – Different Desktop Configurations



EXHIBIT C – FSFN Batches

Listed below are the FSFN, reporting, ETL and COBOL batch names. FSFN and Reporting Batches

# Environment Batch Description

1 Production 188Form_Template

2 Production 30 - Day Visitation Report By Agency

3 Production 30 - Day Visitation Report By District

4 Production Abuse During Services By Agency - Listing

5 Production Act_No_Lnk_Cln

6 Production Act_No_Lnk_Prv

7 Production Act_Posb_Cln

8 Production Act_Posb_Prv

9 Production Active Alerts - Exceptions

10 Production Active Alerts - Statewide Listing

11 Production Active Clients With No Link

12 Production Active Licensed Linked Providers

13 Production Active Licensed Providers With No Link

14 Production Active Linked Clients

15 Production Active Unlicensed Linked Providers

16 Production Active Unlicensed Providers With No Link

17 Production Adoption Eligibility Determinations Due

18 Production Adoption Eligible Children Tpr Complete Listing By Agency

19 Production Adoption Eligible Children Tpr Complete Listing By District

20 Production Adoptions Finalized By Month & Cumulative Sfy By Agency

21 Production Adoptions Finalized By Month & Cumulative Sfy By Agency Listing

22 Production Adoptions Finalized By Month & Cumulative Sfy By County

23 Production Adoptions Finalized By Month & Cumulative Sfy By District Listing

24 Production Adoptions Finalized By Month & Cumulative Sfy By Unit

25 Production Adoptive Home Supervision - Listing By Agency

26 Production Adoptive Home Supervision - Listing By District

27 Production Adoptive Home Supervision Statewide By District By Agency

28 Production Adoptive Home Supervision Statewide By District By County

29 Production Adoptive Home Supervision Statewide By District By Unit

30 Production Adult Investigation Alleged Victims Seen By Time By Agency

31 Production Adult Investigation Alleged Victims Seen By Time By County

32 Production Adult Investigation Alleged Victims Seen By Time By Unit

33 Production Adult Investigation Leaderboard - Statewide By District

34 Production Adult Investigation Victims Not Seen - District By Adult Investigation - Daily Listing

35 Production Adult Investigations At A Glance For Open Investigations By Agency

36 Production Adult Investigations Backlog Index By Agency

37 Production Adult Investigations Backlog Index By County

38 Production Adult Investigations Backlog Index By Unit




39 Production Adult Investigations By Zip Code - Listing

40 Production Adult Investigations Commenced By Time - Statewide By Agency

41 Production Adult Investigations Commenced By Time - Statewide By County

42 Production Adult Investigations Commenced By Time - Statewide By Unit

43 Production Adult Investigations Completed (Exit Cohort) By Agency

44 Production Adult Investigations Completed (Exit Cohort) By County

45 Production Adult Investigations Completed (Exit Cohort) By Unit

46 Production Adult Investigations Received By Intake Sequence Type By Agency

47 Production Adult Investigations Received By Intake Sequence Type By County

48 Production Adult Investigations Status Report - Daily

49 Production Adult Investigations Status Report By Agency - Monthly

50 Production Adult Investigations Status Report By District - Monthly

51 Production Adult Safety Assessments Reviewed By Supervisor By Time - Statewide By County

52 Production Adult Safety Assessments Reviewed By Supervisor By Time - Statewide By District

53 Production Adult Safety Assessments Submitted To Supervisor By Agency

54 Production Adult Safety Assessments Submitted To Supervisor By County

55 Production Adult Safety Assessments Submitted To Supervisor By Unit

56 Production Afcars Adoption Error Report By Agency

57 Production Afcars Adoption Error Report By District

58 Production Afcars Adoptions Compliance Rates Statewide By District

59 Production Afcars Foster Care Compliance Rates

60 Production Afcars Foster Care Error Report By Agency

61 Production Afcars Foster Care Error Report By District

62 Production Annual Finalized Adoptions By Intervals - Tpr Petition Filed To Tpr Order – Statewide By County

63 Production Annual Finalized Adoptions By Intervals- Goal Of Adoption To Tpr Order – Statewide By County

64 Production Annual Finalized Adoptions By Intervals- Tpr Order To Finalization – Statewide By County

65 Production Annual Finalized Adoptions By Intervals-Adoptive Placement To Finalization – Statewide By County

66 Production Annual Finalized Adoptions By Intervals-Length Of Time Tpr On Appeal – Statewide By County

67 Production Annual Finalized Adoptions By Intervals-Tpr Order To Adoptive Placement – Statewide By County

68 Production Approved Adoptive Families Face sheet

69 Production Business Objects Data Integrator Etl Process For Children seen Report.

70 Production Case Note Lag Time (Home Visit - Childs Current Residence) - District By Agency

71 Production Case Note Lag Time (Home Visit - Childs Current Residence) - District By Unit

72 Production Case Note Lag Time (Home Visit - Childs Current Residence) - District By Unit By Worker

73 Production Cases Closed Per Month-Statewide By Agency

74 Production Cases Closed Per Month-Statewide By County

75 Production Change In Placement

76 Production Child Investigation Alleged Victims Seen By Time District By Agency




77 Production Child Investigation Alleged Victims Seen By Time District By County

78 Production Child Investigation Alleged Victims Seen By Time District By Unit

79 Production Child Investigation And Special Condition Report By Agency

80 Production Child Investigation And Special Condition Report By District

81 Production Child Investigation Lack Of Recurrence Of Maltreatment Within Six Months Of Service Termination By Agency

82 Production Child Investigation Lack Of Recurrence Of Maltreatment Within Six Months Of Service Termination By District

83 Production Child Investigation Lack Of Recurrence Of Maltreatment Within Six Months Of Service Termination Summary

84 Production Child Investigation Leaderboard By Agency

85 Production Child Investigation Leaderboard By Unit

86 Production Child Investigation Victims And Children Not Seen - Listing By Agency

87 Production Child Investigation Victims And Children Not Seen - Listing By District

88 Production Child Investigations And Special Conditions Status Report Agency – Monthly

89 Production Child Investigations And Special Conditions Status Report District – Monthly

90 Production Child Investigations At A Glance For Open Investigations By Agency

91 Production Child Investigations At A Glance For Open Investigations By County

92 Production Child Investigations At A Glance For Open Investigations By County - Excel Format

93 Production Child Investigations At A Glance For Open Investigations By Unit

94 Production Child Investigations At A Glance For Open Investigations By Units - Excel Format

95 Production Child Investigations By Zip Code By Agency

96 Production Child Investigations By Zip Code By District

97 Production Child Investigations Commenced By Time By Agency

98 Production Child Investigations Commenced By Time By County

99 Production Child Investigations Commenced By Time By County - Excel Format

100 Production Child Investigations Commenced By Time By Unit

101 Production Child Investigations Completed (Entry Cohort) By Agency

102 Production Child Investigations Completed (Entry Cohort) By County

103 Production Child Investigations Completed (Entry Cohort) By Unit

104 Production Child Investigations Completed (Exit Cohort) By Agency

105 Production Child Investigations Completed (Exit Cohort) By County

106 Production Child Investigations Disposition Detail A By Agency

107 Production Child Investigations Disposition Detail A By District

108 Production Child Investigations Disposition Detail B By Agency

109 Production Child Investigations Disposition Detail B By District

110 Production Child Investigations Institutional By Provider - District By Intake # Listing

111 Production Child Investigations Institutional By Provider Agency By Intake # Listing

112 Production Child Investigations Received By Intake Sequence Type Statewide By District By Agency

113 Production Child Investigations Received By Intake Sequence Type Statewide By District By County

114 Production Child Investigations Received By Intake Sequence Type Statewide By District By Unit

115 Production Child Most Serious Findings On Closed Investigations - Statewide By Agency

116 Production Child Most Serious Findings On Closed Investigations - Statewide By County




117 Production Child Trust Fund Placement

118 Production Children Achieving Permanency Within 12 Months - Statewide By District By Agency

119 Production Children Achieving Permanency Within 12 Months - Statewide By District By County

120 Production Children Achieving Permanency Within 12 Months - Statewide By District By Unit

121 Production Children Active Receiving In-Home Or Out-Of-Home Services - Monthly Listing By Agency

122 Production Children Active Receiving In-Home Or Out-Of-Home Services - Monthly Listing By District

123 Production Children Active Receiving In-Home Or Out-Of-Home Services Daily Listing By Agency

124 Production Children Active Receiving In-Home Or Out-Of-Home Services Daily Listing By District

125 Production Children Adopted Within 24 Months District By Agency

126 Production Children Adopted Within 24 Months District By County

127 Production Children Adopted Within 24 Months District By Unit

128 Production Children And Young Adults Active By Primary Worker By Agency

129 Production Children And Young Adults Active By Primary Worker By County

130 Production Children And Young Adults Active By Primary Worker By County - Excel Format

131 Production Children And Young Adults Active By Primary Worker By County Monthly - Excel Format

132 Production Children And Young Adults Active By Primary Worker By Unit

133 Production Children And Young Adults Active By Primary Worker By Unit By Worker

134 Production Children Available For Adoption And Web Status 135 Production Children Available Tpr'D With Goal Of Adopt Waiting For Adoption By Agency

136 Production Children Available Tpr'D With Goal Of Adopt Waiting For Adoption By County

137 Production Children Available Tpr'D With Goal Of Adopt Waiting For Adoption By Unit

138 Production Children Entering Out-Of-Home Care After Prior Reunification - Listing By Agency

139 Production Children Entering Out-Of-Home Care After Prior Reunification - Listing By District

140 Production Children Entering Out-Of-Home Care After Prior Reunification - Statewide By Agency

141 Production Children Entering Out-Of-Home Care After Prior Reunification - Statewide By County

142 Production Children Entering Out-Of-Home Care After Prior Reunification - Statewide By Unit

143 Production Children Exiting Foster Care By Time In Care

144 Production Children Exiting Out Of Home Care By Exit Reason By Agency

145 Production Children Exiting Out Of Home Care By Exit Reason By County

146 Production Children Exiting Out Of Home Care By Exit Reason By County - Excel Format

147 Production Children Exiting Out Of Home Care By Exit Reason By Unit

148 Production Children Identified As Victims

149 Production Children In Out Of Home Care By Legal Status By Length Of Stay (Monthly And Annual Report) - Statewide By Agency

150 Production Children In Out Of Home Care By Legal Status By Length Of Stay (Monthly And Annual Report) - Statewide By County

151 Production Children In Out Of Home Care By Legal Status By Length Of Stay (Monthly And Annual Report) - Statewide By Unit

152 Production Children In Out-Of-Home Care 24 Months Or More With Goal Of Adoption District By Unit

153 Production Children In Out-Of-Home Care 24 Months Or More With Goal Of Adoption Statewide By Agency




154 Production Children In Out-Of-Home Care 24 Months Or More With Goal Of Adoption Statewide By County

155 Production Children In Out-Of-Home Care By Time In Care By Agency

156 Production Children In Out-Of-Home Care By Time In Care By County

157 Production Children In Out-Of-Home Care By Time In Care By Unit

158 Production Children Out-Of-Home-Care By Time In Care By Agency

159 Production Children Out-Of-Home-Care By Time In Care By District

160 Production Children Reunified Within 12 Months By Agency

161 Production Children Reunified Within 12 Months By County

162 Production Children Reunified Within 12 Months By Unit

163 Production Children Reunified Within 12 Months Listing By Agency

164 Production Children Reunified Within 12 Months Listing By District

165 Production Children Seen Not Seen - Daily Listing By Agency

166 Production Children Seen Not Seen - Daily Listing By District

167 Production Children Seen Not Seen - Monthly Listing By Agency

168 Production Children Seen Not Seen - Monthly Listing By District

169 Production Children Seen Not Seen Number And Percent By Agency - Daily

170 Production Children Seen Not Seen Number And Percent By Agency - Monthly

171 Production Children Seen Not Seen Number And Percent By County - Daily

172 Production Children Seen Not Seen Number And Percent By County - Monthly

173 Production Children Seen Not Seen Number And Percent By Unit - Daily

174 Production Children Seen Not Seen Number And Percent By Unit - Monthly

175 Production Children Seen Not Seen Number And Percent By Unit By Worker – Daily

176 Production Children Seen Not Seen Number And Percent By Unit By Worker – Monthly

177 Production Children Served In Out-Of-Home Care - Length Of Removal By Number Of Placements Statewide By District By Agency

178 Production Children Served In Out-Of-Home Care - Length Of Removal By Number Of Placements Statewide By District By County

179 Production Children Served In Out-Of-Home Care - Length Of Removal By Number Of Placements Statewide By District By Unit

180 Production Children With Recurrence Of Maltreatment Within Six Months Of Previous Investigation - Listing By Agency

181 Production Children With Recurrence Of Maltreatment Within Six Months Of Previous Investigation - Listing By District

182 Production Children With Recurrence Of Maltreatment Within Six Months Of Previous Investigation By Agency

183 Production Children With Recurrence Of Maltreatment Within Six Months Of Previous Investigation By County

184 Production Children With Recurrence Of Maltreatment Within Six Months Of Previous Investigation By Unit

185 Production Client Eligibility Data Report For Cost Allocation

186 Production Client Eligibility Data Report For Cost Allocation Monthly

187 Production Clients Active In Out-Of-Home Care-Listing By Agency

188 Production Clients Active In Out-Of-Home Care-Listing By District

189 Production Court Activities Summary

190 Production Data Comparison Report




191 Production Dcf_Act_Link_Prv

192 Production Dcf_Act_Posp_Link_Prv

193 Production Dcf_Act_Unk_Link_Prv

194 Production Demographics Of Children Receiving In-Home Services By Agency

195 Production Demographics Of Children Receiving In-Home Services By County

196 Production Demographics Of Children Receiving Out-Of-Home Services - Statewide By Agency

197 Production Demographics Of Children Receiving Out-Of-Home Services - Statewide By County

198 Production Diligent Search Activity

199 Production Duplicate Provider Report

200 Production Family Assessments By Timeframes - Agency

201 Production Family Assessments By Timeframes - District

202 Production Find Available Family Report

203 Production Fingerprints Birth Verification Photographs - Not Obtained-Listing By Agency

204 Production Fingerprints Birth Verification Photographs - Not Obtained-Listing By District

205 Production Fingerprints Birth Verification Photographs - Obtained By Agency - Monthly

206 Production Fingerprints Birth Verification Photographs - Obtained By County - Monthly

207 Production Fingerprints Birth Verification Photographs - Obtained By Unit - Monthly

208 Production Fingerprints Birth Verification Photographs Obtained By Agency - Daily

209 Production Fingerprints Birth Verification Photographs Obtained By County - Daily

210 Production Fingerprints Birth Verification Photographs Obtained By Unit - Daily

211 Production Florida Submission

212 Production Goal Of Permanently Committed Children

213 Production Hotline Intakes Received – Daily

214 Production Hotline Intakes Received – Monthly

215 Production Hotline Intakes Received - Monthly - Excel Format

216 Production Hotline Intakes Received - Daily - Excel Format

217 Production Inactive Clients With No Link

218 Production Inactive Linked Clients

219 Production Inactive Linked Providers

220 Production Inactive Providers With No Link

221 Production Information And Referral

222 Production Initial Child Safety Assessments Reviewed By Supervisor By Time - Statewide By Agency

223 Production Initial Child Safety Assessments Reviewed By Supervisor By Time - Statewide By County

224 Production Initial Child Safety Assessments Reviewed By Supervisor By Time - Statewide By Unit

225 Production Initial Child Safety Assessments Submitted To Supervisor By Time - Statewide By Agency

226 Production Initial Child Safety Assessments Submitted To Supervisor By Time - Statewide By County

227 Production Interstate Compact(Icpc) Children From Florida In Another State

228 Production Interstate Compact(Icpc) Children In Florida From Another State

229 Production Investigations-No Jurisdiction (Adult) By Agency

230 Production Investigations-No Jurisdiction (Adult) By District




231 Production Investigations-No Jurisdiction (Child) By Agency

232 Production Investigations-No Jurisdiction (Child) By District

233 Production Judicial Reviews Completed On Time

234 Production Judicial Reviews Due In 60 Days By Agency

235 Production Judicial Reviews Due In 60 Days By District

236 Production Judicial Reviews Overdue - Monthly Listing By Agency

237 Production Judicial Reviews Overdue - Monthly Listing By District

238 Production Mcr Active Missing Children

239 Production Mcr Missing Child Location Efforts

240 Production Medicaid Activity

241 Production Merged, Deleted, And Linked Providers - Listing

242 Production Milestone Case Future Summary

243 Production Milestone Case Overdue Summary

244 Production Milestone Legal Future Summary

245 Production Milestone Legal Overdue Summary

246 Production Missing Adult Ssn

247 Production Missing Child Ssn – Agency

248 Production Missing Child Ssn – District

249 Production Monthly Ncands Exception Report

250 Production Number And Percent Of Children Returning To Foster Care Within One Year Of Reunification

251 Production Oca Reconciliation

252 Production Oca Roll-Up

253 Production On call Schedule Listing

254 Production Overpayment Activity

255 Production Parental And Separated Sibling Visits

256 Production Pending Invoices

257 Production Person Merge

258 Production Person Merge Listing

259 Production Placement Of Children In Licensed Residential Group Care

260 Production Placements With Ending Reason Of Duplicate Provider Cleanup

261 Production Possible Active Client Links

262 Production Possible Active Licensed Provider Links

263 Production Possible Active Unlicensed Provider Links

264 Production Possible Inactive Client Links

265 Production Possible Inactive Provider Links

266 Production Potential Clients For Independent Living Services By Agency - Monthly Listing

267 Production Potential Clients For Independent Living Services By District - Monthly Listing

268 Production Potential Duplicates-Based On Name D.O.B

269 Production Potential Duplicates-Based On-SSN

270 Production Pre And Post Case Merge Report Monthly

271 Production Pre And Post Case Merge Report Weekly




272 Production Pre And Post Case Split Report Monthly

273 Production Pre And Post Case Split Report Weekly

274 Production Prepayment Authorization

275 Production Provider Listing - Listing (#-D) – Agency

276 Production Provider Listing - Listing (#-D) – District

277 Production Provider Listing - Listing (E-K) – Agency

278 Production Provider Listing - Listing (E-K) – District

279 Production Provider Listing - Listing (L-Q) – Agency

280 Production Provider Listing - Listing (L-Q) – District

281 Production Provider Listing - Listing (R-Z) – Agency

282 Production Provider Listing - Listing (R-Z) – District

283 Production Removal Placement Exceptions Listing By Agency

284 Production Removal Placement Exceptions Listing By District

285 Production Residential Treatment Center Placement Judicial Review

286 Production Review Continuance Events

287 Production Security Administration - Changes

288 Production Security Administration - Point In Time

289 Production Statistical Report Of Cases Merged And Split Monthly

290 Production Summary And Listing Report Run Times

291 Production Summary And Listing Report Run Times

292 Production TANF Eligibility Determinations Due

293 Production Timeliness Of Data Entry - Statewide By Agency

294 Production Timeliness Of Data Entry - Statewide By County

295 Production Timeliness Of Data Entry - Statewide By Unit

296 Production Timely Filing Of Predisposition Study

297 Production Title Iv-E Eligibility Determinations Due

298 Production Trust Account Reconciliation

299 Production Voided Invoice

300 Production Weekly BOE Point In Time Security

301 Production Weekly BOE Security Changes

302 Production Weekly Data Comparison

303 Production Worker Contacts With Birth Parents By Agency

304 Production Worker Contacts With Birth Parents Listing By Agency

305 Production Worker Contacts With Birth Parents Listing By District



ETL Batches


1 Production Sync Data warehouse tables with OLTP for any delete and merge records

2 Production Sync CBC tables with OLTP for any delete and merge records

3 Production Sync Datamart tables with OLTP for any delete and merge records

4 Production Incremental ETL Process for Location, Security, Assignment tables in Datamart

5 Production Incremental ETL Process for Case, Case Participant, Case Participant Info, Mcr, Notes tables in Datamart

6 Production Incremental ETL Process for Common Management, Investigation Modules of Datamart

7 Production Incremental ETL Process for Service Management, Provider Modules of Datamart

8 Production Incremental ETL Process for Eligibility tables of Datamart

9 Production Incremental ETL Process for Financial tables of Datamart

10 Production Incremental ETL Process to Update the control table of the Datamart

11 Production Report ETL Process for Children Active Receiving Services Report and Children Active Receiving Services Universe

12 Production Report ETL Process for Children Seen and Not Seen Report

13 Production Report ETL Process for Finger Prints, Birth Certificates and Photographs

14 Production Report ETL Process for Children Available for Adoption

15 Production Report ETL Process for 30 Day Visitation

16 Production ETL Process for Children Seen Extract for External Interface

17 Production Report ETL for Provider and Episode Service Rate Validation

18 Production ETL Process for Worker Ldap Extract

19 Production FTP Process for Children Seen not seen extract for External Interface

20 Production Report ETL Process for Eligibility Cost Allocation report

21 Production ETL Process for Data warehouse Incremental. This Step of the process Updates the timeframes for the incremental steps run in STEP2 - STEP4

22 Production ETL Process for Data warehouse Incremental. This Step of the process Updates tables A through CP

23 Production ETL Process for Data warehouse Incremental. This Step of the process Updates tables D through ME

24 Production ETL Process for Data warehouse Incremental. This Step of the process Updates tables ME through Z

25 Production ETL Process for Data warehouse Incremental. This Step of the process Updates the timeframes for the next incremental run

26 Production ETL Process for Creating Reference Data/Pseudo Ids for CBC Incremental Process

27 Production ETL Process for Cbc Incremental CBC_ALLEGATION_Z , CBC_CHLD_INVS_DISTRICT_Z and CBC_INVS_PART_Z

28 Production

ETL Process for Cbc Incremental CBC_CTKR_HIST_Z CBC_CTKR_Z CBC_DEPN_GOAL_Z

29 Production

ETL Process for Cbc Incremental CBC_DEPN_RMVL_REV_Z CBC_DEPN_RMVL_Z CBC_PROV_COMBINED_Z

30 Production ETL Process for Cbc Incremental CBC_PRSN_ADDR_LNK_Z CBC_ADDR_Z

31 Production

ETL Process for Cbc Incremental CBC_PLAC_Z CBC_PROV_ADDR_LNK_Z CBC_PROV_AREA_Z




32 Production

ETL Process for Cbc Incremental CBC_UNT_ADDR_LNK_Z CBC_UNT_AREA_Z CBC_UNT_STAT_HIST_Z

33 Production

ETL Process for Cbc Incremental CBC_DISPOSITION_DETAIL_Z CBC_INVS_APPROVAL_HISTORY_Z CBC_INVS_APPROVAL_Z

34 Production

ETL Process for Cbc Incremental CBC_CODE_DESC CBC_CODE_DESC_LRG CBC_CODE_DESC_STATIC

35 Production

ETL Process for Cbc Incremental CBC_DEPN_REAS_SRVC_EPISODE_Z CBC_DEPN_REAS_SRVC_LVNG_ARRNG_Z CBC_DEPN_RMVL_CTKR_Z

36 Production

ETL Process for Cbc Incremental CBC_PRSN_AKA_Z CBC_PRSN_ELIG_Z CBC_CAS_CHRON_NOTES_Z

37 Production

ETL Process for Cbc Incremental CBC_WRKRPH_Z CBC_WRKR_Z CBC_UNTMGR_Z

38 Production

ETL Process for Cbc Incremental CBC_CPS_INVS_SFTY_FCTRS_CHILD_IH_DTLS_Z CBC_CPS_INVS_SFTY_FCTRS_CHILD_II_Z CBC_INVESTIGATION_Z

39 Production

ETL Process for Cbc Incremental CBC_CAS_HIST_Z CBC_CAS_OTH_HIST_Z CBC_CAS_OTH_Z

40 Production

ETL Process for Cbc Incremental CBC_DEPN_LIVAR_Z CBC_DEPN_HIST_Z CBC_DEPN_LEGL_STAT_Z

41 Production

ETL Process for Cbc Incremental CBC_PROV_FCL_Z CBC_PROV_PRSN_Z CBC_PROVPH_Z

42 Production

ETL Process for Cbc Incremental CBC_PRSN_PRSC_MDCN_HIST_Z CBC_PRSN_RACE_Z CBC_PRSNID_Z

43 Production

ETL Process for Cbc Incremental CBC_PRSNPH_Z CBC_PROV_UNT_Z CBC_PRSN_Z

44 Production ETL Process for Cbc Incremental CBC_CAS_CHRON_TYP_Z CBC_CAS_CHRON_Z

45 Production

ETL Process for Cbc Incremental CBC_CAS_PRSN_ID_Z CBC_CAS_PRSN_RELN_Z CBC_CAS_PRSN_Z

46 Production

ETL Process for Cbc Incremental CBC_CAS_WRKR_DEPN_Z CBC_CAS_WRKR_Z CBC_CAS_Z

47 Production

ETL Process for Cbc Incremental CBC_PRSN_PRSC_MDCN_Z CBC_UNIT_Z CBC_UNTPH_Z

48 Production

ETL Process for Cbc Incremental CBC_2_1_DEPN_WF CBC_2_2_CAN_PRSN_WF CBC_AREA_Z

49 Production ETL Process for Cbc Incremental CBC_CPS_INVS_SFTY_FCTRS_CHILD_IH_Z CBC_CPS_INVS_SFTY_FCTRS_CHILD_II_DTLS_Z




50 Production ETL Process for Updating Control Time stamp for CBC Process

51 Production Report ETL process for Child Investigation Status Process

52 Production Creates a Trigger File to indicate Report ETL Process has been completed

53 Production ETL Process for ECI Extract

54 Production Ftp Process for ECI Extract

55 Production ETL Process for ECI Extract

56 Production Daily ETL Process comparing ICWSIS Data with FSFN Data

57 Production ETL Process to compare counts from OLTP Tables

58 Production ETL Process to compare counts from Dw and Datamart Tables

59 Production ETL Process that obtains all transactions from Mid OLTP from Previous Day

60 Production FTP Process for Tran stats

61 Production ETL Process to load to summary of all transactions for previous day

62 Production Report ETL Process for On call Schedule

63 Production Report ETL Process for Milestone Reports

64 Production ETL Process for active children that deals with Case Plans, Family Assessment, Safety Plan, Out of Home Plan

65 Production Report ETL Process for Potential Duplicates Report

66 Production Report ETL Process for Continuance Event

67 Production Report ETL for 'NYTD Survey'

68 Production Report ETL Process for Diligent Search

69 Production

ETL Process for Creating CBC File CBC_ADDR_Z_FF CBC_CAS_CHRON_Z_FF CBC_CAS_CHRON_PRSN_Z_FF

70 Production

ETL Process for Creating CBC File CBC_CAS_OTH_HIST_Z_FF CBC_CAS_OTH_Z_FF CBC_CAS_PRSN_ID_Z_FF

71 Production

ETL Process for Creating CBC File CBC_DEPN_LEGL_STAT_Z_FF CBC_DEPN_RMVL_Z_FF CBC_DEPN_LIVAR_Z_FF

72 Production

ETL Process for Creating CBC File CBC_PROV_PRSN_Z_FF CBC_PROV_UNT_Z_FF CBC_PROVPH_Z_FF

73 Production

ETL Process for Creating CBC File CBC_PRSN_RACE_Z_FF CBC_PRSN_ELIG_Z_FF CBC_PRSN_Z_FF

74 Production

ETL Process for Creating CBC File CBC_UNT_ADDR_LNK_Z_FF CBC_UNTPH_Z_FF CBC_CPS_INVS_SFTY_FCTRS_CHILD_IH_DTLS_Z_FF

75 Production ETL Process for Creating CBC File UNIT_XREF_SYNC_FF2 WRKR_XREF_SYNC_FF2

76 Production

ETL Process for Creating CBC File CBC_CAS_CHRON_NOTES_Z_FF CBC_CAS_CHRON_TYP_Z_FF CBC_CAS_HIST_Z_FF

77 Production

ETL Process for Creating CBC File CAS_XREF_SYNC_FF2 EMPL_XREF_SYNC_FF2 PROV_XREF_SYNC_FF2




78 Production

ETL Process for Creating CBC File CBC_PLAC_Z_FF CBC_ALLEGATION_FF CBC_AREA_Z_FF

79 Production

ETL Process for Creating CBC File CBC_DEPN_HIST_Z_FF CBC_DEPN_GOAL_Z_FF CBC_DEPN_RMVL_REV_Z_FF

80 Production

ETL Process for Creating CBC File CBC_PRSN_ADDR_LNK_Z_FF CBC_PRSN_PRSC_MDCN_HIST_Z_FF CBC_PRSN_AKA_Z_FF

81 Production

ETL Process for Creating CBC File CBC_UNT_Z_FF CBC_UNT_AREA_Z_FF CBC_WRKR_Z_FF

82 Production

ETL Process for Creating CBC File CBC_CPS_INVS_SFTY_FCTRS_CHILD_IH_Z_FF CBC_CPS_INVS_SFTY_FCTRS_CHILD_II_DTLS_Z_FF CBC_CPS_INVS_SFTY_FCTRS_CHILD_II_Z_FF

83 Production

ETL Process for Creating CBC File CBC_CAS_PRSN_RELN_Z_FF CBC_CAS_PRSN_Z_FF CBC_CAS_Z_FF

84 Production

ETL Process for Creating CBC File CBC_CODE_DESC_LRG_Z_FF CBC_CODE_DESC_Z_FF CBC_CODE_DESC_STATIC_Z_FF

85 Production

ETL Process for Creating CBC File CBC_DEPN_RMVL_CTKR_Z_FF CBC_DEPN_REAS_SRVC_LVNG_ARRNG_Z_FF CBC_DEPN_REAS_SRVC_EPISODE_Z_FF

86 Production

ETL Process for Creating CBC File CBC_INVS_APPROVAL_HISTORY_FF CBC_INVS_PART_FF CBC_PROV_FCL_Z_FF

87 Production

ETL Process for Creating CBC File CBC_PROV_ADDR_LNK_Z_FF CBC_PROV_AREA_Z_FF CBC_PROV_COMBINED_Z_FF

88 Production

ETL Process for Creating CBC File CBC_CAS_WRKR_DEPN_Z_FF CBC_CAS_WRKR_Z_FF CBC_CHLD_INVS_DISTRCT_FF

89 Production

ETL Process for Creating CBC File CBC_CTKR_Z_FF CBC_CTKR_HIST_Z_FF CBC_DEPN_Z_FF

90 Production

ETL Process for Creating CBC File CBC_DISPOSITION_DETAIL_FF CBC_INVESTIGATION_FF CBC_INVS_APPROVAL_FF

91 Production

ETL Process for Creating CBC File CBC_PRSN_PRSC_MDCN_Z_FF CBC_PRSNID_Z_FF CBC_PRSNPH_Z_FF

92 Production

ETL Process for Creating CBC File CBC_WRKRPH_Z_FF CBC_UNT_STAT_HIST_Z_FF CBC_UNTMGR_Z_FF

93 Production Email Process to inform the completion of CBC Jobs

94 Production Report ETL Process for Monthly Children Active Receiving Services

95 Production Report ETL Process for Monthly Finger Prints , Birth Certificates and Photographs

96 Production Report ETL Process for Monthly Case Plan, JR and Services

97 Production Report ETL Process for Placement Stability Report

98 Production Report ETL Process for Monthly Eligibility Cost Allocation report




99 Production Report ETL Process for Investigation Zip Report

100 Production Report ETL Process for Case participants at the end of the month

101 Production Report ETL Process for Worker Contacts with Birth Parents Report

102 Production ETL Process for Service Snapshot at the end of the Month

103 Production ETL Process for Service Snapshot for a Complete Month

104 Production ETL Process that tracks the Monthly Children Seen and Not Seen for analytical Purposes

105 Production ETL Process for all children Discharged from Services

106 Production ETL Process with all the Monthly Mcodes

107 Production ETL Process with all the Quarterly Mcodes

108 Production Report ETL Process for 7 Series



111 Production ETL Process to Load Afcars from Datamart to OLTP

112 Production Report ETL Process for Children Identified as Victims

113 Production Report ETL Process for Adoption Interval Children. Annually, Last Saturday of July.

114 Production FIXED RATE BATCH

115 Production PRE PAY FIXED PRICE

116 Production DAILY PRE PAY ETL

117 Production AD HOC LOAD BO USER ETL

118 Production AD HOC ADMINISTRATOR FISCAL SECURITY ETL

119 Production AD HOC BO ZONE SECURITY ETL

120 Production AD HOC INCREMENTAL BO SECURITY ETL

121 Production AD HOC BUSINESS DAYS ETL

122 Production AD HOC SERVICE TYPE DIMENSION ETL

123 Production AD HOC DATE DIMENSION ETL

124 Production AD HOC DEMOGRAPHIC DIMENSION ETL

125 Production AD HOC ELIGILITY TYPES DIMENSION ETL

126 Production AD HOC INCREMENTAL BO FISCAL AGENCY SECURITY ETL

127 Production AD HOC POPULATION LOAD ETL

128 Production DAILY FLORIDA SUBMISSION ETL

129 Production DAILY OCA ETL

130 Production DAILY TRUST ACCOUNT PLACEMENT CHANGE ETL

131 Production AD HOC VISITATION DIMENSION ETL

132 Production ETL TO POPULATE LEGAL EXCEPTION REPORT COBOL Batches


1 Production Families First Network

2 Production BIG BEND CBC EAST FA

3 Production BIG BEND CBC WEST FA

4 Production PARTNERSHIP FOR STRONG FAMILIES

5 Production CLAY AND BAKER KIDS NET INC




6 Production Family Support Services

7 Production FAMILY MATTERS OF NASSAU COUNT

8 Production St Johns County Commission

9 Production CBC of Brevard

10 Production Family Services of Metro Orlando

11 Production CBC of Seminole

12 Production Children's Network of SW Florida

13 Production Child and Family Connections

14 Production ChildNet Inc

15 Production CHARLEE of Dade County

16 Production Our Kids Inc.

17 Production COMM PARTNERSHIP FOR CHILDREN

18 Production Kids Central Inc.

19 Production HEARTLAND FOR CHILDREN INC

20 Production United for Families

21 Production FAMILY CONTINUITY PROGRAM

22 Production Hillsborough KIDS Inc.

23 Production YMCA North

24 Production Sarasota YMCA

25 Production Central Office Child Welfare

26 Production Eckerd Youth Alternatives Inc.

27 Production Centre for Family & Child Enrich

28 Production Children's Home Society

29 Production Family Resource Center

30 Production His House Children's Home

31 Production Kids Hope United

32 Production Wesley House Family Services

33 Production CA-7 Other Cobol Job names

34 Production Birth Day Batch

35 Production Pre-calc-on-going

36 Production Birth day batch Parameter update

Platform Software Version Status

Application Layer Java J2EE Bea Web Logic

1.5 9.2

Database Layer IBM DB2 z/OS, IBM DB2 Universal Database (UDB)

9.1

Data Warehouse Layer

SAP Business Objects Data Services

12.2

Report Layer Business Objects XI SP5

11.5



Hardware Server Type Server Name Hosted At Operating System

Production Application Servers

NSRC Red Hat Enterprise Linux 5.4

Database NSRC Z/OS 1.12

Database NSRC Red Hat Enterprise Linux 5.4

Batch Servers

NSRC Windows Server 2003 R2

Report Servers


UAT Test Application Server




Report Servers


System Test Application Server




Report Servers


Development Application Server

NSRC Windows XP

Database

NSRC Z/OS 1.12

Report Server




Mobile Specs Platform Software Version Status

Application Layer Blackberry Operating System (BBOS)

6.0 Supported

Database Layer None

Hardware Server Type Server Name Hosted at Operating System

Production Application Download Server

NSRC Windows Server 2003 Standard Edition R2

Web Services NSRC Linux Red Hat 5.4

Database

Test Application Download Server



Database

Development Application Download Server



Database

(End of Document)

STATE OF FLORIDA · 2012. 2. 28. · STATE OF FLORIDA – DEPARTMENT OF CHILDREN AND FAMILIES...

Documents

Transcript of STATE OF FLORIDA · 2012. 2. 28. · STATE OF FLORIDA – DEPARTMENT OF CHILDREN AND FAMILIES...