1. TxDPS TLETS Update TCJIUG May 2, 2008 Tena Watson

2. Conversions to new TLETS –Progress Report –Common Technical Issues Relevant Projects –Criminal History Information Exchange Format –Financial Responsibility Verification Program –Mental Health Continuity of Care –On the Horizon Topics

3. Transition Status Fully Converted  ~ 490 local agencies  3 TxDPS HQ Divisions In process  ~ 15 local agencies have started  1 THP Division Scheduled  ~ 35 local agencies are scheduled Goal is 20-30 sites per week in order to make the September 2008 deadline

4. General Process 5 steps to the cutover: 1.Security Review Process 2.Initial Contact 3.Exchange Information 4.Configuration by TxDPS & local agency 5.Cutover and cleanup

5. Satellite Connectivity

6. Network Configuration (satellite) TxDPS provides subnet of static IP addresses HN7700 has Ethernet port Single Device (not on a network) –Connects directly into HN7700 with a standard cable Multiple devices –May use our IP addresses with a standard Switch –May use NAT to translate our addresses using enterprise level router –May choose to use two NIC cards

8. Local Agency Challenges Agency participants neglect to review TxDPS provided documentation http://www.txdps.state.tx.us/director_staff/information_management/tlets/tletsindex.htm Documentation and Process is lengthy Agency technical staff non-existent or too busy. Agency does not prepare their network prior to scheduled date. Some difficulty with scheduling interface vendors Agency does not own necessary equipment Agency believes the move is optional

9. Coordinating Efforts TxDPS allows the local agency to identify the dates of cutover. It is the agency’s responsibility to communicate schedules to TxDPS

10. Operator Information User IDs for all Operators, including those behind an interface. Credentials are validated for workstation operators. Authority granted to all operators. Training must be kept up to date to prevent revocation of authorization

11. Patience is Appreciated TxDPS resources are limited TxDPS makes accommodations where possible Please voice your concerns Please make recommendations

12. Questions/Comments about Re-Engineering?

13. NLETS Chief Project Criminal History Information Exchange Format Purpose: –Support Bureau of Justice Statistics National Criminal History Improvement Program (BJS, NCHIP) –Leverage standards expected from National Information Exchange Model (NIEM) –Proof of Concept: facilitating State efforts to implement the standardized rap sheet in XML, either using GJXDM or NIEM

14. NLETS CHIEF Project NLETS will serve as custodian of the national standard Rap Sheet technical specifications, software artifacts and documentation NLETS to advance and promote the standardized Rap Sheet and facilitate Joint Task Force initiatives Development of Rap Sheet Information Exchange Package Documentation ( IEPD) which is NIEM conformant

15. CHIEF Pilot States Florida Kentucky Maine Massachusetts Pennsylvania Texas New York Wisconsin

16. CHIEF Objectives Develop strategies and tools to transform between GJXDM and NIEM Support the Joint Task Force in the development of a Next Generation Rap Sheet with additional content and presentation formatting Develop Service Oriented Architectural frameworks in the pilot states Provide comprehensive statistics to support crime prevention and recidivism efforts Document “Lessons Learned” and recommend extensions and/or revisions to the NIEM

17. Architecture

18. CHIEF Project Exchange of NIEM compliant CCH information: –Between TLETS & the Criminal History Database –Between TLETS & NLETS –Between TLETS and TLETS interfaces (FUTURE) Status –TxDPS CCH currently uses GJXDM 3.0 RAP internally –NIEM 2.0 RAP Specification completed –CCH to begin transmitting RAP responses NIEM 2.0 XML documents by Fall, 2008

19. Impact to Criminal Justice Agencies Text RAP will still exist, but format may change In the future: –the RAP can be transmitted as an XML document to the local criminal justice agency –Or Not (State will continue to provide a Text Format) TxDPS will contribute a style sheet to format the RAP XML document as a PDF file.

20. Sample XML RAP

21. Sample XML RAP (cont)

22. Sample XML Rap (cont)

23. The PDF RAP

24. The PDF RAP (cont)

26. Technical Resources National Law Enforcement and Correctins Technology Center (NLECTC) –http://www.nlectc.orghttp://www.nlectc.org Georgia Tech Research Institute Justice XML Information Center –http://justicexml.gtri.gatech.edu/http://justicexml.gtri.gatech.edu/ Global Justice Information Sharing Initiative Group –http://www.it.ojp.gov/topic.jsp?topic_id=8http://www.it.ojp.gov/topic.jsp?topic_id=8 GJXDM Training and Technical Assistance Committee (GTTAC) –http://it.ojp.gov/topic.jsp?topic_id=192http://it.ojp.gov/topic.jsp?topic_id=192

27. Technical Resources National Information Exchange Model –http://www.niem.gov/index.phphttp://www.niem.gov/index.php NIEM-O-RAMA –http://www.niem-o-rama.orghttp://www.niem-o-rama.org IEPD Clearinghouse –http://it.ojp.gov/iepd/http://it.ojp.gov/iepd/ Integrated Justice Information Systems Institute (IJIS) –http://www.ijis.org/servlet/tsi.Traction?type=homehttp://www.ijis.org/servlet/tsi.Traction?type=home

28. FRVP Result of SB 1670 79th legislature Financial Responsibility Verification Program Goals –Reduce the number of uninsured drivers –Provide accurate, timely verification of insurance –Reduce burden on municipalities and citizens

29. FRVP New TLETS interface Data from TxDOT, TxDPS and insurance companies are matched and updated weekly. Vehicle Registration/Driver License formats Routine or Extended Responses

30. FRVP System returns Confirmed, Unconfirmed, Not Found, or Multiple. Citizen is still required by law to carry proof of insurance. Each Law Enforcement agency will develop their own polices Texas Statute: –Response NOT probable cause to stop a vehicle –NOT to be used as investigative tool.

31. FRVP Project Status –Development completed –Accuracy / Load testing underway –Pilot project (Registrations Only) to begin late May –Statewide rollout in late summer –Driver License component to be delivered at a later date http://www.texasure.com

32. Mental Health Continuity of Care Result of SB 839 - 80 th Legislature Department of State Health Services Clinical Management for Behavioral Health Services Retrieval of Mental Health Status for incarcerated persons Goals –Identify offenders with Mental Health needs –Improve continuity of care for offenders

33. Mental Health Continuity of Care New TLETS interface Form/Format limited to Jail Personnel Jail will submit parameters and receive a response of one or many possible matches including treatment facilities’ contact information. DSHS will also send a notification to community care facility.

34. Mental Health Continuity of Care Project Status –Design Completed –System under development –Connectivity to be in place in Late June –4-6 weeks of testing –Should be available in August Google TCOOMI

35. On The Horizon Foster Care Homes –Result of SB 723 -- 80th legislature –DFPS data will be provided to TCIC and interface with TLETS. –Allows peace officer to determine if a domestic violence offender resides at a Foster Care address. –Requirements Phase –Implementation Date Unknown

36. On the Horizon Child Safety Check List –TCIC File to locate a child/family for the purpose of investigating abuse or neglect –SB 6, 79 th legislature –Child Protective Services –Requirements Phase –Availability date not yet known

37. On the Horizon TPWD Automated Boat Registration Requirements Phase – Currently waiting on TPWD –Hope is not lost –Availability date not yet known

38. Questions?

39. Contact Information TLETS tena.watson@txdps.state.tx.us tena.watson@txdps.state.tx.us

40. Thank you