New article
Recently updated
Understanding complaint record fields
Who is this article for?Noise office staff who need a reference for the fields in a complaint record.
Access to the ANOMS Noise Analyst Workbench is required. Fields are customised per site and may differ.
This article describes the main fields that make up a complaint record in the ANOMS Complaints Properties window.
Understanding the complaint properties window
Use this article as a reference when entering or reviewing complaints.
Note: The enquiry and complaint screens are customised per site — your fields and layout may differ from the examples shown.
The Latitude and Longitude fields are filled automatically when a valid address is entered.
Reviewing major complaint properties fields
The following table describes each field in the complaint record:
Field name | Description | Entry example |
Complaint No. | Unique number assigned by the system to identify the complaint | 12345 |
Caller Number | Unique number assigned by the system to identify the caller | 1234 |
Caller Name | Name of the caller | James Smith |
Correlation ID | Unique number linking the complaint to an operation | 1788871 |
Contact ID | Unique number identifying each contact made by the caller | 1000 |
Contact Date and Time | Date and time of the caller contact | 1/1/2005 5:00:00 PM |
Title | Title of the caller | Mr, Ms, Dr, Mrs |
First Name | First name of the caller | James |
Last Name | Last name of the caller | Smith |
Phone Number fields | Phone number at the complaint location | |
Email address of the caller | chris@email.com | |
Address lines | Street number and name | 350 Main St |
City | City or town of the complaint location | Anywhere |
State | State of the complaint location | Select from list |
Zip Code | Postal code of the complaint location | 60605 |
Latitude | Latitude of the complaint location | Decimal value |
Longitude | Longitude of the complaint location | Decimal value |
Entered by | Name of the operator entering the complaint | |
Event Date/Time | Date and time that the event occurred | 10/01/02 11:30:00 |