Create a New Violation Case (with Checklists)


New Violation Cases (with Checklists)

1.       Find the address/map location to create the case.

a.       Try searching the Addressing pane (bottom left corner) first, to see if GIS has an address point for the violation location.

if you get a result, move on to the next step.

b.       If there’s not a valid address point, navigate to the appropriate location on the map – one easy way to do this is to find a nearby address.  TIP: The underscore character (_) can be used as a wildcard character in house numbers, so you could see everything on the 1300 block of Perdido St by entering 13 Perdido in the address search.

2.       Right-click on the address (if there is one) or on the map, select the parcel.  If there is not an address point, find the location on the map and select Create New -> Code Incident.

a.       If you chose a location from the map, you’ll get another Specify Location dialog box, where you can check Mouse-Clicked Location.  It’s usually a good idea to check the Near box – by default.  LAMA will add the nearest address point as the location label, even though the X-Y coordinates are based on where you click.

3.  Whichever way you got there, the Incident Properties window will open next.  If your division has more than one case type, you can select it from the Type drop-down list.  With the correct case type selected, add a brief description and click the Create button.

4.      Select the appropriate choice for whether the incident has been inspected yet or not.  For this example, we are assuming the site has already been inspected.

5.      In the Inspection Details window, you can change the inspector’s name (if it’s not the current user) and the date (if the inspection wasn’t today). To open the checklist of individual violations, click on the magnifying glass next to Violations.

6.       The violation checklist for your case type will open.  Anything checked as Deficient will be added to the case as an individual violation associated with the case.  The inspector can also add a description or comment to any line.  It’s not necessary to fill out OK or N/A for LAMA purposes, but they are options in case your department needs more specific details.

7.       After clicking the Close button on the checklist, anything marked deficient will populate an individual violation on the case. You can mark the inspection’s Status by selecting any of the options other than Pending in the Status drop-down box. We typically use Violation: WIP (work in progress) for cases where someone is building/renovating/remediating when the inspection occurs, and Violation: No WIP for when there are no changes or remediation attempts going on at the time of the inspection:

8.       The Violation Form is the panel along the right side of the screen. Besides the case number, type, and location, there are tabs beneath it where users can access the Events associated with the case, the specific Violations, Documents added to LAMA (e.g. inspection photos, notice letters, etc.), and Details (both custom and GIS-derived data). Completing the Inspection Details form will simultaneously complete the Inspection Event with whatever status you just selected.

If you want to get back into that specific inspection to edit it, you can click on the word  Inspection on the Inspection Event (re-inspections can be added as their own events later, so the record of each visit doesn’t have to be changed).

9.       The Violations Tab will show the code number and section of code for each deficient checklist item.  The full descriptions are stored in LAMA though, and can be added to a notice letter, hearing letter, or any other document that’s had a template created.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.