CRISCRASH REPORT ELECTRONIC SUBMISSION Texas Department of Transportation

CRIS-CRASH REPORT ELECTRONIC SUBMISSION Texas Department of Transportation – Crash Reporting and Analysis for Safer Highways (CRASH). October 30, 2020

Agenda § Crash Record Information System Overview § CRASH Introduction § CRASH Production Statistics § Introduction to Configure § Introduction to CRASH § Data Sharing & Reporting § Crash Report Online Purchase System § Agency Support § Future § Follow Up Questions 2

Crash Record Information System (CRIS) – Overview CRIS is a web-based, proprietary software system, built to capture Texas Crash Reports (CR-3) images and data. CRIS is used by Law Enforcement Agencies, Metropolitan Planning Organizations, State Agencies, and Tx. DOT for crash-related reporting, analysis, and to obtain copies of Texas Crash Reports. This is the landing page for CRIS. We will walk through Configure and CRASH as part of this presentation.

CRASH Introduction § Tx. DOT CRASH - for Electronic Submission: Crash Reporting & Analysis for Safer Highways (CRASH) is a component of CRIS, developed for investigators to provide crash data in an automated and secure environment. Tx. DOT has enabled over 800+ business rules and edits, along with integrations with Tx. DMV’s Registration Title System (RTS) and Tx. DPS’s Texas Law Enforcement Telecommunication System (TLETS) to assist investigators with timely and efficient data entry. As of March 2017, there are 508 agencies using CRASH and 36, 759 users of the CRIS system. 4

CRASH Introduction - Free CRASH Benefits 1. System was built with timely data entry in mind and includes immediate validation, click-through error correction, and summary panel 2. System includes pre-loaded agency values for specific CR-3 fields (i. e. charges, streets, how notified) and additional custom agency fields, not on CR-3 3. Integration with TLETS for quick Driver License information and RTS for VIN or License Plate quick verification 4. System is kept current with enhancements and security upgrades, using Crash User Group inputs 5. User Names and Passwords can be managed by Tx. DOT or internally 6. CRASH Help Desk – 6 AM – 6 PM, 7 days per week, 365 days per year 7. Tx. DOT provides diagramming licenses – Easy Street Draw Web 8. Tx. DOT provides business intelligence licenses for reporting and dashboards through Micro. Strategy 9. Tx. DOT manages annual infrastructure refreshes 5

CRASH Production Statistics § Electronic crashes are being submitted and processed an average of 42% times faster than paper records. § As of 2/11/2017: 93% Electronic 6 % Paper § Tx. DOT is paying $1. 98 to process an electronic record compared to $11. 35 for processing a paper crash report. 6

Introduction to Configure 7

Introduction to Configure § Log On: – Internal Id. P – Configure to allow certain domains (Tx. DOT Hosted) § General § User Management Users – Groups – Roles § CRASH Application Settings – Service Region DAs – Crash Approvals – CR-3 Fields – Custom Fields § E-Submission § Data Sharing 8

Introduction to Configure CR-3 Fields § Allows law enforcement officers to quickly populate specific free form fields on the crash form by selecting from values defined by their agency. § Fields include: Charges Financial Responsibility How Notified Taken By/ Taken To Streets Towed By/Towed To Local Use Property Damage § The value will be populated on the crash image. § The pre-defined values must validate to be accepted in CRASH. 9

Introduction to Configure Custom Fields § Agency can create up to 5 custom fields and will only be provided to your agency and not shared with others. § These values are not included on the crash image and will only be available in Search and included in the agency Data Sharing process. Note: If the field has been used in a crash, the system will not allow the user to delete the custom field until the crash is removed from CRIS. 10

Introduction to CRASH 11

Introduction to CRASH

Introduction to CRASH Landing Page Overview § Touch Screen, Keyboard, and Mouse Enabled § Night Mode § Create Report § Configure Crash Defaults § Report Lists § My Recent Reports § Notifications and Alerts 13

Introduction to CRASH My Notifications and Alerts (Emails and CRASH Landing Page) – Notifications – Any outages due to planned system maintenance or deployments of new releases are included in the notification section. In addition, release notes are published and sent via email two weeks prior to the deployment – Alerts (stale notifications) • User/Approver will receive after 5 days • User/Approver will receive after 10 & 20 days • 30 day alert will delete the Web Crash ID record • Pending BAC Results 14

Introduction to CRASH Approvals & Rejections § None – Record is submitted to Tx. DOT when investigator submits the record § One Level – Record is submitted to supervisor, then Tx. DOT after supervisor approves the record § Two Levels – Record is submitted to supervisor, supervisor approves to another entity and then Tx. DOT after entity approves the record § Approve versus Reject 15

