1 Converging on Standards: Tool Migration Bob Padgett Mark Wagner

2 ●The purpose and the mission of the Child Support Enforcement Program are derived from title IV-D of the Social Security Act oTo enhance the well-being of children by assuring that assistance in obtaining support, including financial and medical, is available to children through locating parents, establishing paternity, establishing support obligations, and monitoring and enforcing those obligations ●Michigan’s child support program operates through the cooperative efforts of three agencies oThe Department of Human Services Office of Child Support oProsecuting attorneys in each county oFriends of the court in each county MiCSES Background

3 ●DHS Office of Child Support oLocate a parent oVoluntary paternity establishment oA referral to establish a court order for paternity and/or support oReferring an existing order for enforcement oRecommending action on an interstate case ●Prosecuting Attorney oObtaining a court order to establish paternity oObtaining court orders for custody, support, and parenting time oLocating a parent MiCSES Users

4 ●Friend of the Court oInvestigating and make recommendations regarding custody, parenting time, and support oEnforcing custody, parenting time, and support orders oModifying custody, parenting time, and support orders oRegister Michigan orders in other states oInitiating income withholding orders oResolving collection problems oProviding alternative dispute resolution oLocating a parent MiCSES Users

5 ●The MiCSES system provides data to and utilizes data from the Data Warehouse oMaintain an address history from a number of sources in support of the location process oCompile statewide case data and manage the interaction with the Federal Case Registry oLink New Hire Data to Court Orders and produce Income Withholding Notices oCompile Financial Institution Data Match account data for use in enforcement actions oCompile Federal Reporting data for use in the OCSE157 and OCSE 34A reports oCompile Medical Insurance coverage information for provision to Title XIX MiCSES Data Warehouse

6 ●Federal Parent Locator System – (SSA, Veteran’s Affairs, DOD, FBI) ●National Directory of New Hires - (New hire information from employers) ●Federal Case Registry - (Nation-wide information) ●Unemployment Agency - (Unemployment claimant benefit) ●Department of Community Health - (Health insurance and Medicaid data) ●Department of Natural Resources - (Fishing, hunting licenses) ●Department of Corrections - (Person, location, parole information) ●Department of Treasury - (Employee withholding taxes) ●State Directory of New Hires - (New hire information from employers) ●Financial Institutions - (Multi-state financial institution data match) ●State Licensing Agencies - (Professional license data) ●Department of State - (Drivers license data) ●Michigan State Police – (Personal protection orders) MiCSES DW Data Sources

7 MiCSES Data Warehouse BI Query CSES_DW APPLICATION SCREENS: MENUS / QUERY SELECTION Main Screen (CSES_DW Primary Screen: Menu/Report Selection) Select by Functional Area:ORSelect by Function:  Standard  Locate People & Addresses  Friend of Court  Locate Employment & Income  FIDM / MSFIDM  Locate Assets & Licenses/FIDM (V3.2.0 Queries)  County Specific Queries  Friend of Court  Federal Reporting

8 ●BI Query oUnsupported Version ●CITRIX oUnsupported Version ●Servers o5 Windows NT Servers ●Teradata oDrivers NOT compliant with WINDOWS NT MiCSES BI Query Environment

9 ●Analysis of Options oUpgrade current Hardware/OS/Application code oDeploy access via MiCSES Oracle Forms or J2EE oDeploy access via DHS Business Objects oShut down - Discontinue the application MiCSES Potential Solutions

10 ●Desktop Standard Options oBusiness Intelligence  Business Objects XI R2 oReporting Tools  Crystal Reports XI R2 State Standards – Business Objects

11 ●MiCSES User Requirements and Functional Design ●MOU with DIT-Agency Services-DHS ●SOW - Business Objects Consultant oReview/Analyze overall reporting requirements oReview/Analyze database structures/views oDesign/Create Business Objects universe(s) based on reporting requirements and underlying structures oProvide full testing of all universes oProvide documentation on universes as required oLayout overall plan for report creation in Business Objects oInterface with DHS BO development staff oAssist MiCSES development staff in aligning to DHS Business Objects processes and standards MiCSES How We Got There

12 ●Five Servers oDHS has four servers oMiCSES purchased a new server oData encryption ●Load Balancing oDetermine number of concurrent users oServer weight calculation for load balancing ●Communication Between Organizations and Upgrades oHave to adapt to different organizational goals and policies DHS - Business Objects Server Cluster

13 ●Repository Statistics oUniverses  DHS – 34  MiCSES – 2 oReports  DHS – 628  MiCSES – 82 oUsers  DHS – 7,846  MiCSES – 1,060 oQueries  DHS – July-59,000 Aug-67,000 Sep-22,000 Oct-39,000  MiCSES - July-32,000 Aug-40,000 Sep-15,000 Oct-20,000 DHS and MiCSES Statistical Information

14 ●Business Objects XI R2 oPlan to upgrade to XI R2 in 2008 ●Test/Development and DR oInvestigate and plan to develop a test/development & DR Environment ●Enterprise Business Objects Licenses oInvestigate an enterprise license strategy The Future

15 Q & A The End