FAC Meeting Notes 2019

Charter

Monday, December 9, 2019

4:05 PM

<<FAC_Charter.pdf>>

Open

2019 FAC Membership

Friday, February 01, 2019

10:29 AM

FAC Committee Membership

2019

Sparta Police Department – Sgt. Booker Ferguson (Outgoing Member)

Hortonville Police Department – Officer Sean Stephens (Outgoing Member)

Walworth County Sheriff – Juan Ortiz (Outgoing Member)

West Bend Police Department – Officer Thomas Lichtensteiger

Outagamie County Sheriff – Patty Bleskey

Kiel Police Department – Joseph Jeanty

Class 1 City— Milwaukee PD, Jeff Vavera

Tribal Community— Ho-chunk Nation PD - Daniel Heimann

State Patrol—Mark Fetzer

State Patrol – Travis Lauer (alternate)

Natural Resources – Warden Andrew Schoeneck

Natural Resources – Warden Timothy Werner

Department of Transportation/DSP TraCS— Darlene Schwartz

Department of Transportation/DSP TraCS— Brian Neil

Department of Transportation/DSP TraCS— Geri Polster

Department of Transportation/DMV/UTC form— Sharon Olson

Department of Transportation/DSP/Crash form—Michael Satteson

Department of Justice/Use of Force form- Derek Veitenheimer

Wednesday, February 13, 2019

3:32 PM

• Office Management Training – New Users (am) - 71 interested

• TraCS Administrator Training – New Users(pm) - 63 interested

  • Review the maintenance guide