Introduction to CRASH Configure Data § Configure My Default Fields – Allows user to pre-populate information for any new crash created § Manage My Templates – CRASH Diagram Template Creator – Edit, Delete, Copy, and Search Templates 16

Introduction to CRASH View Crashes CRASH User: § My Rejected Reports § My Unsubmitted Reports - Add, Edit, and Delete § My Submitted Reports § My Archived Reports – Supplement Agency Authorization Manager, CRASH Manager and CRASH Approver: § My Unsubmitted Reports - Add, Edit, and Delete § Agency Unsubmitted Reports - Edit, Delete, and Reassign § Reports to Approve – Edit, Approve, and Reject § My Archived Reports § Agency Archived Reports All Users: § Search – Approve, Edit, Supplement, and PDF images of CR-3 available 17

Introduction to CRASH Create A New Crash Report § Crash Description § Web Crash ID versus Crash ID § Previous, Next, and Update § View/Add Report Notes § Close, Save, Validate, Submit, and Delete 18

Introduction to CRASH ID & Location § View/Add Report Notes § Bolded Fields = Mandatory Fields § Embedded Help – Error help text § Pre-population § Copy Field Data § Drop Down Values 19

Introduction to CRASH Units & Persons § Adding Units and Persons – Selecting the correct Unit Descriptions – Add Towed Unit, Add Primary Person versus Add Person § Select values using dropdown arrow § Importance of “Next” versus “Update” 20

Introduction to CRASH Property Damage and Factors & Conditions § Property Damage – Add, Edit, and Delete § Factors & Conditions (Environmental Conditions) – Select values using dropdown arrow 21

Introduction to CRASH Narrative – 12, 000 Characters allowed – Spell Check – Copy & Paste from external sources (Word, TLETS, Notepad. . ) 22

Introduction to CRASH Templates/Diagram § Using an Agency Template § Create a New Diagram for the first time § Create Template for the first time 23

Introduction to CRASH Investigator § Investigator Information – Investigator Name – ID Number – ORI Number (TX####### correct format) – District/Area § Crash Report Information – How Notified – Time Arrived – Report Date – Investigation Complete 24

Introduction to CRASH Summary Page Overview § Image Preview (Save Crash Report and Preview button) § Summary Information regarding Crash Record § System Generated Fields 25

Introduction to CRASH Validation § No Returns § On Demand Validation – Reports are Validated within CRASH – Fatal and Warning error messages – Fix and Revalidate - Validation Click Through – Records must be Validated prior to Submission to Tx. DOT 26

Data Sharing & Reporting § CRASH Data Sharing – XML or CSV format § Reports are now available from Tx. DOT CDA Section http: //www. txdot. gov/apps-cg/crash_records/form. htm § Reports from Tx. DOT Business Intelligence Tool (MSTR) – Reports – Scheduled or Ad-hoc – Dashboard and Report development 27

Data Sharing & Reporting Reports from Tx. DOT Business Intelligence Tool Micro. Strategy (MSTR) § MSTR User Roles: – Report Recipients – No training required. Reports receiving reports via email subscription. – Reports Users – No training required but TTI CRASH website review of Micro. Strategy is recommended. Users will only see the Investigating Agency folder and associated reports. – Report Analysts (Power User) – Successful passing of Micro. Strategy course is required. This role enables users to create ad-hoc reports. 28

Data Sharing & Reporting 29

Data Sharing & Reporting 30

Crash Report Online Purchase System § Tx. DOT has built an application that will allow the public to purchase crash reports online 24 hours per day, 7 days per week, and 365 days per year. § The Crash Report Online Purchase System requires that a single crash report be returned from a search before adding it to the cart. § Multiple crash reports can be purchased via a single transaction, but must be added to the cart one by one before checking out. https: //cris. dot. state. tx. us/public/Purchase// 31

Agency Support § CRIS Help Desk – Tx. DOT has a contract with CRIS Helpdesk to provide help desk support, 7 days a week, 365 days per year (6 AM – 6 PM) – Agencies call 1 -844 -CRISHLP (274 -7457) or email support@crishlp. com – Chat support can now be invoked from within CRASH from the Help Menu. § CRASH User Guide § CRASH, Configure, Report, and Dashboard Training § CRASH User Group – 2 nd Thursday every other month between 10 AM – 12 PM, Web. Ex Conference Call 32

Future Tx. DOT continues to: § Keep CRASH updated with enhancements § Ensure agencies have reports and dashboards that assist with their missions 33

Follow Up Questions If you have any follow up questions or concerns, please contact: CRIS Help Desk 1 -844 -CRISHLP (274 -7457) support@crishlp. com 34