• Common Errors(review errors, how to fix errors, dealing with duplicate citations, run a baseline

  • Bring a laptop

  • Q & A

• Adhoc Queries/ Analysis Reports

  • Interactive course

  • Most common reports for all users

  • For novice and/or advanced or split up

• Basic Training to fill out all TraCS forms (old day 1)

  • Include crash form - 56 interested

• MACH Train-the-Trainer

• Use of Force Training

• Covering the maintenance guide

• MCSAP Training

• RMS Training (fall of 2020)

• Common Errors – different from last time – new errors

  • Hands on

  • For the IT – installs, distributions, etc

  • For the office staff – transmissions, completing forms

• Properly imaging and installing TraCS for mobiles so not duplicating

  • Updating or replacing equipment

• Crash Form

• Configuration Wizards, what does that involve

  • Diagram Tool – how to configure, use map, etc

• Best Practices

  • Review the fall pack and all the new features, baseline and table updates

  • Installing a WIPack

    • Go through step by step if we have it ready

• Web Services panel discussion (3 or 4 panel members)

  • Benefits of web services

  • Milwaukee PD, Fontana PD,

    • How to install and set up web services

      • Fontana

• Q & A Use of Force (new form)

  • Part of general session or separate session

• 3 most unused advanced features

  • Batch

  • Linked Attachments

  • ???

• Overview of all TraCS guides and documentation

  • What’s on the Website – FAQ’s, Agency Weekly Reports, etc

• MACH

• How to fill out Crash TraCS Form

  • Hwy 41 - 131 vehicle crash in February - Winnebago talks about trials and tribulations of completing TraCS crash forms and the process.

• RMS Training -Include in 2020 conference

• WISLR, how to get the missing streets in

  • Have a table with Kara and Kathlyn talking about WISLR questions

• What is LEA’s Vision of Future TraCS (have as part of General session - send out as part of survey)

March 19, 2019 Agenda

Friday, February 01, 2019

10:52 AM

March 19, 2019 Notes

Friday, February 01, 2019

10:52 AM

TraCS Forms Advisory Committee Meeting

DSP - DeForest Post - Large Conference Room

March 19, 2019 - 9:00 a.m. - 3:00 p.m.

Attendees: Brian Neil, Geri Polster, Travis Lauer, Darlene Schwartz, Derek Veitenheimer, Michael Satteson, Matthew Drought, Jeff Vavera, Booker Ferguson, Sharon Olson, Joseph Jeanty, Thomas Lichtensteiger, Dave Harvey, Andrew Schoeneck, Mark Conroy, and Tejal Thakkar

Introductions

Reviewed charter.

Amending/Correcting citations

• Milwaukee uses Duncan Systems to make changes to issued citations (an AutoProcess procedure)

• In the past, Milwaukee PD and Madison PD have gone to UTC Council to see if changes could be made to the Uniform Traffic Citation after issuance

• DOT/Office of General Council – Muni court can make changes before transmission

  • Circuit Court will not accept an amended citation

• Suggestion

  • Municipal Court citations - Make all fields available to change with a couple exceptions

    • Exception: Do not allow the Court field or Statute/Violation fields to be changed

  • Circuit Court citations

    • Only allow the current changes. No new suggested changes.

  • All this is before transmission to the court and after issuance

  • No changes allowed after transmission to the court.

• Discussion

  • Milw

    • Agrees with court and statute changes

  • West Bend

    • if the court needs to be changed before transmission, it should be allowed.

      • Wish that all could be changed as the courts change the OWI protocol all the time.

    • Would there be a new form with new document number, or the same form with the same document number?

      • Same document number (citation number) is wanted.

    • Some issues with changing court types.

      • Circuit courts don’t want changes.

    • Is there a need for an Amended Flag field?

      • Would require a schema change.

      • Would this also open a narrative for what was changed?

    • Who is the correct organization to make the decisions on the editing after issuance?

  • DOJ

    • There may be a need to change the NIBRS codes depending on what is changed on the citation.

    • Could have multiple NIBRS codes associated to statute numbers.

  • Kiel

    • If a Supervisor makes a narrative change, will this also set the Corrected Flag.

      • Will need to look into this

  • Could there be a secondary question / box / button to say it is being Corrected instead of finishing the narrative.

  • What about setting up a new access right for correcting

    • Citation Correction

• Decision

  • FAC agrees to move forward with:

    • Should be called Corrected not Amended

    • NTC and UTC forms would be editable after issuance and before transmission to the court except for violation/statute fields and court field.

      • Will not be allowed for Circuit Courts

    • Log of changes needed on the form.

    • Would like to have the Corrected flag set when a citation is edited after issuance

    • Put the flag on the Officers copy, edit the title to add Corrected (to all forms??)

    • Create a standard correction letter with the original value and the changed value would be a good thing to have.

    • Option to allow this at the agency level. (ini setting)

      • Yes, have this.

Statute Committee meeting

• Met with state partners who use the statute table

  • DNR, DOJ, CCAP, DSP, TraCS, DAIT and DMV

• Trying to streamline the updating and populating the violation tables

• Can download from CCAP tables

• There is a number of differences in the total number of statutes available and what we have.

  • Geri to fill in those numbers here

• Need to add the statute start date.

• Descriptions in TraCS is 60 in length, CCAP is 100 characters

  • Try to request that CCAP not add descriptions over 100 characters moving forward

• Need to investigate why CCAP has a number of Statutes that are not marked as a traffic statute, but we have it in the Traffic Table

• DOT will need to add municipal court costs for new statutes added.

Warning Report review

• Handout to review and have comments sent to Geri.

• New report will be available in the March Pack.

• All of the know bugs were fixed in this version

  • Margins were the biggest issue.

  • No longer get the error message when printing

• Redesigned to look more like other reports

  • Kept citation form look

• The new report is according style

  • Grows as information is added to the form.

  • Can be a short as ½ page, can be a lot longer.

• Fields appear when there is data, do not appear when there is no data.

  • Case number

  • Additional description

  • Additional instructions

• When 2 or more statutes or ordinances are entered, all descriptions are concatenated in the field. Up to 3 lines.

• When the report needs to be sent to the agency, the additional title of Mail To: above the agency address

• Days to Corrections will appear on the Officer copy. It has never been on the defendant copy.

• Discussion

  • Like that it is standardized and looks like all the other reports.

  • All the data fields are the same, nothing changed.

  • Date Correction seems to be too small that it may be lost.

    • Also add it to the Date Time line on top of the form

      • Date to appear when populated.

March Pack testing agencies

• Sparta, SQL and web services

• Kiel, access

• Will get this authorized on Wednesday. Along with the maps.

• Geri needs to send this handout to Kiel and Sparta so they can provide to officers prior to the March Pack. Done

Use of Force and Arrest related Death = UFAD

• Injury sections should be identical for officer and subject

• Group 1 : Injury should be consistent on both the subject and officer. We will compare and make the fields common between them. Make sure the actions are per subject, who is armed. Subject is listed first.

• Incident numbers need clarification

• Cover fire needs different working.

• A lot of documentations. Questions on the top of the form.

• Non reportable disposition.

• Officer group/info. first then subject group/info.

• Deadline. Report right away then fill out the rest of the fields could be months. Should have some sort of cutoff.

• FBI needs a '0' report to be submitted monthly.

  • No Use of Force/Arrest Related Deaths to report for that month.

• Open records county level not local jurisdiction level.

• Not identify specific officer/victim.

• Climb reporting opt in, at the agency level.

• Training purposes also.

User Conference Items

• Darlene reviewed the 2019 LEA Survey Results

• 550+ agencies use TraCS

• 204 agencies responded to the survey

• User Conference Evaluation

  • Responses all over the board

• Handout sheets

  • Training

    • Have some interest in the Office Management, Office Admin trainings

    • Comments

      • Should find a way to explain how to go to Web Services

        • Issues and how to fix them

      • Need to advertise what the class is and what it is covering

      • Get better documentation, including known issues and fixes

      • Crash

        • Have a session on the different situations that the crash unit has experienced.

      • May need to add experience level to descriptions (novice, advanced, etc)

  • Does the helpdesk track their calls?

    • What are the top issues?

  • May want an unscripted Question or Answer session

  • Common officer errors/validation errors

    • Common errors for IT

    • 50% validation then 50% IT.

    • Or separate into 2.

  • Common errors

    • WIJIS error. Go into log WIJIS doesn't always give a correct status.

    • Duplicate document number -- new feature.

    • Don't say call the help desk. Give us the actual fix.

  • Web services.

    • Panel.

    • 4 hour vs 1 hour.

    • Not enough content for 4 hour as all install is. Obstacles. Issues.

  • Derrick will do a blurb for UFAD.

    • Do we need a session for it.

    • Probably 2 session and/or general session.

  • Do hands on walk through. Informal breakout. For user and admin.

  • Crash form. One of session, talk about Winnebago over 100 units.

    • Fluff. Maybe over lunch about it.

  • Weird crash session. Stress F2 help. Adding email to all.

  • UFAD and pursuit.

  • Configuration wizard. In the install reinstall updates.

  • Rebuild the autonumber.ini.

  • Common tips and tricks.

  • Advanced features.

    • Batch transmission

    • File upload.

  • MACH

    • MACH more users? Almost solved but developer the MACH server is stressed.

  • IT best practices

    • Go over:

    • TraCS diagram tool: since 73 is going away. Custom Palette.

    • Question sworn IT or regular IT or hay your good with computers guess what you are TraCS guru.

    • Do we need decision makers at the conference.

    • Centralized database.

      • Cost, manage own data.

      • General session.

      • Other examples of other state. Agreements, host data release data.

    •  

    • How to make TraCS better. Include what we are doing, what do you want.

  • Pre conference

    • Current training is for novice. Have both one in morning one in afternoon.

    • Advanced is case by case basis. AD.

    • Do not duplicate between days.

    • Ad hoc queries. Lots of questions can do 4 hours.

      • More complex.

      • So much data.

    • Crash form training ????

      • Not just crash,

      • Every form, forms manager, end shift/start shift.

      • Form flow

      • Every form

      • Alcohol with other forms and look.

Referrals

• 2733 - Declined

  • Need a little research on a warrant.

  • Beneficial for open records.

  • Name cards separate people.

  • Leave it in.

• 2867: Approved.

  • Need to add the country.

• 2541 – Conditionally approved. Line 14

  • Combine Basis and Other Basis fields. Make it narrative, 2000 characters. Change to Basis for Stop/Contact

  • Jurat section

    • Sparta put Non Expiring in the commission expires field for judges

    • Add choices to the do you want to remove the "no notary" section.

      • Audio checkbox add.

  • Affidavit

    • Take the time and AM off of the DOB field.

• 2823 – Informational only. No decision needed.

• 2832 - Test

  • Should do some performance testing on transmission and storage

  • Are there any other limits we might find.

  • If ok go to 10 megs.

  • At least double the size. (1mb to 2 mb)

  • Check for LEA's RMS issues as well.

• 2833 - Approved

  • If approved, should be added to all the other forms with narratives.

• 2834 - Declined

  • The change would not be consistent with the citation.

  • Keep as is. Would make the printed warning form longer if moved.

• 2857 – Approved.

  • Now have unlimited Definable fields available.

  • If approved, which statute would you like, can only have one.

    • Does not matter

  • Just the three citations

• 2867 - Approved

Meetings in the future

• Would people like the option to call in, if they can't make the drive in for the meeting?

  • They like getting out of office

  • Face to face helpful. No.

Future Pack Schedule Changes

• Fall Major update sept.

• Nov/Jan bug fixes and table updates only

• March Enhancements, bug fixes and table updates.

• May/July bug fixes and table updates only

• Comments. Limit enhancements for only 2 times a year.

Crash Update

• Large Crash in February, 2019 occurred on I41 in Winnebago County

• Winnebago County Sheriff's Office completed the crash report

• The Winnebago CSO decided it was a 119 unit crash

• Single crash

  • Set up a high powered/robust computer to enter the crash on - hoping to speed up the entry time some

  • Technically, TraCS is able to handle 99 units for one crash

    • Realistically, it took 15 hours to enter a 55 unit crash in our test system.

  • DOT/Crash Records Unit proposed to Winnebago CSO to enter as smaller crashes and then at the state they would merge it into 1 crash

    • Winnebago CSO agreed and chose to enter and submit 12 crash documents with 119 units.

  • DOT/Crash Records Unit marked the 12 crash reports as "Not available for purchase" as soon as DOT received the crash so customers would buy one of the 12 crash reports. DOT took approximately a week to merge the crash reports and created a cover letter to put on the front of the crash report so they understood that it was one crash, but was submitted in 12 different crash forms.

    • It became available last Friday - 3/15/19.

    • The Crash report is approximately 380 pages long.

2019 FAC Meetings:

• June 12, 2019

• September 11, 2019

• November 13, 2019

June 12, 2019 Agenda

Wednesday, April 10, 2019

10:45 AM

June 12, 2019 Notes

Friday, June 07, 2019

10:27 AM

TraCS Forms Advisory Committee Meeting

DSP - DeForest Post - Large Conference Room

June 12, 2019 - 9:00 a.m. - 3:00 p.m.

Attendees:  Liam Looney, Teresa Heidemann, Chris Kraft, Jeff G, Booker Ferguson, Tom Lichtensteiger, Derek Veitenheimer, Tejal Thakkar, Kevin Barman, Joe Jeanty, Sharon Olson, Aaron Covaleski, Juan Ortiz, Mike Satteson, Travis Lauer, Geri Polster, Brian Neil and Darlene Schwartz

Responsibility Agreement – Matt O'brien

• SP4337

• DNR 4100-129

• Consistency between DNR and DOT

• Add to Alcohol Suite

• Do we need the signature or just put in the form.  Do not sign other forms.

• Arrest, different it is liability.  Just releasing to responsible party.

• Number 5.  maybe a little different.  This is a state patrol form.  Milwaukee PD uses.  

• Need to take the responsibility need signature.  

• Do we add.  Dar wants a clarification we will do research signature.  Print out and scan in.  

  • Is there a way to have them sign on a touch screen 

  • DNR looks almost the same except vehicle type.  

  • Add incident number or case number instead of citation number

  • Have one form with DNR and SP, instead of two forms

  • Add or bring in the vehicle type (want to make sure it works for all vehicles)

  • Remove specific statutes.  Ask a lawyer. 

Correcting Citation 

• Darlene shared results of her inquiry with CCAP and attorneys.  There is no statute that says you can't amend a citation

• This would  be for Municipal Citations only.

  • CCAP would be phased in later.

• Spoke with Court Clerks and found that they do not want to have any amends

• The use of Amended is in the statutes, so we may want to use that term instead of Corrected

• This would be an Opt In program.  Agencies can chose to participate is they want to.

• Statute 19.16.1b says CCAP must change to provide an accurate citation.

• Milwaukee courts say as long as the citation is changed and the customer is properly notified in time to make a defense, that is ok.

• Changes not to be allowed:

  • Court Name

  • Statute number

• There is an issue with the replicating the citation and not catching the venue change needed.

  • Can the replicate be done but not bring over the Court?

  • Would like to have a box that asked if you want to replicate the Court Information

• Can there be a switch to allow a change from CC to a muni?

  • Court is determined by location

  • Can we add a field that triggers a change?

    • Not sure if this will work

• Questions about ordinance and how they are linked to the statute

  • Will the statute override the court?

• Still need to notify the defendant of the changes.

• Would like to be able to change the statute as well

  • All the additional paperwork has the original citation number 

  • Do not want to have to go back and change all the original paperwork to the new citation number

• How is the ELCI and NTC different in the back end. (Geri to supply notes for this)

• Is there a way that once the ticket is issued that all of the links be severed.

  • Can be changed without validation

• Some judges have issues with amended citations

  • Why is the original citation number now have 2 different statutes

  • If you send a correction letter, why didn't you just void and reissue?

• Should allow agencies the option to be able to make the changes

  • Some agencies would not allow officers to make changes

  • Where would the access level be given? Supervisor or other.

• Demo – Geri

  • Went over the handouts

  • Where should the word Corrected or Amended be put?

    • Should go to the right of the Court Use field.

    • Agency space? 

      • Can you print the changes there as well?

  • Can there be a pop up asking for what is changed, like the crash?

    • Need an additional field to print the changes

    • Agency space is not a good option as agencies don't want to lose what is already there.

  • Need to state 'Amended Citation' so it does not look like a specific field has been changed.

  • The Corrected field is populated as the form is opened.

    • CC will always say 'NA'

  • There is a new ribbon for the specific functions as related to citations.

    • Will also move a few buttons to the new ribbon

  • Ribbon buttons

    • Correct Citation

      • Lakdlald

    • Open original

      • This will allow for the creation of a PDF of the original.

        • Agencies able to specify where the original can be stored.

        • Right now storing onto a network share is slow, will be better when webservices functionality becomes available.

      • Working on being able to attach the original pdf as an attachment automatically.

        • Can be attached manually now.

      • Webservices functionality still needs some work before the attachment can be sent to a network location.

      • Can the original be created only when it is opened for change?

        • Would cut down on storage

        • What about purge criteria?

      • Can the log be used to recreate an original?

        • TraCS cannot.

        • Agencies may be able to recreate their own with their own software.

      • Agencies would prefer not to have a pdf generated for every citation issued.

        • This would be way too many to store.

      • Would time be better spent in creating a better way to print the log for that citation?

      • Original – we interpret as the issued citation.

• Access Right

  • Move supervisor access to this button 

    • Issues- why when I change the narrative do I get a pop up asking why I changed the form 

•  Parking ticket- error message given 

  • Circuit courts don't get any special features

  • Muni Court- editing available in many of the fields 

  • Hit validate before you close the form, to ensure the changes work. 

Court type is not based off of field information. 

If they replicate any ticket type (ntc's and lc'c) they are going tog et a pop up message that asks do you want to transfer over plaintiff info

No- nothing will transfer over

They can change it up to the point that they issue. 

Either copy over whole plaintiff group, or you don't.

If you don't turn on access right, they won't see anything

Add additional button to toggle whether it's on or not.

Two issues

One- when you go to install tracs, do you access right or opt in, or both. 

Access Right- since it’s a ribbon, it either shows the ribbon or it doesn't. 

Opt in- set up using configuration wizard, where you have a setting where you say you want this feature, agency wide. 

Like override- used to do it anytime you wanted, now you have to have it on. 

Need access right, but can add opt-in button

Yes- need an agency right, 

EVERYONE agrees! add the opt-in

Call it CITATION AMEND

Getting rid of supervisor access right – moving everything to this specific button 

Is there a way we can start? With LC's?  

• Is there a way only certain statutes would work? - no, unsure how to do.
   

• Is there a way to hit "correct", where only matching court table statutes would show? - no

Sparta doesn't agree with changing the statute or name.

Can't pull anything for transmission from the log. 

Will the old value and new values be captured?  

Some situations the program will change it, the two extra fields get wiped out. 

• New Databars 

  • In April 2018, the FAC expressed a stong desire for a clickable graphic data bar for the initial point of Contact and Damage Areas fields.

  • TraCS worked with TEG to get these Databars developed 

  • Got 4 asked for 2

• Manner of Collision 

  • Options based on relation of vehicles in crash (head to head, side to rear, etc..

  • Initial Point of Contact, pick based on diagram 

    • Added unknown or vehicle not at scene tabs

  • Areas of vehicle damage

  • Seating Position Diagram

    • Split up into Row, position within the row, other locations (cargo area)

    • Pedestrian non-occupant seating position

      • May need to report a "driver" who is not in the car, such as a runaway vehicle or child driver 

      • Need this to get on record. 

    • Lost this in MUK though, so we added a new role, absent driver, treated the same as a regular driver, but makes it clear they weren't in the vehicle, and wouldn't require seating position 

• Current Standard only have rows one through four

  • It's desirable to know which row an individual is in

    • We want to add another field 

      • Might get confusing?

    • We want minimal impact, only opens up if select other 

    • Optional field

• Proposal- for every operator there is a series of factors, including 4 speeding related.

  • Moving those four factors to a separate field, highlighting specific questions about speeding field. 

    • FAC approved

• Updates

  • Began a project to publish crash documentation to public server, it would open it up to public analysts, professionally developed and maintained. 

• Comments

  • NonDomesticated Animal needs to have a definitive answer instead of skipping

  • On Emergency field

Warning Form Feedback

• Boxes instead of underscores 

• Sounds like everything is good

• Use of Force and Arrest

  • Use of Force Form coming this year, 4^th quarter. Via TraCS.

• UFAD- Use of Force and Arrest Related Death

  • Most of the time there won't be anything to report, but still need to report monthly what is going on

  • Target heads of agencies to ensure reporting 

• You can transmit this form multiple times.

• Two agencies = two groups now

• No issue with data being in programs

  • Does the form do enough for an agency's lower level use of force

  • This form will likely organically grow. Likely agencies will come up and say were collecting things in word or excel, but I need ability to record tasers and stuff. 

  • Inevitable expansion overtime 

• Does there need to be an agreement between DOJ AND DSP? 

  • No- you guys are the sponsor, take what you need

Law Enforcement Side- hesitant on this 

YELLOW necessary fields 

Number of citizens??

Printed Report Available? - yes, still working on it in DOJ. 

Referrals

• 2875

  • Button that issues citation without printing. 

  • Use contact summary

  • no

• 2892

  • Email + paper copy of citation 

  • Defendant needs paper copy. 

  • No

• 2902

  • Trooper has had issues with advanced notice for translator. 

  • Court different time for translator??

  • Agency Space- first 20 characters

  • Talk to C-CAP and address it next time. 

• 2903

  • Text Reminders – defer to Schema 

• Could we limit the statute numbers by officer? 

  • Sounds like an officer issue not a training issue.

• Margin errors 

  • Converting the reports

  • Attachments, reports will print them

• FALL OF 2019

  • Converting a bunch of FAC only reports this fall. 

• Administrative Review Report 

  • Last three pages will be one report

  • Looks a little different, but that was necessarily

  • They like boxes

• Informing the Accused 

  • Some changes last fall, but requests for changes

  • You either have something written in there

  • Is this more desirable than plain line? The three- yes. 

  • Statute number and description 

    • Why can't we print the officers name in the line? 

  • Confuse truncated statute? Maybe the arrested should read the entire statute. 

  • Don't populate, truncate a statute, because you may be missing a part. 

• Intent to Revoke

Accordion report can't control where page break is

Equipment Inventory

Good

Good

September 11, 2019 Agenda

Thursday, August 15, 2019

3:14 PM

Draft Session Descriptions

Friday, June 07, 2019

7:36 AM

Advanced Features

Audience: IT Staff, Management

Audience Rating: Experienced

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 2:15 - 3:25

This session will review a few advanced features within TraCS, such as the batch transmission, notification services, and file uploads.

Bring any questions you may have on how to use certain features

at your agency or how other agencies are using the feature(s).

Centralized Database

Audience: Office Staff, IT Staff,

Management

Audience Rating: All

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 12:50 - 2:00

Badger TraCS and Wisconsin State Patrol will soon provide a

statewide, centralized database available to all Badger TraCS

agencies across the state, allowing agencies to take advantage of

the multitude of TraCS Web Services features without the need to

host their own IIS Server or SQL Server databases.

This session will discuss project timelines, advantages and answer

any questions or concerns prospective member agencies might

have.

Crash Form Q&A

Audience: Officers, Management

Office Staff

Audience Rating: All

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 10:50 - 12:00

Wednesday, Oct. 16: 12:50 - 2:00

The DT4000 Crash Form should be easy to complete when

reporting simple or routine crashes, but less common or more

complex situations may cause problems. This session will provide

examples and pointers on when and how to report some of these

more difficult cases; for example:

• Unusual Reportable Crashes

• Questions Involving Fatal Crashes

• Truck, Bus and Hazmat Crashes

• Recording Citations on Crashes

• Multi-Unit Crashes

• Transmission/Validation Errors

• Runaway Vehicles/Hit and Runs

• TraCS Diagram Tool

Common Errors - What they

are and how to fix them

Audience: Officers, Office Staff,

IT Staff

Audience Rating: Moderate to

Experienced

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 10:50 - 12:00

This session will incorporate several hands-on situations; the first

half of the session will look at errors the officer or office staff may

receive in several situations.

The second half will identify/rectify the errors. Using a training

version, we will simulate different issues that will help the TraCS

Admin/IT staff recognize and resolve common issues, such as

deciphering whether there was a transmission error to the State or

the RMS software, correct citation number installation issues, and

end/start-shift forms over the network and using a USB drive.

Creating Adhoc Reports

Audience: Officer Staff, IT Staff,

Management

Audience Rating: Novice

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 12:50 - 2:00

Learn how to create and run your own adhoc reports. Bring your

laptops with the fall training version of TraCS installed so you can

follow along and go through the step-by-step instructions to create

ad hoc reports.

When you leave, you should understand the steps for creating

simple adhoc reports and what different data fields or attributes

you can pull into a report. This session serves as an introduction

so you can go home and start creating and writing more reports.

Don't forget to bring your laptop!

Mobile Architecture for

Communications Handling

(MACH): Present and Future

Audience: All

Audience Rating: All

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 2:15 - 3:25

Mobile Architecture for Communications Handling (MACH) software is

hosted by the Wisconsin State Patrol and jointly funded with the

Wisconsin Department of Natural Resources. MACH is in use by

over 180 public safety agencies and 4,500 users within Wisconsin.

The MACH breakout session will provide user agencies and those

interested in MACH with an update as to recent MACH changes, an

update as to forthcoming developments, and answers to any

MACH user or technical questions.

Properly Installing and

Reinstalling TraCS Packs

Audience: IT Staff, Those who

have rights to install software

Audience Rating: All

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 12:50 - 2:00

This session will walk through how to correctly install WIPack updates

on all TraCS machines at your agency - from the TraCS Master to TraCS

Mobile Data Computers (MDCs). Brand new TraCS installations, current

TraCS machines, and replacing TraCS machines will be discussed.

Ensuring the correct WIPack, Map Pack, and Distribution get installed,

preserving not-yet-end-shifted forms, and conserving ELCI citation

numbers will all be discussed. We will also go over how to check

whether WIPacks get successfully installed - and how to rerun the pack

if they haven't.

Tips and Tricks

Primary Audience: Officers,

Office Staff, TraCS Users

Audience Rating: Novice

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 2:15 - 3:25

This session will go through several helpful ideas and suggestions

to make completing, transmitting, or managing your forms easy

and efficient.

The content of this session is geared towards newer users and will

suggest best practices for common processes and practical

information for working in TraCS.

Web Services:

Law Enforcement Panel -

Benefits, Pitfalls, and

Successes

Audience: All

Audience Rating: All

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 10:50 - 12:00

A panel of 3 to 4 law enforcement representatives will go over the

benefits (pros and cons) of Web Services, any obstacles they had to go

through, what they needed to do to prepare. How did they upgrade --

via internal staff, IT vendor, or county IT staff?

We will then discuss the steps agencies need to take to go to Web

Services; including prep work, the actual move over, how to do installs,

and working with Web Services changes from client computers.

Understanding the Use of

Force and Arrest Related

Death Form

Audience: Officers, Management

Office Staff

Audience Rating: Novice to

Experienced

Training Duration: 1 hr 10 min

Wednesday, Oct. 16: 10:50 - 12:00

Wednesday, Oct. 16: 2:15 - 3:25

Learn how to complete the new Use of Force form. You will

understand what fields mean, which ones re required, and how to

best complete the form.

We will go over transmitting and updating the forms that have

been previously transmitted.

Draft Conference Agenda

Friday, June 07, 2019

7:27 AM

Open	2019 Badger TraCS User Conference Optional Training Agenda

 7:30 - 8:30 AM – Registration (Hallway)

7:30 - 8:30 AM – Individual Agency Support / Question and Answer Opportunity (Hallway)

NOTE: Find your personal schedule showing the breakout sessions you selected in the back of your name tag holder.

Open

September 11, 2019 Notes

Monday, September 09, 2019

4:11 PM

Attendees:

Walworth County Sheriff – Juan Ortiz (Outgoing Member)

West Bend Police Department – Officer Thomas Lichtensteiger

Kiel Police Department – Joseph Jeanty

Class 1 City— Milwaukee PD, Matthew Drought

Tribal Community— Ho-chunk Nation PD - Daniel Heimann

State Patrol—Mark Fetzer

State Patrol – Travis Lauer (alternate)

Department of Transportation/DSP TraCS— Darlene Schwartz

Department of Transportation/DSP TraCS— Brian Neil

Department of Transportation/DSP TraCS— Geri Polster

Department of Transportation/DSP/Crash form—Michael Satteson

Guests:

Help Desk Staff

• Dennis

• Alex

• Dave

Crash Staff

• Joe

• Tejal

Milwaukee Staff

• Tammy

• Nancy

• Chris Kraft

Conference Update

Presentations

• Help Desk staff on hand to review presentations

  • Dennis and Tom

  • Dave and Juan

  • Alex and Matt

Amending Citations demo

• Geri walked through the process.

• After issued

  • Amended flag set to No

  • Disposition is Issued

• Go to amend flag field

  • Asks reason for change before the changes are made

  • Make desired changes

• When printed the Citation Amended will show on the upper right quadrant of the PDF of the citation.

• Must make changes to the FormPreferences.ini file

  • Set AmendCitation to True

• Need to have CitationAmend access right

  • This gives access to the Amend button

• Notes: Check for validation breaking when closing the form.

  • Are validations run after editing and printing?

• Questions:

  • Is there logging of the changes made?

    • Yes

• Issue with Municipal courts (Juan)

Incident Form

• Incident workgroup has created the lists of fields and FAC designs the entry form.

• Cut and Paste activity

• Only have one individual group with roles

• Have parent either

  • Separate group with link to others

  • On every person type group like victim, offender, involvement

  • Combine reported by and involvement

• Non Reportable status is no longer used on the crash form after v3

  • Removed so Non Reportable forms can be validated.

• To see Reportability status you need to add the column to the forms manager

  • Right click on the column heading and select Column Chooser

  • Drag the wanted columns to the forms manager

• If a form comes in as Non Reportable, they are using an old form.

• Now need to look at the Reportability Status

• Milwaukee issue

  • Accidents now show Completed.

  • If Validated and Completed, the Reportability Status will show as Non Reportable.

  • Can sort by using the Custom tab on the sort and selecting the definable tab wanted.

Adding Roads

• Should contact WISLR to have roads added.

• Alias can be added by contacting them

• Note: Find the email for WISLR and add to the notes.

Access Levels

• Agencies are able create their own access levels for their agencies.

• FAC should only be involved when a global access level is desired.

• Reviewed access levels (need to add others)

  • Alcohol

  • All Forms

  • AmendedCrash

  • Arrest

  • Attachment

  • BasicUser

  • CallForService

  • DNR

  • DNRCrash

  • Developer

  • DriverCondition

  • ELCI

  • Equipment

  • FatalSupplement

  • Status

  • Supervisor

  • SystemAdmin

  • Task

  • Transmission

  • UFAD

  • ViewOnly

  • ViewOnlyCases

  • Warning

• Leave it the way it is now.

• Other access levels that may be a good candidate

  • ApproveWithoutTransmission

• Should we ask for others?

  • No,, it may be too specific by agency.

Referrals

Item 2997 - Declined

Item 3017 - Declined, use Word that has the envelope settings.

Item 3033 - Question 1 - Declined

Item 3112 - On Hold for further research. Do not want agencies to update Court information.

Item 3116 - Declined. The only date that has the radio buttons are vehicle year. Research to find the break year. Can also set up as an agency default (19 or 20).

Item 3133 - Accepted

Item 3135 - Declined.

Item 3136 - Accepted. Narrative should be at least 50 characters. If not give a warning for a longer message or attachment needed. Could we add a statement between or in the title.

Other discussion:

• Crash Databar review for fall package

• Pedestrian Non Occupant role.

• Parking Tickets

  • Paid, Parking Amount, Parking Ticket, TVRP number fields added

  • Added 1st 2nd 3rd Notice

November 13, 2019 Agenda

Tuesday, October 22, 2019

11:25 AM

November 13, 2019 Notes

Tuesday, November 12, 2019

4:11 PM

Attendees:

Walworth County Sheriff – Juan Ortiz (Outgoing Member)

West Bend Police Department – Officer Thomas Lichtensteiger

Kiel Police Department – Joseph Jeanty

Class 1 City— Milwaukee PD, Jeff Vavera

Tribal Community— Ho-chunk Nation PD - Daniel Heimann

State Patrol—Mark Fetzer

State Patrol – Travis Lauer (alternate)

Department of Transportation/DSP TraCS— Darlene Schwartz

Department of Transportation/DSP TraCS— Brian Neil

Department of Transportation/DSP TraCS— Geri Polster

Department of Transportation/DSP/Crash form—Michael Satteson

Department of Justice—Derek Veitenheimer

Sparta Police Department – Sgt. Booker Ferguson (Outgoing Member)

1. Welcome

2. TraCS User Conference recap

   1. Comments--Good result 108 responses 320 participants. Positives,

   2. 1/2 wanted to attend training next year.

   3. Liked cases during lunch, keep having that next year.

   4. Training the day before was also very good

   5. Questions about moving the conference date.

      1. Some like the idea of sharing what is coming out in the fall pack.

      2. Don't like the idea of sharing what is coming, but then it changes when the pack is released.

      3. Have webinars and in person every other year?

      4. What about a January/February conference.

         1. Could explain the fall pack release issues.

   6. Like having the videos online to review sessions.

3. Fall Pack Release update

   1. Reviewed the release notes from the TraCS meetings

   2. Can fix office machines by just copying the settings.ini file from a working machine to the other office machines.

4. Crash Information

   1. Mass Crash Manual-Massachusetts has an online manual.

      1. Wisconsin would like to get the Crash Form manual online as well.

      2. Asked for TRCC funding but was denied.

      3. Still looking for funding to do this.

      4. Also could make performance metrics (audits) available online

      5. Audit ability is great, but this information needs to be given back to the agencies first.

   2. Transmission Failures

      1. Analyze failures each morning.

         1. Contact each agency to help out.

      2. Failures have been reduced.

   3. Providing feedback to local agencies.

      1. Would like to review crash submissions for other information

      2. Did receive funding to create some tools to accomplish this.

      3. Would like to have a single point of contact at each agency.

         1. Could we add an agency email in the agency group

         2. Could we pull the email from the agency table

            1. Who should be it sent to?

               1. Officer or agency email

         3. Could we add a Reviewed by box that could include the email to send correspondence to? May be a more agency specific…

         4. Could this come from TOPS lab?

            1. Maybe

         5. What about doing this by form?

            1. How would this be tracked and/or stored?

            2. Could put this in the agency table.

      4. The Crash Unit would like to have local agencies provide the checks that they perform so they can incorporate them into these tools.

      5. Could there be a "Supervisor" validations run before transmitting to the state?

         1. These could be warnings

         2. This may be technically feasible, but needs more research.

      6. What about a Pre-Transmission send to the state and if it passes, then it could be sent as final.

      7. TraCS can research and see if this concept is viable.

   4. Fall Changes

      1. New databars

      2. New Role - Pedestrian (Non Occupant)

   5. Planning for 2020

      1. Disentangle Unit status and/or role field

         1. FAC likes this idea

      2. Clean-up, organize long selection list (factors)

         1. Group like items in the lists

            1. Maybe include a header per group

         2. What about setting rules that would eliminate some selections based on prior information?

      3. F2 Help Improvements

         1. Update pre 2017 pages

         2. Include validation rule descriptions

            1. Have validation help files available during validation

            2. After running the validation, have a Validation Help that would open up and highlight the areas/errors

            3. Would need to ask TEG to make this process available

            4. Could they add a validation document link up in the Help field?

         3. Section Help (Scenarios)

         4. FAC thought all these are good ideas

      4. True Private Property/Parking lot short form

         1. Would still like to be able to do a full form

      5. Revisit Fatal Notification from TraCS, Fatal supplement

         1. Some issues of not being used is that it is email based and not all machines have email access.

         2. Incorporate the Fatal Supplement into the full Crash Form

      6. TLT

         1. Reference point automation project

         2. What improvements would LE like to see in the TLT.

            1. Engineer suggestions

               1. Greater clarity on ramp accidents.

               2. Background map is not very detailed, would like to see structures, etc

            2. Law Enforcement

               1. Would like to see a google map or LIDAR maps

               2. Intersection crash usually shows an estimated distance even if it appears to be in the center.

               3. Could it get down to the lane based values instead of centerline values.

         3. What is the possibility of removing the 50 radius at an intersection so that an intersection accident does not show a distance.

1. UFAD

   1. Delays, last minute validations. Xml server had issues.

   2. Trying for a release this year. Might not happen. Need to get a staging webservice, waiting on DOJ. Final production trying for Dec 11th finalized.

   3. Can enter old data back to Jan 2019. zero report is very important.

   4. Send Derek list of agencies that have updated.

2. Law Enforcement Survey

   1. Anything we should add that you want to know

   2. What forms are agencies using?

   3. Are you on Access or SQL

   4. Interested in using the hosted database?

      1. Still using access

      2. Other questions if they say yes

   5. Like the sign up genius for appointments?

   6. What RMS and MDB they are using

   7. Still using Windows 7 and how many machines?

      1. No longer supported after Jan

   8. User Conference

      1. Different time of year?

      2. Prefer a webinar instead of in person?

      3. Step by step instructions? Not from a live presentation

   9. Fatal notification?

      1. Creating a fatal supplement group on the crash form.

      2. Would you like a report for the fatal notification so that you get a pdf?

      3. NOTE: may look into a Fatal Notification form in the future

   10. Incident Form

       1. If TraCS has an incident form how likely are you to use it?

   11. Would your agency be interested and / or use a Tow form?

3. Incident Form

   1. Outputs

      1. eReferral to DAIT - mandatory

      2. IBR to DOJ - mandatory

      3. Probation / Parole

      4. Human Trafficking

      5. Suspicious Activity Reporting

      6. Child Protection Services

      7. Prescription Drug Monitoring Program - mandatory

      8. Overdose Detection Mapping Application program

      9. Local Drug Unit

      10. Cleary

      11. WSIC

      12. Fusion Center

      13. Human Services - Adult and Child Protective Service

      14. HIDTA

   2. Prescription Drug Monitoring Program

      1. Fields needed listing review.

   3. Transmission

      1. How is double incidents recorded and sent in?

         1. Current website is set up for only one report at a time.

         2. The PDMP would have to allow their system to accept more than one at a time.

         3. If they cannot accept more than one, can we put multiple groups on the form and transmit them one at a time?

            1. No we cannot.

      2. Need to clarify how 1 person with 5 prescription pills is handled. (Geri please review this line)

      3. Would DOJ be able to create a service to parse out to proper agencies, similar to eCitation webservice

   4. Testing ideas

      1. Looking for an area that agencies could come in and test forms.

      2. Possibly in the Law Library

      3. DOJ is working on a testing lab

   5. Timeline

      1. Still working on getting it out for fall 2020

      2. FAC would rather have complete system put out

         1. May reduce le buy in if it is not complete and they would have to train on a partial system.

4. Hosted Database

   1. Programming changes are being worked on and should be completed by March.

      1. Migration of data tool will also help in going to the local agency SQL system

   2. Transmission

      1. Batch transmitted by the state in Accepted status

      2. Will need to have good documentation on how and why to use statuses.

      3. May have to start using Tags as well to convey when form is ready for the next step.

      4. RMS files will be put on the application server and local agencies will have to download them.

   3. Table manager

      1. Locals will update their tables, but we need to have some programming done to have this is done.

      2. Still looking into having any updated tables to be downloaded at login.

   4. User

      1. TEG is looking into locking down some of the user fields. Primary ID is the one we are worried about. It will be set by TraCS to an email address.

   5. If a local agencies host other agencies data, can the hosted agencies update their own tables.

      1. Yes, after TraCS get some programing done.

   6. Master Index, can we search for archived names?

   7. Fees

      1. Would it be feasible to ask le for the payment up front when the contract is signed?

         1. FAC does not see this as a problem.

      2. Would be used to replace equipment at end of service life.

      3. FAC thinks projected fees ($50 to $100) may be too low.

5. Project Prioritization

6. Referrals

   1. 3159 - Declined. If someone does not complete the test or refuse, then all clues are present. Could be a training issue for the judge as well.

   2. 3169 - Print out of owners name and last known address. Accepted but low priority.

   3. 3179 - Would be ok just to link to the upper level 356.57 instead of each subsection. Can't use a hyperlink in the violation search. Would need to request TEG to allow this to happen. - Accepted

   4. 3183 - Accepted

   5. 3189 - Accepted

   6. DSP - Can the "Do you want to run TransComm now?" button.

      1. If removed, it makes it hard to find failures.

      2. Can we program it to continue after a set amount of time?

7. Next Meeting

   1. Tentatively scheduled for February 12th.